Bug 10244 - AssemblyName should not be a configuration-specific setting
Summary: AssemblyName should not be a configuration-specific setting
Status: NEW
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: unspecified
Hardware: PC Windows
: Normal enhancement
Target Milestone: ---
Assignee: Lluis Sanchez
Depends on:
Reported: 2013-02-12 11:44 UTC by Eric Maupin
Modified: 2013-03-13 11:30 UTC (History)
3 users (show)

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 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 original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Eric Maupin 2013-02-12 11:44:35 UTC
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.
Comment 1 Sebastien Pouliot 2013-03-13 11:30:20 UTC
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