I am not sure if this is your issue but I have had issues with Com Interop when upgrading from VS2005 to VS2010.
It relates to Aximp not working via the IDE. We got around it by performing the Aximp via cmd line. https://connect.microsoft.com/VisualStudio/feedback/details/557722/errors-utilizing-activex-controls-in-vs-2010 "We have a VB6 based ActiveX Control compiled into a .ocx file that we have used in one of our .net projects under Visual Studio 2008. However with Visual Studio 2010 we found that when we try to create an instance of our object on our control surface by double clicking it from the tool box Visual Studio 2010 throws an error indicating that it doesn't think the ActiveX was registered correctly. We dug into this a bit and I narrowed it down to 2 public interfaces in the ActiveX control that Visual Studio 2010 doesn't like. Oddly the behavior is different if the target framework is set to 4.0 or if it's set to an earlier framework. When your target framework is .net 4.0, if you have a public interface that exposes EITHER the VBRUN.EventInfo class -OR- exposes the VBA.CallType class you will have this problem. When your target framework is set to .net 3.5, if you have a public interface that exposes BOTH the VBRUN.EventInfo class -AND- exposes the VBA.CallType class you will have this problem. Curiously if one or the other is exposed (but not both) the problem doesn't occur. It is very important that we get this fixed if we are to migrate our project, used in 30,000 workstations around the globe, updated to Visual Studio 2010." It is supposed to get fixed in .NET 4.0 SP1 "if resources and scheduling allows them" Regards Adrian Halid Senior Analyst/Programmer IT Vision Australia Pty Ltd (ABN: 34 309 336 904) PO Box 881, Canning Bridge WA 6153 Level 3, Kirin Centre, 15 Ogilvie Road, Applecross, WA, 6153 P: (08) 9315 7000 F: (08) 9315 7088 E: [email protected]<mailto:[email protected]> W: http://www.itvision.com.au<http://www.itvision.com.au/> ___________________________________________________________ NOTICE : This e-mail and any attachments are intended for the addressee(s) only and may contain confidential or privileged material. Any unauthorised review, use, alteration, disclosure or distribution of this e-mail (including any attachments) by an unintended recipient is prohibited. If you are not the intended recipient please contact the sender as soon as possible by return e-mail and then delete both messages. ___________________________________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Scott Baldwin Sent: Wednesday, 27 April 2011 7:09 AM To: ozDotNet Subject: Re: COM problems in Visual Studio 2010 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 <[email protected]<mailto:[email protected]>> 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: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] 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: [email protected]<mailto:[email protected]> [mailto:[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]> [mailto:[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 __________ 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
