Hello Mike,
I actually wrote it in some details so that anyone with similar problem can
find this later.
Also I hope Microsoft can release a hotfix for this problem, which is quite
annoying.
Sincerely,
Ilya Ryzhenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
MS> Wow, talk about a debugging nightmare. I can only imagine what a
MS> long and painful process it was to get to the bottom of that issue
MS> (only to find out it's not even your fault!). We're all grateful
MS> for your efforts :).
MS>
MS> Cheers.
MS> Mike
MS> "Ilya Ryzhenkov" <orangy@jetbrains.com> wrote in message
MS> news:76a2bd0b154c538ca67d87a2cfa0b@news.intellij.net...
MS>
>> Hello,
>>
>> 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&P
>> ageID=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!
>>
>> Sincerely,
>> Ilya Ryzhenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
