After many hours of unmanaged debugging of Visual Studio assembly loading
and binding process, it turns out that the problem is caused by bug in CLR.
It happens not only to ReSharper, but to other plugins as well: http://forums.microsoft.com/MSDN/ShowPost.aspx?PageIndex=0&SiteID=1&PageID=0&PostID=2812645
We identified the reason of the crash and it was quite funny: ReSharper references
System.Core.dll itself. If our investigations are correct (still verifying
this with Microsoft), any addin referencing this assembly will cause "silent
death" when WebSite with specific properties is opened. Those properties
are assemblies in web.config, which reference System.Core.dll themselves,
and System.Core.dll is not loaded via website reference before them.
Since we were going to remove dependency on .NET Framework 3.5 anyway, we
reimplemented some of the System.Core functionality in source code (so we
can continue eat our own dog food with queries and extension methods) and
removed reference to System.Core.dll. This fixes the problem here.
Whoever experience the problem, please check nightly build 773 and see if
it fixes the problem. Thank you for your patience!
"Develop with pleasure!"