 |
|
| FriendFeed is the easiest way to share online. Learn more » |
Travis Koger
I like VS2010's new Repository Explorer, SVN appears to be working smoothly in it, even with what I thought was going to be an incompatible AnkhSVN plugin. No probs there. Mmm, didn't bring through Beyond Compare settings from VS2008.
October 19
- Comment
- Like
- Share
Roberto Bonini liked this
So you can commit to svn fro within VS now??
- Roberto Bonini
from iPhone
You always could with AnkhSVN. Been doing that for a long time. But the Repo Explorer, I have just linked directly to SVN across the net and it came through perfectly.
- Travis Koger
Even has its own History Viewer. Not sure if it is better than AnkhSVN yet though.
- Travis Koger
Yeah. I knew about the VisualSVN guys. Didn't know about AnkhSVN tho. But sounds awesome.
- Roberto Bonini
from iPhone
I am using TortoiseSVN, VisualSVN Server and AnkhSVN in VS2008.
- Travis Koger
Thanks. Will try out ankhSVN in the morning.
- Roberto Bonini
from iPhone
The VS2010 Repo Explorer doesn't really get SVN though, still using the 'CheckOut' terminology.
- Travis Koger
http://ankhsvn.open.collab.net/servlet...
- Travis Koger
Thanks Travis.
- Roberto Bonini
from iPhone
Hey check your DM Roberto.
- Travis Koger
Thanks Travis.
- Roberto Bonini
from iPhone
No probs.
- Travis Koger
Travis, the VS2010 Repo Explorer, is that the one provided by AnkhSvn that's not working? You should also be able to use File -> Open -> Subversion Project.
- Sander Rijken
As far as the diff/merge settings are concerned, they are stored per VS instance so VS2008 can have a different one set than VS2010
- Sander Rijken
Sander, yeah actually I think it might be the AnkhSVN repo explorer rather than a built in one. There is also the open Subversion Project.
- Travis Koger
It's definitely the one from AnkhSVN then :) sounds like we're integrating seamlessly there :-)
- Sander Rijken
Sander, yeah it works really well actually, although I have been having regular crashes in VS2010 though working with WPF projects, now in the habit of saving after every change I make. Haven't sourced the problem yet but I am searching though.
- Travis Koger
from iPhone
If you want to help out, use Tools -> Attach to process from a second VS instance, just do your work until it crashes. Then inspect the exception, and report an issue at connect.microsoft.com (if not a known problem ofcourse). If it's a valid issue it'll most likely still be addressed for the final version
- Sander Rijken