I look forward to trying out the new version of SourceSafe. As a development team we have been flustrated by the lack of web support in the current version and have moved to using SourceGear Vault for our distrubted development teams.

Is microsoft going to release a beta or preview of VSS 2005 throught MSDN Downloads? I am also interested to know if it was developed from scratch o use the VSS code base.

Thanks,

Patrick

Let's hope they've firmly ditched the existing codebase and written it from scratch, including Sql Server storage capabilities.

I suggest simply using Perforce instead of SourceSafe. It would take years for SourceSafe to come to par with Perforce.

I'd like to see VSS adopt the "changelist" metaphor from Perforce so that a group of files can be checked in/out as part of a single logical change to the project.

I realize that the "View>Search" mode of VSS will let you list all of your checked out files and let you check them all in at once with a comment, but once your checkin is complete, there is no relationship between the files except for their common comment, and comments are relatively useless for the purpose of grouping files to examine a logical project change.

Related issue: Viewing "All files checked out to me" is too common of a need to have it under a view mode that you have to switch to.

I think VSS for our environment is quite good.
But the integration with VS.NET 2003 is frustrating, sometime doesn't get new versions, sometimes the link to VSS disappears, and I need to restart VS.NET.

Also would be nice merge-like function that allow not to lock the file (live CVS)

I concur with sloppycode, we definitely need to see a better integration with SQL Server as a storage repository.

Another issue I would like to see resolved is the incorporation of meta data, i.e. such aspects as tracking bug report information through VSS and keeping statistics on them.

VSS needs to support the concept of a "release," whereby you can patch an older version of your app while still working on a newer version.

This should also allow you to merge changes from the older version to the new, or keep the changes at the older version if necessary. (e.g., Continuus)

The way VSS works now, it is difficult to patch any but the most recent build of your app.

If it can have a report type function to indicate the file changes, by who and by date and time(or date range) it would be nice. This will make Code reviews much easier in a development team of 5+

Yep These functionalities are really major changes in VSS 2005....
~~~~~~~~~~~~
- More highly refined and integrated version control system which helps new and expanded capabilities for teams and individuals
- Use Visual Studio to connect to Visual SourceSafe databases from anywhere in the world where HTTP or HTTPS Web access is available
- Enhanced Performance provides significantly faster access speeds for common operations
- Data storage capacity is increased to 4 GB
- Customize the user interface with any specified language and font.
- Use the new plug-in editor/viewer feature to compare and view source code and document differences using any third party or custom tool.
- Managed Code Extensibility
- Use events, such as OnBeforeCheckout or OnAfterCheckIn to automate your process. Leverage the new MSBuild tool by creating custom tasks that retrieve and download source code files before building them with an automated build.
- Unicode and XML Support
- Check Out Improvements - Within Visual Studio, check outs are now automatic and prompting is reduced.


and so on..........

~~~~~~~~~~

Why have a limit on the storage capacity?

To me it sounds like the internal design is bad and that it should be redesigned.

where could I get vss from now?

1) I'd like to have VSS integrated with MS SQL Server tools (EM and QA)for developing stored procedures, UDF, triggers, SQL query, DTS packages ...
2) New version of VSS has to support old versions of developer tools like VB 6, VC++ 6. Or it has to give me possibility to install and use new version of VSS in a parallel with old one.

Why not give MKS source integrity and integrity manager (bug tracker) a try. There is no other product on the market that can beat the MKS enterprise offering...

SQL Server SQL Server SQL Server SQL Server SQL Server SQL Server SQL Server SQL Server

VSS is unreliable. Please scap existing code base and start over. Thank you.

FYI - atomic check-ins are a requirement.

VSS is not unreliable *IF* it is maintained. I have automated scripts that do analyze and fix operations weekly. Our VSS databases are backed up nightly.

As far as the size limit, I have VSS databases that have approached 10GB without major issues. Yes the ran faster when we were able to archive older information. With a good maintenance plan though it is possible to run a world class VSS database without fear.

Thank you kindly,

I don’t care about new features. All I care is that the darn thing works properly with the current features. I frequently get messages telling me that there are writable copies of files being checkout and if I would like to replace them (WHY???). Some time I check files in and only the source safe status changes, my FILE changes are never reflected in source safe. VERY frustrating.

Is there a list of planned features/upgrades/patches for VSS 2005?

Looking at the 'new features' I get the feeling that they've just dusted out the existing codebase and baked in some extra's on a rainy sundayafternoon. This is not at all a compelling upgrade. I'll stick with SourceGear Vault thank you.

Didn't you guys read the "roadmap" link at the top of this page? VSS is for individual developers or very small teams. Microsoft is releasing "Visual Studio 2005 Team System" for real development teams. It should say something about VSS that very few development teams at Microsoft have ever used VSS, and most now use something called "Source Depot", which is really just the licensed codebase of Perforce.

Jamie