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
  1. Home
  2. General Programming
  3. Visual Studio
  4. IDE and SourceSafe

IDE and SourceSafe

Scheduled Pinned Locked Moved Visual Studio
questionvisual-studiohelpannouncement
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C Offline
    C Offline
    Cesar Peralta
    wrote on last edited by
    #1

    Ok, i branched a project. That's what you do when you need to continue development but keeping a version for bug fixing. So i label it VERSION 1.2 branched and, at least from the SS administrator everything looked cool. Well, the time of the bug fixing came, and when we tried to open the branched project from Sourcesafe the dammed program kept linking the downloaded version to the original project not the branched one... reflecting all changes. Any ideas why is this happening? How can i solve this? No Matter where you are, there you are

    D 1 Reply Last reply
    0
    • C Cesar Peralta

      Ok, i branched a project. That's what you do when you need to continue development but keeping a version for bug fixing. So i label it VERSION 1.2 branched and, at least from the SS administrator everything looked cool. Well, the time of the bug fixing came, and when we tried to open the branched project from Sourcesafe the dammed program kept linking the downloaded version to the original project not the branched one... reflecting all changes. Any ideas why is this happening? How can i solve this? No Matter where you are, there you are

      D Offline
      D Offline
      dogby 0
      wrote on last edited by
      #2

      This was a problem with the visual C++ 6.0 as well Basically you cannot branch a visual studio project, without "modifying" the pointers within the project file(s) and workspace file(s). Visual studio 6 didnt do this properly, so the new project still had source safe pointers to the old location. The solution with VC6 was to manually edit the dsp and dsw files, or to use a really handy utility (which I'm not sure is still available) called fixworkspace. I havent tried to do this with VS .NET yet. I imagine you may be able to use "Change source control" to make it work

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

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