Bug 17240 - Could not load file or assembly 'mscorlib, Strong name validation failed.
Summary: Could not load file or assembly 'mscorlib, Strong name validation failed.
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.8.x
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2014-01-15 05:46 UTC by Andy
Modified: 2015-07-17 11:37 UTC (History)
9 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 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 Andy 2014-01-15 05:46:08 UTC
Could not load file or assembly 'mscorlib, Version=, Culture=neutral, PublicKeyToken=7cec85d7bea7798e' or one of its dependencies. Strong name validation failed.

VS 1.8.35
XS 4.2.2 build 2
Comment 1 Andy 2014-01-15 06:26:12 UTC
There's a workaround on stack overflow
Comment 2 Shruti 2014-10-30 05:48:58 UTC
Dear Andy,

Can you please confirm us that you are still facing this issue ? 

If you are facing this issue again, Please provide us steps in detail which will help us to reproduce this issue.
Comment 4 Ian Ceicys 2015-07-17 11:37:20 UTC
Updating the status to resolved not reproducible. We do not have enough information to take any action on this bug.