Fortress  Vault Pro November 1, 2010: SourceGear announced that Fortress 2.0 is now Vault Professional Edition 5.1 This demo is still using Fortress 2.0

Reference Video Demo: Documentation:

Why change? Why Vault? VSS Does not offer cheap branching, so we hesitate to create branches. Also does not support ActionScript type filenames which forced us to use Subversion for FLEX development. Now we straddle using two Version Control systems. Vault combines the best of VSS and Subversion and adds some enhancements of its own. Surveyed about 20 Version Control systems. Several are cheaper(free), Several are more powerful (AccuRev, Team Concert). Vault has by far the lowest learning curve, has the essential features and is priced competitively.

Features SourceSafe Integration Very Low learning curve. Works almost exactly like VSS. Includes all VSS key features: Share file/folder, Pinning, Repository data is stored in a SQL Server database Atomic Checkins Cheap and fast branch- Like Subversion. Merge Branches wizard make the job simple Line History, view the line history in VS Vault integrates seamlessly with both Microsoft Visual Studio and Eclipse.

Shelving: Shelve changes if you don’t want check in incomplete code (or waiting for code review) DiffMerge, integrated folder/files compare tool.DiffMerge Bug Tracking /Feature Requests Tracking / Working Items/ Change Sets. Can look for changes based on a Bug number.Bug Tracking Build Integration (Visual Build Pro support vault/fortress)Build Integration Folder Security (set access level for each users/groups) More : vault.html vault.html

Demo 1.To the website In the admin page, create two working Items 3.Show Vault Client GUI 4.Open a project bind by Vault (it can be done in either Client or VS) 5.Create a branch (client) 6.Modify some files in both branches 7.Shelve/unshelve my changes 8.Check in with select Working items 9.Merge branches using Merge Wizard (client) 10.View the change history, and line history