Yesterday I discussed the beginnings of my hardware environment. There's a
little more to it than that, but for the moment I'll focus on the development
tools I use for development. In this post I'll focus on some of my .net
development tools...
Main IDE
Visual Studio 2003 - My
main development has been in C/C++/C# over the many years. For this project I
will be using C# and ASP.NET
NUnit Add-in - Point &
Test NUnit integration
GhostDoc Add-in - Source
code commenting is easier than ever with this little tool.
Database
MS Access
- One of the main reasons I'm using this is because my previous hosting service
didn't support SQL Server, In my development project I'll be using a provider
model to decouple the data store from the rest of the application. Once the MS
Access portion is complete, I'll most likely implement a SQL 2000 and SQL 2005
version.
Source Control
Source Safe
- I've used this a lot in past projects and had a pretty automated setup for
pinning versions, branching and labeling
SubVersion - I may investigate this
for future source projects
CVS - I've used this in the past, not my
favorite but TortoiseCVS makes it easy
Build Tools
NAnt - I've used
Ant for all my Java projects so it only
seems natural to use NAnt for my current development.
MSBuild - I'll be
looking at this in the future for evaluation purposes, but (N)Ant works in
multiple OS's
Cruise Control.Net - This will be
something new for me. I want to explore
continuous integration for my development project so I will be documenting
the process for setting this up in my environment
Testing Tools
NUnit - Again, I've used
JUnit for Java projects so this was a
no-brainer. The only issue is getting used to some of the nuances of each such
as the way
instancing works in JUnit as compared to NUnit
NUnit.ASP - I haven't used this
so it will be an interesting ride. Again, I'll use this blog to explore my setup
and use of the tool.
SQLUnit - I'm haven't used this
either, but I'll be taking a look at that as well
Other things to consider
NCover - I'll need to look at
this in the future
SourceMonitor 2.0 - Code
Metrics
That's a quick summary of what I'll be working with. There are a few others I
didn't have time to list (I've only allocated .5 hour to actually composing on
this blog) but I'll continue to update this entry with more information over
time. I'm sure I missed a few obvious tools that I either take for granted, do
there work in the background, or that I haven't had a need for yet.
Tomorrow's topic will be a quick introduction to my project.