Yes, you are correct Kirsten, it is only valid for .Net 4.0 framework, also it is automatically set to false for all system references, so unfortunately this is not the answer to my problem. On Mon, Apr 25, 2011 at 10:42 PM, Kirsten Greed <kirst...@jobtalk.com.au>wrote:
> Hi David > > I think this property is only relevant for version 4 of the dot net run > time. > > Right click the reference to the assembly in your project > > Select properties > > Regards > > Kirsten > ------------------------------ > > *From:* ozdotnet-boun...@ozdotnet.com [mailto: > ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Peter Maddin > *Sent:* Monday, 25 April 2011 7:49 PM > > *To:* 'ozDotNet' > *Subject:* RE: COM problems in Visual Studio 2010 > > > > 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-types-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:* ozdotnet-boun...@ozdotnet.com [mailto: > ozdotnet-boun...@ozdotnet.com] *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:* ozdotnet-boun...@ozdotnet.com [mailto: > ozdotnet-boun...@ozdotnet.com] *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 > > > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 6068 (20110424) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > -- Scott Baldwin Senior Developer - QSR International <http://www.qsrinternational.com> blog: http://sjbdeveloper.blogspot.com
