Note that there are some explanatory texts on larger screens.

plurals
  1. PONAnt and MSBuild command line woes
    primarykey
    data
    text
    <p>I'm trying to configure NAnt to automate my build process - once I've got this step nailed, I'll be integrating the unit tests.</p> <p>Perhaps I don't exactly know what I want, so please correct me if there is a completely different way of doing all of this...</p> <p>I want two NAnt targets, one to do quick, debug builds to make sure everything works and the tests pass, and another target to do a proper compile and publish (its a web application project)</p> <p>My problems are...</p> <ol> <li>I can't get MSBuild to compile just the dlls, it's always copying all of the web-app junk (images, css, .aspx files etc) with it. Is there a way to stop this? If so, how?</li> <li>When I compile using /t:Compile, its still creating .pdb files for the dlls. Is this correct? I Thought these were for the debugger, and therefore shouldnt be present when doing a release compile?</li> </ol> <p>here is my NAnt target for the full release compile (publish):</p> <pre><code>&lt;target name="build.deploy" description="Compile Web Site." depends="init"&gt; &lt;exec basedir="." program="C:\WINDOWS\Microsoft.NET\Framework\v3.5\msbuild.exe" commandline=" MyProj/Interface/Interface.csproj /nologo /t:Compile /t:ResolveReferences;_CopyWebApplication /p:OutDir=../../deploy/bin/ /p:WebProjectOutputDir=../../deploy/;AspNetConfiguration=Release" workingdir="." failonerror="true" /&gt; &lt;/target&gt; </code></pre> <p>Thanks for you help!</p> <p>P.S. I dont have to use msbuild if there is an easier way. I tried to use CSC first, but I couldnt resolve all the referencing problems i was getting. Suggestions very welcome </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload