The issue pertains to the Visual Studio 2010. I have two projects: a class library and a setup project. The class library exposes a COM object (plugin) using the .NET COM interoperability. The library depends on a number of COM type libraries. For each COM
type library there is a corresponding primary interop assemby, properly registered using "regasm /codebase". The target framework is 3.5 (the hosting application that loads the plugin only supports 2.0 runtime). The library compiles without any issues, but
setup project fails to detect any of the COM dependencies. The issue is easily reproducable, just create a simple class library in VS2010, change the target framework to 3.5, add a reference to a COM type library. Create a setup project
and add the "Primary Output" to it. The COM dependencies would not show up.
It seems to only happen if I switch the target framework to 3.5 BEFORE building the deployment package. Switiching the framework to 4.0 and changing the "Embed Interop Types" to "False" does fix the issue.
I was going to submit an issue to Microsoft, but want to see if there someone out there who ran into the same issue.
Thanks for any suggestions
View Complete Post