Any of my projects that previously were connected to SourceSafe now generate an exception that the plug-in is unavailable. Sure enough, there are no source control plug-ins installed.
Is this something that must be independently installed to access Source Safe Strange that this all worked just fine in Beta1.
SourceSafe plug-in in Beta2?
Hot Topic
- Graphics Example Strictly C#
- ReportViewer control - protected memory error when printing
- Anonymous Interface Implementations
- VSS Add-in Missing after Installation
- How to hide a ToolWindow next time VS Starts up.
- Problem with Specifying Command Bars
- Possible bug with .net 1.1?
- Unable to create Excel Workbook Project
- Optimization joint between 2 tables
- How do I draw a line using XAML?
Visual Studio
- ServiceHost Implementation has changed in WinFX Sept CTP 2005
- Background Picture
- InnerChannel.SessionId always null on the client proxy
- cannot find keycodev2.dll or Invalid Keycodev2.dll
- Getting XPath expression for an XMLNode
- ADO.NET (XML) Datasource Missing
- Deploying Crystal Reports Web Application
- OPENING A TEMPLATE IN WORD 97
- Import export settings
- Referencing Office XP PIAs
SourceSafe plug-in in Beta2?
Michael Mac
Hi,
Did you successfully install the Beta 2 product
If you installed only Visual Studio Pro, then you would need to install SourceSafe 2005 Beta 2 from the standalone setup.
-Alfredo
Douwe
I am not using Team Project yet so I don't really care about that.
Let me know, please!
thanks,
Darcy
DaveC#
If so, you might want to try re-opening your solution from source control to allow VS to regenerate its binding files.
--Oren