I previously was developing with VS 2003 and VSS 6.0d, then I tried installing Beta 2.0. I realized that my VS 2003 is now using VSS 2005 (integrated with it) and as a result, I am having a number of problems with my previous project under source control. Show differences produces a number of exceptions which I have found in the newsgroups (for previous versions of VSS) is a result of having 2 versions.
What should I do to revert the configuration of my VS2003 to use VSS 6.0d instead I couldn't find any options from VS 2003 menus. Or should I continously use VSS2005 and just have to do something
VS 2003 with VSS 6.0d after installing Beta 2.0 of VS 2005
Hot Topic
- How to update PropertyGrid after changing type
- Capture association events
- Expander control
- Adding drop down list control to an Appointment Form
- Default browser for Visual Studio
- Unable to Reference office.dll in VS 2005 project
- Register for COM Interop
- Odd behavior on explicitly calling a custom Sharepoint Web Service from Infopath
- Word 2003 with VSTO 2003 stops working when .Net Framework Beta 2 is installed
- December CTP Installation trouble
Visual Studio
- Username credential without windows account
- MouseDown event in an image
- TabControl and ItemTemplate
- FileProperties2 interface in VsSDK ProjectBase
- Installation Problem - VS2003
- Programmatically Expand/Collapsing items in TreeView
- Implementing the silent check out feature.
- Hardware acceleration of WPF on XP
- Does ReportViewer run in Medium trust ?
- commandbarbutton click event doesn't fire on client machine
VS 2003 with VSS 6.0d after installing Beta 2.0 of VS 2005
DarkCat
You can open a command prompt, go to the VSS 6.0d install folder and run "regsvr32.exe ssscc.dll" and "regsvr32.exe ssapi.dll" (or if you want you can reinstall the VSS 6.0d from CD)
Then close and reopen the VS2003 shell and it should use the VSS 6.0d provider.
Alin
Ray Myers
thanks a lot guys!
Chris Anderson
Beta 2 installs visual source safe as part of the installation, just put your dvd and click add or remove vs 2005 components and remove visual source safe, after it I would reinstall visual source safe 6.0 d and analyze the database.