Visual SourceSafe - Organizing it all

Okay, I received tremendous help yesterday with my thread on how to set up and start using VSS.

Now I have all my aspx and aspx.vb source checked-in. I would like to ask for some advice on how to organize my stored procedures.

On the top of my VSS tree, I have a safe. Then I have one folder, let's suppose it is called "Application .NET". Under that I have a folder called Website1 (because like an idiot, I took VS's default name when I started my project. Oh well, what's in a name, anyway?) This is where all my VB and ASP.NET code is.

Parallel to Website1, I would like to create a folder called Scripts (I guess) and put there my .sql script file which contains all my CREATE PROCEDURE instructions. Yes?

I'm also struggling with the following. My new project is asp.net, but it is replacing a classic ASP web application. I am migrating the pages piecemeal. I've converted the login page to .net, and everybody logging in sees that page. But then, depending on the user id and password, some people go to .net pages and some people are still classic asp. I've had to change the classic asp pages to go back to login.aspx upon logging out, not to the obsolete login.asp. I also commented out a call to an ASP function that I rewrote in .NET. So if I have a file called home.asp and it's in \admin and there's also a different one in \subadmin, I want to have a structure in VSS to check in both these with their new .net-aware code.

I guess I just need advice on using VSS with other files than a VS project.

Thanks.

That's the beauty of VSS.... you can put anything in there you want. We use ours to store all of our SQL Scripts, development tools, documentation templates, as well as system developer documentation (definitions of look up tables and such - usually in Excel).

-tg

I second what tg has posted.

We literally have everything from programming code (in C#, VB.NET and VB6) as well as store procedures, Excel files, Word files, Text files, Visio drawings, and God knows what all else in VSS.

Its best to organize your vss so its got some logic to it.

.NET Code
-Client1
--SomeSolution1
---MyProject
----???
-Client2
--SomeSolution2
---etc

Other Code
-OtherFiles
-Database

Pictures
-My Pics
-Public Pics
-etc