Fog Creek Software
Discussion Board




Welcome! and rules

Joel on Software

.NET Quality Control Tools

The recent discussion on source control got me to thinking about other tools that impact quality control.  I've been trying to put together a suite of "peripheral" development tools that work together well.  For example,

NUnit - unit test framework
NAnt - automated builds
NDoc - automated library documentation
MS Web Application Stress Tool - performance & reliability tests
FogBugz - bug tracking
VSS/CVS/Perforce - source control

What additional tools do you use, and what works together well in your experience?

ODN
Tuesday, March 11, 2003

FXCop - Programming conventions enforcement tool. Enables your team to write consistent CLS compliant code and even checks variable naming conventions and interface correctnes. Customisable to allow your own perception and desired level of 'correctness' ;)

http://www.gotdotnet.com/team/libraries/

Sergio
Tuesday, March 11, 2003

We definitely use NUnit a lot. I've used NAnt and NDoc in private products, but we're using a much better (and costly) documentation generator now, and VS.NET very poor but functional enough project management. Also a +1 for FxCop.

Not a quality tool directly, I use Jay Freeman's Anakrino[1] a LOT to disassemble the library binaries into C# source code. It answers a lot when peering into the internals of the system.

If you do a lot of web development, and need to sniff the wire, you might find a lot of value in Simon Fell's ProxyTrace[2] and relatives.

[1] http://www.saurik.com/net/exemplar/
[2] http://www.pocketsoap.com/tcptrace/pt.aspx

Brad (dotnetguy.techieswithcats.com)
Tuesday, March 11, 2003

Oh, and of course, we use FogBUGZ. :) Version 3.0 is great.

Source control is CVSNT w/ SSPI and TortoiseCVS[1] for the shell. We haven't yet integrated CVS w/ FogBUGZ, mostly because of limited time to get IT work done.

[1] http://www.tortoisecvs.org/

Brad (dotnetguy.techieswithcats.com)
Tuesday, March 11, 2003

http://draconet.sourceforge.net/

Like Cruise Control this tool can help automate your daily (hopefully) builds.

Ian Stallings
Wednesday, March 12, 2003

I'm finding Visual Studio.NET's project deployment tools inadequate for ASP.NET.

Specifically, the only tool it has is the Copy Project action.  This allows you to copy all files necessary to run an application.  That's good. 

However, there's no way to copy only necessary files that have changed.

Richard Ponton
Thursday, March 13, 2003

Are there Installer test tools out there that can verify my installation, post-installation? Especially multilingual installations (expectied files, folders, start menu items, reg keys, and so on)???

-j
Tuesday, March 18, 2003

*  Recent Topics

*  Fog Creek Home