Error on Properties Page "COM object that has been separated..."

I have both a Windows XP SP2 PC and a Virtual Windows 2003 Server. Both have VS2005 Team Edition with SP1 and VS2008 Team. I have installed the ReSharper 4.0 Evaluation on both and on both I get the following error:

1) Open a project page for a C# class project
2) Select either Application, Build, Build Events, Debug, Reference Paths and Signing and the message "An error occurred trying to load the page. COM object that has been separated from its underlying RCW cannot be used."

I have checked the Event logs and there is no message there. The message is the same for the tabs cited above. However other tabs such as Resources, Settings and Code Analysis behave normally. Given the need with the solutions here to specify a refererence path this severely restricts my work.

The appearance of this error after installing ReSharper on two machines (with different OS) indicates ReSharper as the likely culprit. I still remain impressed enough with ReSharper to want to buy my own license, but I am disturbed by these problems with team Edition. I previously used ReSharper with Visual Studio 2005 Pro and it was very useful.

Any suggestions as to how I may fix this error?

3 comments
Comment actions Permalink

I have made one further observation. If I click on Fred.sln within Window Explorer, I can open all the properties pages without getting the COM RCW separation message.

If start up VS2005 from the menu and open a previously opened solution from the start page, I get the problem.

If I close down Visual Studio and re-open from Windows Explorer, I do not get the problem!

Well I have a work around, but I would like a complete fix!

I have also reported this at

Edited by: TATWORTH on Jul 24, 2008 3:26 PM

0
Comment actions Permalink

Do you have StyleCop/Source Analysis (not the Code Analysis from Visual Studio, but the new tool that came out to check C# code style on MSDN)?

Because its a known bug of StyleCop/SourceAnalysis that is being fixed in the next version (of StyleCop, not Resharper) with that -exact- behavior.

0
Comment actions Permalink

I had the same problem last month and it turned out that Microsoft Source
Analysis for C# was indeed causing this behaviour.

http://gabriel.lozano-moran.name/blog/PermaLink,guid,8cea48ab-e1c0-4950-866e-55f970acf2f2.aspx

Cheers

Gabriel Lozano-Moran

"Francois Ward" <no_reply@jetbrains.com> wrote in message
news:13872964.151551216919504385.JavaMail.jive@app4.labs.intellij.net...

Do you have StyleCop/Source Analysis (not the Code Analysis from Visual
Studio, but the new tool that came out to check C# code style on MSDN)?

>

Because its a known bug of StyleCop/SourceAnalysis that is being fixed in
the next version (of StyleCop, not Resharper) with that -exact- behavior.



0

Please sign in to leave a comment.