I have a similar problem.

Where do you set this property to false.

 

I managed to find a reference here
http://weblogs.asp.net/cazzu/archive/2011/03/11/check-your-embed-interop-typ
es-flag-when-doing-visual-studio-extensibility-work.aspx

 

But on the assemblies I think are causing me grief, there no "Embed Interop"
Types property.

Is there something somewhere where you have to set to make this option
visible?

 

Regards Peter

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Kirsten Greed
Sent: Monday, 25 April 2011 5:27 PM
To: 'ozDotNet'
Subject: RE: COM problems in Visual Studio 2010

 

Hi Scott

We had problems with VS2010 that did not occur in VS2008

They were solved by turning  Embed Interop Types Off on the assemblies

Cheers

Kirsten

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of Scott Baldwin
Sent: Wednesday, 20 April 2011 4:48 PM
To: ozDotNet
Subject: COM problems in Visual Studio 2010

 

Does anyone know if COM Interop has changed in any way in VS2010?

 

I am getting COM exceptions when debugging an existing application in VS2010
when working with IShellItem. These COM exceptions did not occur in VS2008,
and I can't find any difference in the code. The exceptions don't actually
change the way in which the application works, and don't come up when not in
debug mode, but I would like to get to the bottom of why they are occuring.

 

Attached is a minimal VS2010 solution that exhibits the behaviour, any help
would be much appreciated.


Thanks.
-- 
Scott Baldwin
Senior Developer - QSR International <http://www.qsrinternational.com> 

blog: http://sjbdeveloper.blogspot.com

Reply via email to