Bug 4937 - binding generator fails to load assemblies on .NET 4.0
Summary: binding generator fails to load assemblies on .NET 4.0
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.1.x
Hardware: PC Windows
: --- blocker
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-05-07 21:36 UTC by Atsushi Eno
Modified: 2012-05-10 18:06 UTC (History)
3 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 FIXED

Description Atsushi Eno 2012-05-07 21:36:31 UTC
The bug details are discussed here.

http://lists.ximian.com/pipermail/monodroid/2012-April/009953.html
Comment 1 Atsushi Eno 2012-05-07 21:39:32 UTC
I could reproduce the issue after uninstalling VS11 beta and .NET
Framework 4.5 beta. The issue was due to this .NET bug (Marek
remembered the issue when he saw the .NET stack trace):
https://connect.microsoft.com/VisualStudio/feedback/details/635365/runtimehelpers-initializearray-fails-on-64b-framework#details
Comment 2 Marek Safar 2012-05-08 03:47:41 UTC
Mono's official mono/cecil does not have such static constructor which means upgrading to the official version should fix the problem.
Comment 3 Chris Hardy [MSFT] 2012-05-08 06:50:26 UTC
I see the same issue with VS2010 and Windows 7.
Comment 4 Atsushi Eno 2012-05-08 07:04:38 UTC
Note that this happens *only* with VS2010 *without* VS11 (.NET 4.5).
Comment 5 Atsushi Eno 2012-05-10 18:06:51 UTC
Fixed.