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 on
GitHub or Developer Community 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.
The distributed Mono.Cecil and Mono.Cecil.Mdb assemblies are referencing mscorlib version 2.0.
For those who cannot compile them, please supply them compiled against mscorlib version 4.0 to use with this target framework.
Why is this a problem? Assemblies compiled against 2.0 mscorlib should work fine on 4.0.
Even if this might be possible (Side by Side having two CLR in one App) i don't want to mix up the CLR's and blow up the App.
Furthermore it's possible to have only version 4 installed, so what to do then ?
You will not have two CLRs. The 4.0 CLR can load assemblies that target 2.0.
It seems you are right. I've seen no mscorlib 2.0 module loaded when loading Cecil (despite of it is referencing 2.0)
I have no idea how this is possible, but you may close this issue. Sorry.
The runtime has special handling for references to assemblies known to be in the core framework, and automatically upgrades such references to a newer version at runtime when loading the assembly.
Sorry for adding an additional note:
I've used Cecil also in Windows .Net (don't beat me)
This cross-platform usage seems not to be possible any more as it seems
Windows has not such an mechanism :-(
.NET does this too.
Forget my last post, i was wrong again :-(