Bug 1493 - MonoDevelop.AspNet assembly does not have a strong name
Summary: MonoDevelop.AspNet assembly does not have a strong name
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: ASP.Net ()
Version: 2.6
Hardware: PC Linux
: Lowest minor
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-10-14 07:27 UTC by Danny Bembibre Gude
Modified: 2014-05-21 17:16 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 on Developer Community or GitHub 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:

Description Danny Bembibre Gude 2011-10-14 07:27:36 UTC
I want to add the assembly MonoDevelop.AspNet to use the class Internal.ParserException (FileName method), but im only can use via reflection because the assembly is not signed with a strong name.
Comment 1 Mikayla Hutchinson [MSFT] 2014-05-21 17:16:31 UTC
Sorry, we are not strongnaming MD assemblies.