In our office we use CVS to manage the component/Designer codebase, and use a repository to manage our different workflow model versions.

CVS works well... when committing changes to a file, it attempts to "resolve" changes when other changes were made to the file in the mean time. It's also very easy to use when combined with the TortoiseCVS Windows Explorer snap-in.

I have seen other offices use SVN, and from what I see it looks and behaves very similar to CVS.

Thanks for the info. We will be using SVN. It will be nice with Workflow Enterprise comes out with the built in codebase.

We use SVN and Tortoise. They work great, but it seems like everytime I open a workflow the files change, even if nothing in the workflow changes. it will be nice when the repository in Enterprise is ready.