Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Implicit Dependencies with Visual Studio
wernight
#1 Posted : Friday, July 13, 2012 4:17:46 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 6/11/2012(UTC)
Posts: 7

Thanks: 1 times
The page https://www.ncrunch.net/...ng_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)
Remco
#2 Posted : Saturday, July 14, 2012 9:41:27 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,143

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Thanks for the feedback. I've updated the page to make it clearer.
wernight
#3 Posted : Monday, July 16, 2012 9:12:40 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 6/11/2012(UTC)
Posts: 7

Thanks: 1 times
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?
Remco
#4 Posted : Tuesday, July 17, 2012 7:13:16 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,143

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
.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.
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.037 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download