[ScintillaNET] Re: Automating build for .NET
- From: <scintilla@xxxxxxxxxxxxxxxxx>
- To: <scintillanet@xxxxxxxxxxxxx>
- Date: Thu, 3 Jun 2004 13:02:12 -0400
> Visual Studio.NET - What else and why else?
Because it is difficult to automate, difficult to integrate with other tools
(e.g. NUnit, CruiseControl.net), and difficult to run non-interactively. No
disrespect, but my experience has been that only the most trivial of
non-production projects can hope to achieve quality or stability without
extensive build automation. But perhaps your VS.NET chops are better than
mine, and you have been able to do things like automatically run unit tests,
package, label source control, and upload when you build. Kudos, if so.
I've set up about ten different projects now using NAnt. The best option
seems to be to use the <solution> task so you can still develop with VS.NET
without having to maintain two different repositories. I find NAnt to be
fairly mature, and generally quite capable. Version 0.85 is going to add
some really nice features, and you can get them now if you're willing to run
the beta (I do at one client with only minimum problems).
Check out FlexWikiPad and friends over at the fwcontrib project [1] if you
want an example of a fairly generic NAnt/VS.NET setup that you can totally
rip off.
I'm also happy to share my experiences further, either on- or off-list.
[1] http://sf.net/projects/fwcontrib
--------------------------------------------------------------------------
ScintillaNET Mailing List: ScintillaNET@xxxxxxxxxxxxx
To unsubscribe: Send an email to scintillanet-request@xxxxxxxxxxxxx
and put "unsubscribe" (without the quotes) in the Subject line.
Web Page: http://tinyurl.com/yvoh2
Other related posts:
