We almost had a similar problem where I work. Fortunately bzr's command-line tools are very nice to use (especially compared to subversion), so a few scripts and some tutorials later and most of the devs here are happily working on local bzr branches connected to a central svn trunk. If your project shied away because of lack of VS integration, I'd be interested in which specifics were significantly (or even slightly) more difficult with command line tools & a good wiki vs. visual studio integration...? Without knowing what these specifics are, it would take quite a lot of effort to get even slightly close to the integration projects like ahnksvn offer for subversion. <div class="gmail_quote">On Wed, Jul 7, 2010 at 3:31 AM, Guy Gascoigne-Piggford <<a href="mailto:guy@wyrdrune.com">guy@wyrdrune.com</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> > Couple of months ago I've tested beta of Visual Studio integration. It's > called uniscc -- UnifiedSCC. It's not open sourse IIUC. > > But in general you're right. There is no integration because nobody working > on this. And nobody working on this because nobody interested too much. > And... sadly we had a .net project (at work) switch from bzr back to svn purely because of the lack of integrated tools. So there are folks who would be interested if it existed, but the lack is just forcing some people away from bzr. > hg beats bzr here. > > > </blockquote></div> -- Philip Peitsch Mob: 0439 810 260