Implicit Dependencies with Visual Studio

The page https://www.ncrunch.net/documentation/troubleshooting_project-build-issues is pretty good but could be improved by:

• Tell how to do in Visual Studio for .csproj (a bit like you did for .proj but via the GUI)
  
• Tell how to do in Visual Studio for .vcxproj (a bit like you did for .proj but via the GUI and for C++ projects)
  
• Avoid numerated lists (they suggest doing more than one action in steps)
  

Thanks for the feedback. I've updated the page to make it clearer.

Thanks.

How do you do that for a C++ project? Files don't get usually copied to the output folder but may be NCrunch has another trick that avoids having a custom NCrunch configuration?

.vcxproj files still make use of the same (or at least very similar) syntax in order to include source files, for example:


<ItemGroup>
<ClInclude Include="ClrCpp.h" />
<ClInclude Include="resource.h" />
<ClInclude Include="Stdafx.h" />
</ItemGroup>
<ItemGroup>
<ClCompile Include="AssemblyInfo.cpp" />
<ClCompile Include="ClrCpp.cpp" />
<ClCompile Include="Stdafx.cpp">
<PrecompiledHeader Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">Create</PrecompiledHeader>
<PrecompiledHeader Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">Create</PrecompiledHeader>
</ClCompile>
</ItemGroup>
<ItemGroup>
<None Include="app.ico" />
<None Include="ReadMe.txt" />
</ItemGroup>

NCrunch is able to identify these dependencies in the same way as for C#/VB dependencies, so in theory as long as the file is showing in the VS solution explorer, then NCrunch should be aware of it and no custom configuration should be necessary.