A question about sharing
-
A question about sharing and sourcesafe For quite a long time, we have settled for having our VS.NET projects on our local machines. But now we have started a very large project, and we need to find a solution that lets us work on the same project at the same time. And we also want to be able to manage the files with Visual Sourcesafe. The project is, of course, an ASP.NET application, so it has to be possible to debug on the shared webserver. Please help a simple programmer who can't handle anything else than code :-) I guess it's possible to get all this using Visual Sourcesafe combined with VS.NET, but I need to be guided step by step, consider me a child :rolleyes: "After all it's just text at the end of the day. - Colin Davies "For example, when a VB programmer comes to my house, they may say 'does your pool need cleaning, sir ?' " - Christian Graus
-
A question about sharing and sourcesafe For quite a long time, we have settled for having our VS.NET projects on our local machines. But now we have started a very large project, and we need to find a solution that lets us work on the same project at the same time. And we also want to be able to manage the files with Visual Sourcesafe. The project is, of course, an ASP.NET application, so it has to be possible to debug on the shared webserver. Please help a simple programmer who can't handle anything else than code :-) I guess it's possible to get all this using Visual Sourcesafe combined with VS.NET, but I need to be guided step by step, consider me a child :rolleyes: "After all it's just text at the end of the day. - Colin Davies "For example, when a VB programmer comes to my house, they may say 'does your pool need cleaning, sir ?' " - Christian Graus
1.) Make sure appropriate version of SourceSafe client is installed on developer machines. 2.) Put together ONE master of the code on one machine, so that the IIS virtual directory can be removed from the other developers computers. (This master can be removed once the project is safely (!?) stored in SourceSafe.) Steps 3 to 5 are done on one computer only. This is to create the project in SourceSafe, and copy the contents. 3.) To copy the source code from one machine into SourceSafe, open the project in VS.NET. 4.) In VS.NET, select: File | Source Control | Add Solution to Source Control... 5.) The SourceSafe integration in VS.NET will prompt you about different stuff, like filesharing vs. frontpage extensions, and where in SourceSafe to put the project... I guess you'll figure out what to do from here. Steps 6 and later are done on all the other developers computers. 6.) Remove the IIS virtual directory that contains the PRE-SourceSafe solution. (After backing up its contents!) 7.) Load the project from SourceSafe by selecting (in VS.NET): File | Source Control | Open From Source Control... 8.) Select your solution from there, and again: I guess you'll figure out what to do from here. There ARE other ways of doing this, without removing the IIS virtual directory. Changing SourceSafe bindings later on is an option, but I wouldn't recomend that with an ASP.NET project.
-
1.) Make sure appropriate version of SourceSafe client is installed on developer machines. 2.) Put together ONE master of the code on one machine, so that the IIS virtual directory can be removed from the other developers computers. (This master can be removed once the project is safely (!?) stored in SourceSafe.) Steps 3 to 5 are done on one computer only. This is to create the project in SourceSafe, and copy the contents. 3.) To copy the source code from one machine into SourceSafe, open the project in VS.NET. 4.) In VS.NET, select: File | Source Control | Add Solution to Source Control... 5.) The SourceSafe integration in VS.NET will prompt you about different stuff, like filesharing vs. frontpage extensions, and where in SourceSafe to put the project... I guess you'll figure out what to do from here. Steps 6 and later are done on all the other developers computers. 6.) Remove the IIS virtual directory that contains the PRE-SourceSafe solution. (After backing up its contents!) 7.) Load the project from SourceSafe by selecting (in VS.NET): File | Source Control | Open From Source Control... 8.) Select your solution from there, and again: I guess you'll figure out what to do from here. There ARE other ways of doing this, without removing the IIS virtual directory. Changing SourceSafe bindings later on is an option, but I wouldn't recomend that with an ASP.NET project.
Thanks, I'll give it a try! "After all it's just text at the end of the day. - Colin Davies "For example, when a VB programmer comes to my house, they may say 'does your pool need cleaning, sir ?' " - Christian Graus