Name of the blog

Short description of the blog

PureCM 2009-2 beta available now

We have had an encouraging amount of feedback for the public betas we published for our last 2009-1 release. So of course we’re going to do it again for the upcoming 2009-2 release!You might have already read about some of the enhancements that you will get with PureCM 2009-2; if not, here are the bigger chunks:
  • Enhanced Visual Studio 2005/2008 integration
  • New Windows Explorer plugin
  • Bulk merge and rollbacks directly on the server

With this current beta, you will now be able to test the first two enhancements yourself. Both the enhanced VS integration and the Explorer plugin are included in the PureCM client installer to keep installation as easy as possible. If you want to select them individually, simply choose the “Standard” installation.

>> Download the PureCM 2009-2 beta [link removed]

What can I expect from these enhancements?

Tim has covered the new Visual Studio features with his blog in detail, but we’re really quite excited about it so here they are again:

  • No binding of solutions needed. This makes it much easier to add a new solution to PureCM or to get a source controlled solution from PureCM.
  • Embedded PureCM views. You can now display both the “Workspace explorer view” and the “Workspace changeset view” known from the PureCM GUI to manage your changes; plus you will get a PureCM toolbar to easily access the most common operations.
  • Perform advanced workspace operations. Embedding the workspace explorer view allows you to access operations such as rebase, workspace merge (merging changes from other streams into your workspace), shelve and unshelve etc. etc. – just have a go with the “All tasks” operations from the context menu  ;-)
  • Organise checkouts using changesets. Create one or more changesets to group your ongoing changes/checkouts directly in Visual Studio.
True, not everybody is working with Visual Studio, and we have had quite a number of requests for a basic integration into Windows Explorer. This plugin is particularly useful when working with many different tools, but without having the need to access advanced GUI features. This is what you get with this beta:
  • Get files from PureCM (i.e. creating a workspace)
  • Add files to a folder/workspace under version control
  • Checkout files and Submit changes
  • “Check consistency” to automatically detect changes when editing files without checkout
  • Support for namespace changes
  • Access file history
  • Visualisation  to show file differences and resolve conflicts (should they occur)
There are some features excluded from this beta which will definitely make it into the final release:
  • Add folders and files to version control as a new project/stream
  • Status icons for files under source control

So much for theory. To get a hands-on experience, download the beta installers, run them... and let us know what you think. Any feedback is highly appreciated.

>> Get the PureCM 2009-2 beta [link removed]

To send us your feedback, simply comment this blog or send an email to Have fun!

New FTP Deployment Service beta

Why using the deployment service?

There is more than one way to get the project files stored in PureCM to a target machine:

  1. Use the PureCM GUI and create a workspace in your target location
  2. Use the command line client to create a workspace in your target location

Both options will create a local copy of the project files on your target machine; so that looks like a perfect way to achieve your goal. In fact, most build tools pull the latest project version that way.

However, both solutions involve installing at least one of the above clients on your target machine, and somehow triggering “update to latest”. ‘Mhmmm, I might not like that for my production environment,’ you say. ‘But I can see that this might be useful for my web developers.’

So this is where the FTP deployment service comes in. Instead of pulling the files to your target location, the deployment service pushes them there. Because it can listen to changes submitted against a stream, it’s capable of deploying them automatically. Stephen has already wrote a nice article on how you could use this service for web development.

How does it work?

The example below shows a possible setup using the FTP deployment server:

  1. A developer submits a change to project 1, which is under source control in PureCM
  2. The development manager merges the change to the deployment stream, which is the base stream for the FTP deployment service. Note that the deployment service can run on the same or a different machine as the PureCM server.
  3. The FTP deployment service listens for changes and gets the change into his workspace.
  4. Only changed files and folders are sent via FTP/SFTP to the target location.

Of course, this is only an example, but I’m sure you get the idea.

Getting the beta download

So now you know about the FTP Deployment Service, why not download the beta and tell us what you think? Is there a feature you miss, or a bug you found? Simply comment this blog or email us your comment to

Learn more >>

Download the FTP deployment service >>

Here it is - the PureCM 2009-1 Beta

This update is to highlight that the download links below now point to the latest 2009-1 RC build.


New features

PureCM 2009-1 comes with two major enhancements:

  • Live merge tracking. This powerful feature gives you live and instant transparency about which changes need merging between two streams. Whether you want to push a bug fix back into the development stream or integrate a number of feature streams into your mainline, you can perform all operations directly on your stream without the need to create a workspace. After that, all merges are tracked for full transparency.
  • Task-centric GUI. As a developer, you spend 90% of your time in your workspace. As a manager, your focus is on the project stream. The new task-centric GUI gives you exactly the information you need for your task – not less, and not more.

Further 2009-1 enhancements supporting parallel and distributed development:

  • Workspace Rebasing. Easily switch the content of your workspace to any stream, be it a branch or a snapshot.
  • Deployment Service. Automatically transfer changes to your production environment without installing a PureCM client.
  • PureCM Components. Share libraries across projects to keep them in sync and control change with repository-wide file locking.

Click here to find a more detailed overview about PureCM 2009-1.

How do I best install the PureCM 2009-1 beta?

Note that you need to install both the server and client components of the PureCM beta to test the new features. Depending on your current use of PureCM, you might want to choose one of the following options.

Your current situation

Possible PureCM setup

Download links

I am new to PureCM and have no PureCM components installed yet.

Get the PureCM server and client installer for your OS and follow the on-screen instructions.



Combined client and server

Client installer

Server installer

Eclipse plugin


I am currently evaluating an older version of PureCM, but do not use PureCM for production.

Note that only one version of PureCM can be installed at any one time on a machine. You can thus choose to install the PureCM beta on a clean machine or uninstall your current PureCM version and replace it with the beta.




Please use the links above.

I am already using PureCM for production.

Option 1: You install the PureCM server on a clean machine for testing purposes. Download the .ZIP beta client and run it alongside your current production client when testing (no installation of beta client needed)



Client ZIP

The ZIP client can only be used if you already have a PureCM client installed on your machine.


Please use the links above to download the server component(s).


Option 2: You install both the PureCM server and client on a clean machine for testing purposes.



Please use the links above.


The system requirements are identical to previous PureCM releases and can be found here.  Note that this is a beta product. We would therefore advice that you do not use it on production data.


We are highly interested in getting your feedback, both the good and the bad. This allows us to tailor PureCM’s features to your needs and fix bugs that might have escaped our internal testing. Please send any comment or bug report to, or comment this blog directly. Thank you for your valuable feedback!