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 10244 on
Developer Community or GitHub 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
Visual Studio does not completely support AssemblyName as a configuration specific setting. For someone moving to XS from VS, this is confusing and may lead to mismatched assembly names. This can cause problems with [InternalsVisibleTo] (https://bugzilla.xamarin.com/show_bug.cgi?id=10223) that is not correctable from the UI in Visual Studio.
The same* issue caused a lot of confusion for debugging some issue(s) for Cocos2d-XNA where the iPhone and iPhoneSimulator assembly names were different - and Type.GetType(string) was used.
* at least the different name parts, not sure how much, or even if, VS was involved