Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 for Bug 46943 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
When we upgraded to Mono 4.6 we found that several of our registry key related unit tests failed.
In our products unit tests we created a registry key in a using block and then called a method which created resulted in the same key being created, also in a using. Values were added to that key in the method before the key was disposed.
In our unit test we verified those values before disposing of the key in the test.
This currently results in a NullReference exception in a call to GetSubKeyNames but some analysis of the code shows that even if the crash was avoided the behavior would still be different from Windows.
The following unit test should pass:
public void TestGetValueNames()
using(var testKey1 = Registry.CurrentUser.CreateSubKey(@"Software\Xamarin\UnitTests").CreateSubKey("4.6.1"))
using(var testKeyInner = Registry.CurrentUser.CreateSubKey(@"Software\Xamarin\UnitTests").CreateSubKey("4.6.1")