It depends on your goal. I develop custom modules. I tried adding DNN to VSS but eventually abandoned it because it took a lot of work to keep the VSS image in sync with all the DNN updates. I found I rarely used the VSS image. Now I store the dlls and only the ones I reference. If you’re customizing the DNN core it may make sense to keep DNN in VSS. However you’d need to decide whether you want to keep everything or just the projects you customize. Two approaches work for me…
1) Mimic the development folder structure in VSS. Then when you do a get-latest and everything falls into place.
2) Use a flat folder structure, every project is at the same level in the hierarchy.

Over time I’ve grown to like the flat folder structure. Whenever I try something else I almost always end up reorganizing it later. Also, a Flat Folder structure is easier to create automated build scripts against. The following website is an excellent overview of how to setup source folders…

http://software.ericsink.com/scm/source_control.html

Brian

---

Qualtiy DotNetNuke modules and custom development; we've been serving the DNN community for over 2 years and have hundreds of satisfied customers. Let us serve you today.

I haven't used VS 2005, we actually switched from VSS to Vault. Typically, I don’t store anything in Vault that can be auto-generated from source code in Vault. So if I can build a .dll I don’t store it in Vault. In the case of DNN I only store the dlls (not the source) and only the dlls I reference in the build scripts. In Vault, I can mark a folder as Cloaked and it won’t be downloaded to my local machine. Does VSS 2005 have that capability? Will it let you get the latest version and clear the read-only flag?

---

Qualtiy DotNetNuke modules and custom development; we've been serving the DNN community for over 2 years and have hundreds of satisfied customers. Let us serve you today.