Is anyone successfully using the PushOK plug-in for Subversion with Dev Studio? Or ANY version control plug-in for that matter?

I've been playing around with the PushOK plug-in for a few days, and frankly, I'm pretty disappointed. Here's my findings -- I'd like to hear from others that have used it.

• It throws exception errors at almost every turn -- whether I'm actually doing something or not I get errors. But it doesn't seem to stop working...
  
• The status of certain files doesn't seem to stick. Sometimes a file says it's not controlled when it really is -- until I refresh and then it's magically back. Doesn't do it on all files, just some.
  
• Locks up and/or crashes my dev studio occasionally (like while I'm writing this).
  
• When adding items to a repository, you should be able to indicate which module (subfolder) in a repository you want to add it to. It lets you change the selection, but then says your changes won't be saved -- basically saying you have to use a SVN SWITCH command which the plug-in can't do. It ends up adding the file to the original folder selected, not the one you switched it to. This makes the organization of repositories terrible since it seems that ALL WebFOCUS code would end up in one folder.
  
• Similar to the above issue, you can't seem to switch repository URLs once you've got it connected to one either. In other words, you're first setup step is set and can't seem to be changed (that I've found).
  
• With a file checked out, make a modification and save it but don't check it back in yet it still changes the file on the WF server. I was really hoping it would behave more like a real version control system where the changes aren't happening in the production environment until you commit/checkin. What's the point of checking out/in if that's the case? (This may not be the plug-in's fault, but rather the nature of how WF works as a web server -- I'm okay with that, but still want to be able to modify code w/o messing up production).
  

For what it's worth, we've got the SVN repository deployed as a file folder, not on a webserver. We're also using TortiseSVN.

Overall, the plug-in is terrible quality, totally flaky, unstable, unpredictable, and gives the illusion of decent functionality that really isn't there. I'm pretty disappointed and really don't see any benefit of using the plug-in. (No offense to the original developers, I'm just fairly frustrated.) I'd rather just manually deal with the files via TortiseSVN by checking the files out onto my local harddrive and treating my local server like it's a dev server.

I'd like to hear your input -- maybe I'm too picky, but I don't think so. Maybe the way we're organized is not the best way to make it work properly -- I hope that's the case because that's probably easily changed. It sounds like the direction that IBI is recommending for SVN is to use PushOK and that's unfortunate -- I'd like to see IBI take a more intentional approach to the problem and try to solve it or find a better plug-in.

Sorry for the frustrated tone - I was just hoping for something much better (usable). I hope someone out there has had better luck than I have that I can learn from.
/rant

This message has been edited. Last edited by: Kerry,

Trav,

The main problem is that any plug in for Subversion to talk to the Microsoft SCC API will need to be closed source as Microsoft it protected by a non-disclosure agreement. This means that the open-source people can't get their hands on it to tweak it till it works.

PushOk is the main commercial SCC API plugin available that I can find, here are a list of other SCC providers for subversion - maybe one of these would help:

http://www.projxpert.com/WebHelp/Hosted_Tools_and_Servi...e_with_Projxpert.htm
http://subversion.tigris.org/links.html#ide-plugins

I don't actually Subversion with Dev Studio, but this is supposed to be a working SCC plugin - http://www.daveswebsite.com/software/tamtamsvn/index.shtml

If you are sure that pushok is at fault - and not some configuration issue, seeing as you have at least 3 levels between DS and subversion - then you might have some luck at pushok's knowledge base (http://www.pushok.com/tickets_public.php?group=5)

Hope some of this might help somewhat

Cheers

Stu

I haven't tried all of those, but I've tried a few. I did try TamTam and am not having any luck there either -- in fact I can't get it to work at all. I'm not 100% sure that it's pushok's fault, but I do think that it has it's issues. I'll see what I can come up with on their knowledge base, but I wanted to ask here first since there's a better chance that someone here was using it like I was.

Given that IBI's plan is to support that plugin going forward, I may have to just log a case and see where that takes me.

If anyone else has used PushOK or SVN, please chime in -- there has to be more of you out there...

Just pushing to see wether there is new information around.

I've been trying to use the pushok SVNSCC-Plugin as well as the Microsoft TeamFoundationServer SCC-Plugin.
Both of them seemed to work.

Until you lock the computer. After unlocking both plugins show an error message (which is quite hard to get rid off) and Developer Studio lost all information regarding Version control.

Restarting DevStudio solves the problem until the next lock.

We tried to trace the problem and it looks like the DevStudio closes the connection to the Version Control server upon locking.
When coming back, it does not reopen the connection but tries to access the items anyway and that seems to cause a crash in both plugins.

This way both of them are pretty much unusable.