Bug 2015 - Compilation checks strong name for all references
Summary: Compilation checks strong name for all references
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.8 Beta 2
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-11-13 06:07 UTC by Kenneth
Modified: 2011-11-16 09:02 UTC (History)
2 users (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 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:
Status:
RESOLVED NOT_ON_ROADMAP

Description Kenneth 2011-11-13 06:07:20 UTC
When compiling a project that has a strong name, MonoDevelop will check that all referenced projects have a strong name, and otherwise abort compilation.

This is of course logical, but it differs a bit from what Visual Studio does.
In Visual Studio, the reference strong name check is done when a type is actually referenced inside the project being compiled.

As the project I am working on loads the assemblies at runtime, there is no need to check the strong name (and some projects have references that are not strong named). With Visual Studio, I can reference the projects without actually using them in code. This causes VS to copy the dll's into the project output folder, where I can later load them dynamically.

With MonoDevelop, I can not compile the project which references the projects that are not strong named, and thus the dll's are not copied to the output folder.

I realize that this is perhaps a slight abuse of how the build system works, but I have not found any alternative way to achieve the same with MonoDevelop or VS.
Comment 1 Lluis Sanchez 2011-11-15 15:33:55 UTC
As a workaround, you can add the assembly as a file to the project, setting the build action to None and the Copy to Output Directory option to Always.
Comment 2 Kenneth 2011-11-16 09:02:33 UTC
That does not really work, because the file to copy depends on the type of build, i.e. you cannot add both debug and release files to the output folder.

Also, any dependencies must be manually included as well.