Summary: Product feedback about ""Visual SourceSafe""
SeeAlso: ProductFeedback, VisualSourceSafe, VisualStudioSourceControlIntegration

Raves :-)

*bundled with VS.NET
*intuitive

Rants :-(

*let us have it
*here
*no integration into explorer (see http://tortoisesvn.tigris.org/ for explorer-Integration of subversion) - you have to use thirdparty addins..
*no atomic checkins
*no webinterface
*you have to analyze the database very often

Ease of Setup

It would be great if VSS was easier to setup. The interface is not very intuitive. I spent several hours trying to setup a simple DB for a small 6 person shop and ended up giving up because I could not figure it out. Perhaps a tutorial on how to setup the DB and clients would be very helpful.

Remote Access Support

SourceSafe requires a "domain topology" - which completely stinks when using it over the internet! If I'm working from home and not attached to a VPN, I want to be able to use sourcesafe using ONLY TCP/IP. No domains, no VPNs, no mess! Using web services to do this is a horrible idea - now I need to setup IIS in addition to a domain? AHHhhh :(

Poor administration tools.

By v6.0d, I would expect there to be some plugin that would be able to pull administrative information from an active directory. Instead, I have to duplicate a bunch of logins. You would probably be un-surprised at the number of people who assume VSS uses Windows NTLM or AD and then are shocked to find out it's a mostly manual process.

Release SCC from NDA

Why is the SCC/SCCI API under an NDA? Given the grassroots community Microsoft is targeting with the Visual Studio Express SKUs, wouldn't it make sense to release the API and allow developers to make plugins for things like CVS?