MSBuild output and Visual Studio output vs. COM interop

I am trying to get a sandboxed build environment setup in my development team.

The problem I am currently facing is a DotNet project that references a VB6 COM assembly. The COM assembly is registered with the build system, but when I run msbuild against sln I get the following error:

error MSB3303: Could not resolve COM reference "f630637a-718a-41c7-9c52-41f934dc4625" version 3.2. Object reference not set to an instance of an object.

      

The GUID for this assembly is correct and if I load the solution in Visual Studio it builds fine and generates Interop assemblies. * as needed.

I don't want Visual Studio to be built as a requirement in build steps.

How can I get msbuild from command line to build Interop assemblies the same way as VS?

+2


source to share


1 answer


It looks like msbuild doesn't match project dependencies in the same way as IDE - according to this question



If I create a specific project that was unsuccessful before building the whole solution, everything is fine.

+2


source







All Articles