Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / General / September 2005

Tip: Looking for answers? Try searching our database.

Problem with SourceSafe Integration from Uninstall?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Cody Powell - 27 Sep 2005 16:45 GMT
Greetings all,

A while back, I installed Beta 1 of VS.NET 2005 to a machine that
already had VS.NET 2003 installed.  Today, I tried to open a C# project
with integrated Source Control settings through Visual Studio 2003.
When I pulled it up, I got a messagebox that said, "The beta period has
expired."  The only beta I had on the machine was for VS.NET 2005, so I
went ahead and uninstalled that.

Now, I appear to have lost all of the Source Control capability in my
VS.NET 2003.  When I go into Tools->Options->Source Control, it will no
longer allow me to set my Login ID or access any Advanced properties.
Furthermore, whenever I try to open a project that's already checked
into SourceSafe in VS 2003, I get a message saying that the
mssccprj.scc file couldn't be located.  The file is there, and I could
open it just fine before I uninstalled VS.NET 2005 Beta 1 (before the
beta expired, that is).

Does anyone have any idea what's going on here?  It seems to me that
during the VS 2005 uninstall, the Source Control integration options
were also removed.  If that's the case, how do I get them back into my
dev environment?  I checked the VS.NET 2003 setup and I didn't see
anything along those lines.  I'm really hoping a complete
uninstall/reinstall isn't needed.  Any help would be greatly
appreciated.  Thanks,

Cody Powell
Cody Powell - 27 Sep 2005 19:44 GMT
No response necessary here, as I've figured it out.  Uninstalling and
reinstalling Visual Studio .NET 2003 didn't fix the problem, but
uninstalling and reinstalling SourceSafe did.  Once I did that,
everything was suddenly better.

Cody

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.