Things to be vaguely anxious about

Now now, don't go thinking that I'm going to turn this blog into my own, personal tupperware 'o neurosis. (It's not like you have enough of your own neurosis. I'm sure you want to share mine.)

In the name of "doing it right", there are a few things I want covered as I begin tutoring myself in development. It's almost like I know a bunch of the "best practices", but I've just never implimented them. Well, all of them. At once. For a single project.

Lessee...

• Source Control - How do I get this nifty Visual Studio 2005 Express Edition IDE to integrate nicely with subversion? (or am I stuck with doing the _svn thing with TortoiseSVN..?) Is there a "better" choice then svn? (keep in mind we want to do auto building and unit tests) The "new" visual source safe? (now now, keep the tomatos to yourself, I'm just asking..!!)


• Unit Testing - I've rolled my own unit testing in some perl development (yes, I know there are cpan modules to make it easier), but...what tool is the "best" for doing unit testing in C#? (equiv. of JUnit for java...) Pitfalls?


• Automated Build & reporting - Need to integrate those unit tests into an automated build framework. Build,test,report. (what is it..ant for java? .net equiv?)


• DB integration with the above. How to version the database and include it's versioning, rebuilding, and loading with data as part of the unit test process. I came across a wonderful doc a while back but I neglected to bookmark it. Bad me, bad, bad me!

That's all I can think of for now. Ok, now that the checklist is created I can get on to real work...(see, I told you I was being neurotic. =^)   )