Santomania : Setting up a .NET Development Tree

This Blog

Syndication

Search

News

** BlogWave FAQ **

Me

My Bits and Snippets

BlogWave

WssDal (/w source)

FixSiteLinks (/w source)

HierarchyMapper (/w source)

Disclaimer
All opinions are my own. All content is provided "AS IS" with no warranties, and confers no rights. Use code samples at your own risk.
Posts may contain information that is confidential, privileged or unsuitable for overly sensitive persons with low self-esteem, no sense of humour or irrational religious beliefs. Any dissemination, distribution or copying of this post is not authorised (either explicitly or implicitly) and constitutes an irritating social faux pas. Unless the word absquatulation has been used in its correct context somewhere other than in this warning, it does not have any legal or grammatical use and may be ignored. No animals were harmed in the preparation of this post. Those of you with an overwhelming fear of the unknown will be gratified to learn that there is no hidden message revealed by reading this warning backwards, so just ignore that Alert Notice from Microsoft: However, by pouring a complete circle of salt around yourself and your computer you can ensure that no harm befalls you and your pets. If you have read this post in error, please add some nutmeg and egg whites and place it in a warm oven for 40 minutes. Whisk briefly and let it stand for 2 hours before icing.

Setting up a .NET Development Tree

Not new but worth mentioning anyway:

Mike Robert treats us to a detailed recipe for building up a development tree, from creating the initial directory structures through automated builds and unit tests. Available here (HTML) and here (PDF)

And even better, he wrapped up the advice into an automated tool which will generate everything for you: Tree Surgeon. A real time saver (if you are still developing with VS2003) ....

Published Wednesday, August 24, 2005 11:32 AM by Addys

Comments

# re: Setting up a .NET Development Tree

Wednesday, August 24, 2005 12:55 PM by Zachary Burns

Would you consider this still valid for Visual Source Safe 2005?

The reason I'm asking is we really cannot afford the huge price tag of Visual Studio Team System when it ships and are probably going to look at the new VSS or Subversion with the Windows clients.

I just wanted to see if the final shipping version of VSS has the same problems as 6.0d did with corruption, inability to remotely share and Unicode.

Your thoughts?

New Comments to this post are disabled

Santomania