Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
N

nicsys

@nicsys
About
Posts
1
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Source Control / Collaboration
    N nicsys

    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?

    C# csharp asp-net visual-studio sysadmin collaboration
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups