1 / 6

Fortress  Vault Pro

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. http://www.sourcegear.com/ Video Demo: http://www.sourcegear.com/video/index.html

Download Presentation

Fortress  Vault Pro

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 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

  2. Reference • http://www.sourcegear.com/ • Video Demo: http://www.sourcegear.com/video/index.html • Documentation: http://www.sourcegear.com/vaultpro/documentation/

  3. 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.

  4. Features http://www.sourcegear.com/vault/ • 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.

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

  6. Demo • To the websitehttp://udiply4451.unitrininc.unitrin.org/VaultService/ • In the admin page, create two working Items • Show Vault Client GUI • Open a project bind by Vault (it can be done in either Client or VS) • Create a branch (client) • Modify some files in both branches • Shelve/unshelve my changes • Check in with select Working items • Merge branches using Merge Wizard (client) • View the change history, and line history

More Related