Source Control / Collaboration
-
We were a 100% classic ASP shop until perhaps a year ago when we started jumping into ASP.NET. We're finally at a point where we're comfortable enough with the language to start deploying production applications. But we're running into problems because of the way Visual Studio works with a complete local copy on the developer's workstation. There's nothing specifically wrong with the way it works, it's that we don't know how to handle multiple developers on the same project. We typically use Dreamweaver to directly edit copies of the files on the server via FTP. It's simple to connect via Dreamweaver, open up the ASP file, make your changes, save, and you're done, the new code is running live on the site. Right now, about all we can do is download a fresh copy of the ASP.NET site each time we want to make a change - obviously time-consuming. We all telecommute so we can't have the source code on a share that we can all access. Is there a product out there that will allow us to remotely synchronize our versions? I've seen the SourceGear vault, that seems like it might fit the bill. Does anybody have any experience with this product, or have any recommendations?
-
We were a 100% classic ASP shop until perhaps a year ago when we started jumping into ASP.NET. We're finally at a point where we're comfortable enough with the language to start deploying production applications. But we're running into problems because of the way Visual Studio works with a complete local copy on the developer's workstation. There's nothing specifically wrong with the way it works, it's that we don't know how to handle multiple developers on the same project. We typically use Dreamweaver to directly edit copies of the files on the server via FTP. It's simple to connect via Dreamweaver, open up the ASP file, make your changes, save, and you're done, the new code is running live on the site. Right now, about all we can do is download a fresh copy of the ASP.NET site each time we want to make a change - obviously time-consuming. We all telecommute so we can't have the source code on a share that we can all access. Is there a product out there that will allow us to remotely synchronize our versions? I've seen the SourceGear vault, that seems like it might fit the bill. Does anybody have any experience with this product, or have any recommendations?
Check out Microsoft's Visual Source Safe: http://msdn2.microsoft.com/en-us/vstudio/aa718670.aspx[^] It integrates nicely with Visual Studio which is good for .Net, or take a look at Tortoise SVN here: http://tortoisesvn.tigris.org/[^] which integrates nicely with Windows Explorer
-
Check out Microsoft's Visual Source Safe: http://msdn2.microsoft.com/en-us/vstudio/aa718670.aspx[^] It integrates nicely with Visual Studio which is good for .Net, or take a look at Tortoise SVN here: http://tortoisesvn.tigris.org/[^] which integrates nicely with Windows Explorer
Sourcesafe is universally acknowledged as the worst versioning software ever created. MS doesn't even use it. (My last experience there was with SourceDepot, which is a customized version CVS, iirc). We happily use Subversion. Tortoise is just a GUI front-end to Subversion, which is commandline in nature. There is also a Visual Studio interface to Subversion, called Ankh.
-
Sourcesafe is universally acknowledged as the worst versioning software ever created. MS doesn't even use it. (My last experience there was with SourceDepot, which is a customized version CVS, iirc). We happily use Subversion. Tortoise is just a GUI front-end to Subversion, which is commandline in nature. There is also a Visual Studio interface to Subversion, called Ankh.
sherifffruitfly wrote:
Sourcesafe is universally acknowledged as the worst versioning software ever created.
Unfortunately my superiors at work have not yet been convinced of this. For them it serves it's purpose without screwing things up, so we still use it.
-
sherifffruitfly wrote:
Sourcesafe is universally acknowledged as the worst versioning software ever created.
Unfortunately my superiors at work have not yet been convinced of this. For them it serves it's purpose without screwing things up, so we still use it.
Reasonably clarifying: http://en.wikipedia.org/wiki/Microsoft\_Visual\_SourceSafe