0

I have an unmanaged C++ project, the output of which I need to copy to the output folder of a .NET project.

Visual Studio 2010 won't let me add the C++ project as a project reference as it isn't creating a managed assembly.

I've tried adding the following to the .csproj file manually but it doesn't seem to be working (eg. when running msbuild, the .NET project is being built first)

<ItemGroup>
    <ProjectReference Include="pathtoproject\unmanaged.vcxproj">
        <ReferenceOutputAssembly>false</ReferenceOutputAssembly>
        <Private>False</Private>
    </ProjectReference>
</ItemGroup>

How can I enforce this build dependency to work with a command-line build?

David Gardiner
  • 16,892
  • 20
  • 80
  • 117

3 Answers3

2

So it turns out that the example I gave in the question is actually correct. That will cause the C++ project to build first.

My problem was that I was trying to hook in to the MSBuild targets in the .NET project to then copy down the C++ dll, and I was doing this too early in the build cycle for that project (I was hooking into BeforeBuild). Using the 'BeforeCompile' target instead seems to be late enough in the build cycle that it works properly.

David Gardiner
  • 16,892
  • 20
  • 80
  • 117
1

Add both projects to a solution and use the project dependencies to make sure the the unmanaged project builds first. You can build a solution from the command line.

Project Dependencies Dialog

ta.speot.is
  • 26,914
  • 8
  • 68
  • 96
Gary
  • 5,642
  • 1
  • 21
  • 41
0

I believe your question may have been answered in this thread:

How do I add a reference to an unmanaged C++ project called by a C# project?

Have a look at SLaks answer

Community
  • 1
  • 1
ezekiel68
  • 148
  • 7
  • It is similar - though all the responses there seem to relate to copying the build output - not enforcing the build order to make the C++ project build first – David Gardiner Feb 05 '13 at 03:48