Please note: This page has been retired.

You can find current information from the links below

If you need to buy a license for this specific version, please contact us for availability and pricing.

Other information on this page is shown for historical reference only and may have changed considerably since.

What’s new in PureCM Standard 2010-2b?

Enhancements

• Add 'pcm admin integ-tests' command.
• Add 'Permissions' menu on a project item to update the security without going to the stream.
• Warn when deleting a license that the original license is required for renewals.

Bug Fixes

• Child streams not appearing in stream history list.
• Intermittent client crash when creating a workspace via 'Start Task'.
• Errors when creating a feature stream with ':' in feature name.
• Projects files tab shows tasks when clicking on a project.
• Project item properties not showing 'Create From Parent' stream name.
• Edit issue window must be closed before changes are applied for mandatory fields.
• Fix potential server memory leaks.
• Handle exceptions better within PureCM.Client.
• Intermittent crash when working offline and viewing the history of a file.
• License expired message always appears on GUI startup.

What’s new in PureCM Standard 2010-2?

Major Enhancements

• Process automatic merge rules in background.
• Update .NET API to create, enumerate and complete projects, versions, and features.
• 64-Bit Windows Installers.

Visual Studio Enhancements

• Projects window.
• New 'Add To PureCM' dialog using projects.
• New 'Get From PureCM' dialog using projects and tasks.
• Save Visual Studio files before submit.
• Fix potential hangs after opening the file history window.

Minor Enhancements

• Add 'auto-encoding' file type option.
• Add 'disable line ending translation' file type option.
• Dont lock server database when performing a merge in the Resolve Tool.
• Friendly client messages when server is disconnected.
• Disable changing the encoding of an existing file type. You must create a new file type and update the relevant files.
• Open workspace view after switching a workspace.
• Get CruiseControl plugin working for CruiseControl.Net 1.5.
• Saved dialog positions work with mutliple monitors.
• Enable browse button when selecting a path in the Repository Import Wizard.
• Rename 'View My Changesets' policy to 'Developer User'.
• Default path for a release changed to 'Version Releases' folder.

What’s new in PureCM Standard 2010-1e?

Enhancements

• Update message when closing the Resolve Tool allowing you to save your changes.
• Resolve Tool allows you to add a combination of left and right changes.
• Resolve Tool allows to select lines within a conflict for copying.
• Add Undo toolbar button to Resolve Tool.

Bug Fixes

• Merge rules not being deleted when completing a feature.
• Crash when importing certain data into SQL.
• Visual Studio hangs when checking out certain files.
• Events and triggers stop working after calling begin-backup.
• Workspace path may appear truncated when creating/switching a workspace.
• Task report templates not being installed on Ubuntu.
• Linux client can hang when selecting a stream within the Merge Rule creation dialog.
• Resolve Tool labels are incorrect in some instances.
• Resolve Tool does not support shift and cursor keys for selecting lines.

What’s new in PureCM Standard 2010-1d?

Major Enhancements

• Support SQL Server for the server database.
• Support moving features where changes have already been submitted.
• Ability to switch a workspace which contains changes.

Minor Enhancements

• Access file data and diffs using the .NET API.
• Support merging changesets within the Projects view.
• Support managing shared components within the Projects view.
• Support project and version reject.
• Sort projects on priorty then name.
• Update resolve tool titles to include the stream name.
• Ignore 'bin' and 'obj' folders by default.
• Add 'text/utf-8-with-BOM' as default file type.
• Don't show permissions when creating a new report.
• Handle pcm begin-backup, end-backup and make snapshots with SQLite server database.

Visual Studio Plugin Enhancements

• Integrate with the Visual Studio progress bar.
• Open the Visual Studio editor when double-clicking a file in a PureCM window.
• Open a Visual Studio window rather than modal dialog for file diffs and history.
• Fix crashes/hangs in 'Add to PureCM' dialog.
• Better performance for checkout and revert of multiple files.

What’s new in PureCM Standard 2010-1?

• SQLite database support with up to 100% performance improvements.
• Performance improvements when adding a large number of files.
• GUI and Visual Studio refresh performance improvements.
• Projects View for creating projects, versions and features.
• Support for Visual Studio 2010
• Eclipse plug-in uses the PureCM changeset dialog.
• Component update does not create an edit change item for files which have not changed.
• Synchronise a stream to another stream.
• 'Synchronise to Changeset' workspace menu.
• Ability for 'Force Merge' a changeset which has already been merged.
• Better description for resolve tool when merging changesets.
• Confirm whether to delete the local files when deleting files in a workspace.
• Allow exclude on added folders and files within a workspace.
• Make Repository and Administrator Views policy based.
• Numerous Visual Studio enhanced plugin bug fixes

PureCM Standard Features
PureCM Standard is a cross platform client/server based source control solution, which is shared with PureCM Professional. On the server side, PureCM stores project data in a safe SQLite or SQL Server database for maximum security. Project data is stored in 'Repositories' that can scale to terabyte size. Administrators can manage multiple projects in a single repository to allow for code reuse, as well as creating multiple repositories to separate self-contained projects.

Multiple client types - Users can access project data using one of the full-featured IDE integrations for Visual Studio and Eclipse, including repository browsing and visual file and folder diffs. iIts cross-platform GUI is available for Windows, Linux, Mac and Solaris, and version control tasks can be performed in any tool supporting the MS SCC Interface. PureCM Standard also includes a command line client for task automation. Custom integration and advanced automation can be implemented using the tool's .NET and Java APIs.

Distributed development - Access to the server is based on TCP/IP, allowing any client to connect remotely to the PureCM server out of the box. PureCM also supports VPN connections and SSL/TLS encryption for added security.

Private workspaces - In PureCM, every developer works in a private workspace to isolate his work, facilitating concurrent development and enhancing quality. Using their workspace, developers can edit, checkpoint, build and test their changes locally – even when disconnected. To facilitate collaboration, developers get live checkout tracking and on-demand integration of colleagues' work.

Task-based development - PureCM uses changesets to group individual file changes that represent a task. Changesets are applied atomically and used throughout the development lifecycle. Code reviews, merges or continuous integration builds can all be based on submitted changesets.

Parallel development - PureCM facilitates parallel development by using stream-based branching. Therefore, branches are very lightweight and created instantly. Integrated branches or merged changes are automatically tracked throughout the complete project hierarchy, avoiding remerges and supporting parallel refactoring.

Build automation - PureCM offers out-of-the box integration with FinalBuilder and CruiseControl.NET to facilitate continuous integration. Custom integration can easily be implemented using the tool's .NET or Java SDK.

Security and authentication - PureCM Standard supports access control lists (ACLs) for any object stored in its database from project to file level. ACLs can be inherited throughout the repository hierarchy and defined for both user groups and individual users. Authentication is supported using Windows Domain Authentication, Linux PAM authentication, user/password or certificates.