Bug 38826 - Problem with System.Security.SecureString
Summary: Problem with System.Security.SecureString
Status: RESOLVED FIXED
Alias: None
Product: Compilers
Classification: Mono
Component: C# ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Marek Safar
URL:
Depends on:
Blocks:
 
Reported: 2016-02-17 01:09 UTC by Martin Baulig
Modified: 2016-02-17 18:30 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Martin Baulig 2016-02-17 01:09:32 UTC
We somehow can't compile this anymore:

======
using System;
using System.Security.Cryptography.X509Certificates;

class X
{
	static void Main ()
	{
		new X509Certificate2 (new byte [0], string.Empty);
	}
}
======

If fails with an error message

=====
B.cs(8,3): error CS7069: Reference to type `System.Security.SecureString' claims it is defined assembly `mscorlib, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e', but it could not be found
=====

Tested with 4.2.2, master and 4.3.2.
Comment 1 Marek Safar 2016-02-17 12:33:23 UTC
I cannot reproduce this with master and 2.0.5.0 indicates you have some mix of mobile dlls there.

You can try `mcs --mcs-debug 9` if that reveals anything
Comment 2 Martin Baulig 2016-02-17 18:30:52 UTC
Turns out I had some BCL's in the directory I tried to build in.