Is there an easy way to disconnect and reconnect a project in Visual C++ 6 from the sourcesafe
We have a very large project with lots of directories and subprojects. I branched the project to another directory tree, but VS6 insists on checking out from the original branch.
Is there an easy solution
Thanks,
Maor
disconnect sourcesafe from visual C++
Hot Topic
- Customizing "Search Page" in Document Explorer 8
- C# How to get Excel reference from Smart Tag Recognizer?
- Custom task with assembly reference
- Crystal Reports for Visual Studio 2005 RTM Release?
- SourceSave 2005 Install Problem
- Building custom lookless control
- Debugging Error Message of VS2005
- CheckBox bug when databound and IsEnabled="False", IsChecked="True"
- Keep-Alive in WCF
- Error "The system cannot find the path specified" on ASP .NET 2.0 webform based report.
Visual Studio
- Remote debugging a website with it's wwwroot on a share (UNC)
- Databinding in VSTO
- Custom image size possible in toolbar?
- Reporting Services 2005 - Textbox controls
- Does VSS 2005 have Netsetup?
- AssemblyInfoTask Request
- Project is not visible if always show solution explorer is unchecked
- "Could not read state file" warning
- Excel screen updates - real slow
- Can someone give me an example of how to set an image?
disconnect sourcesafe from visual C++
ddimitrov
If you script a little code to read the DSP and DSW files, you can scrub the control info very quickly. A DSW may have something like this:
Project: "ADORecordSet"=.\ADORecordSet\ADORecordSet.dsp - Package Owner=<4>
Package=<5>
{{{
begin source code control
"$/Enterprise/External_Interfaces/Source/ADORecordSet", OHAGAAAA
.\adorecordset
end source code control
}}}
Package=<4>
{{{
}}}
The pink part should be completely removed.
A DSP will have lines like:
# PROP Scc_ProjName ""$/Enterprise/Trunk/External_Interfaces/Source/FeedFileHandler", IRGGAAAA"
# PROP Scc_LocalPath "."
They should be changed to
# PROP Scc_ProjName ""
# PROP Scc_LocalPath ""
By "sterilizing" the project files, and deleting the VSS files that contain integration information, you can eliminate the incorrect VSS linkage in the branches.
Mickw
Unfortunately there is no easy way to do this.
In VS7 and later you could have used File/SourceControl/ChangeSourceControl dialog to rebind to the new location, but VC6 doesn't have this feature.
You can however attempt to do a manual Unbind, and then Re-add the projects in the new location. For the "unbind" part, you'll have to manually edit the dsp, dsw files and remove the source-control related information. Also, delete the opt, ncb, clw, mssccprj.scc files. If all is done correctly, reopening the worksspace in VC6 should show the project uncontrolled. Then, select the project file in FileView, and add again to source control. Point to the new location. VisualC will see there is already a project in the new location and will ask whether to reconnect to it. Say yes. Repeat for all projects and workspace. Then, checkout the project and workspace files, and make sure you select to leave the local files (otherwise they will get replaced with the store versions which still point to the old location). In the end checkin the new project/workspace files.
Alin