Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>NAnt is a build tool that builds .NET projects and solutions (based on the original Ant for Java). It is also an XML-based "scripting" language where you order "tasks" to do the build work, including the types of things you are talking about--and MUCH, MUCH more!</p> <p>We use NAnt as our build scripting tool (triggered on every source-control checkin by Cruise Control.NET, a.k.a. CCNET, our Continuous Integration tool) to do our automated builds. It includes things like:</p> <ol> <li>Building the solution</li> <li>Running our Unit Tests to make sure the build didn't "break"</li> <li>Deploying our web project to our development server</li> <li>Zipping and archiving a build into a build folder for historical tracking and "backout"</li> </ol> <p>Another solution is MSBuild, which is actually what Visual Studio uses. It is very similar.</p> <p>Do note: You CANNOT build Setup &amp; Deployment projects with NAnt's solution task (you also cannot do this with MSBuild). To get around this, we have started running devenv.com (Visual Studio without a UI) with command-line arguments--using NAnt's "<strong><em>exec</em></strong>" task instead of the built-in "<strong><em>solution</em></strong>" task--to build the whole solution, including Setup &amp; Deployment Packages. We have also uses WiX and MSBuild in the past...</p> <p>Finally, for the specific issue you outline, you should really just consider one of these options:</p> <ul> <li>Simply add the dependent projects to the Web Site solution as Project References and you will get the DLLs there automatically</li> <li>Consider creating a PostBuild task (look on the Project Properties window) that does an xcopy on a successful build</li> </ul> <p>You really can't go wrong investing time in NAnt, and eventually CCNET as your project complexity increases. You can have CCNet watch your source control for checkins or run nightly, AND you can set up dependent projects, so that, for example, if your dependency project builds, it can kick off a build of your web site and/or run Unit Tests to see if anything broke.</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.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      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