I'm using Visual Studio 2012 RC to work with my C # solution all my configuration-specific The settings are stored in a single .props file, which then is included in all my .csproj files.
Nevertheless, VS insists to include this right:
& lt; Property group status = "'$ (configuration) | $ (platform)' == 'debug | sccpu'" & gt; & Lt; IntermediateOutputPath & gt; C: \ Users \ xyz \ AppData \ Local \ Temporary \ vs855E.tmp \ debug \ & lt; / IntermediateOutputPath & gt; & Lt; / PropertyGroup & gt; & Lt; Asset group status = "'$ (configuration) | $ (platform)' == 'release | ACCpu'" & gt; & Lt; IntermediateOutputPath & gt; C: \ Users \ xyz \ AppData \ Local \ Temporary \ vs855E.tmp \ Release \ & lt; / IntermediateOutputPath & gt; & Lt; / PropertyGroup & gt; & Lt; Import Project = "$ (MSBuildProject Directory) \. \ Common.props" /> Why is that so?
FYI, my common file looks like this:
put those intermediateoptionpath Can be gone when MSBLild is given a bad way.
In our case, after the SolutionDir for Output Folders, we had unnecessary slash.
What was not working for us (note additional slash):
& lt; Output Path & gt; $ (SolutionDir) \ ou \ bin \ & lt; / OutputPath & gt; & Lt; IntermediateOutputPath & gt; $ (SolutionDir) \ ou \ obj \ & lt; / IntermediateOutputPath & gt; What worked:
& lt; Output Path & gt; $ (SolutionDir) out \ bin & lt; / OutputPath & gt; & Lt; IntermediateOutputPath & gt; $ (SolutionDir) out \ obj & lt; / IntermediateOutputPath & gt; To help troubleshoot your particular case, turn on diagnostic MSBuild output and go to Tools-> Options-> Projects & Solutions- & gt; Build & Run-> MSBuild Project Build Output Verbosity Then search for the generated folder (eg "Temp").
Using a common project / prop / target file is a great idea, but it requires a little fight with Visual Studio.
Comments
Post a Comment