visualsvn

Is there a way to migrate SourceSafe with HISTORY into a SVN ? Ideally I'd like to use VisualSVN Server, but I don't really want to lose my SourceSafe history. If I have to I will though. M4N A long time ago (it seems) I tried to migrate a SourceSafe DB to subversion using vss2svn , but finally gave up. There were several problems, IIRC: you have to make sure that the SS DB is consistent (e.g. Analyze does not find any problems or is able to fix them). it took a very long time to migrate the DB, because it was quite big. finally the migration failed due to some problems with parsing dates. I

Right now I am using Windows XP. If i just copy the whole repository folder in visual SVN, once the server is down, how can i restore it via the backuped repository folder? another better solution to backup and restore in visual svn ? by the way, any method for backup and restore in visual source control? You can just copy the entire directory in and out. Files is files, there's nothing magic about them. If you want to do something more complicated, like edit the repository contents in some way before restoring, then you need dump and load. svnadmin dump /path/to/repository | bzip2 -9c > svn

Our team (5-10 developers) plans to adopt Subversion for our .NET (Visual Studio) projects/solutions (VisualSVN Server, TortoiseSVN / VisualSVN). What is the best way to organize a new repository tree ? Is it okay to use one big repository or is it better to create different repositories for every solution / product line etc.? Our projects can be categorized this way (example): Main Product Line Main Web App Library 1 Library 2 ... Windows Client Another Windows Client Windows Service Tools Tool A Tool B Product Line 2 Software 1 Software 2 Product Line 3 App 1 App 2 Generally, you want to use

I'm considering using SVN for my .Net projects, and I'd like to know what plugins are available for integrating the source control capabilities directly into the Visual Studio IDE. I already know about the following Visual Studio extensions: VisualSVN , which seems great but is not free. It is implemented as a low-level VS package extension. Is anyone using it? AnkhSVN , which is free but I've heard it's a bit buggy. It is implemented as a VS add-in extension. Is anyone using it? are you experiencing problems? Edit: The 2.0 version is a complete rewrite and seems to solve the problem I've

Recently I am facing problem of commit to SVN. The SVN server I am using is VisualSVN Server 2.5.9 and the client is TortoiseSVN 1.7.12. At first, one user is having problem to commit files to SVN. But that user still can access to the repository and download the update. The second user on second PC is working properly. But today, the second user is having the same problem as the first user. Why is this happen? How can the problem be solved? Thanks. You can get the "Forbidden" error if your user account lacks access permissions to a repository or repository path; it makes sense to check

We have some files in our project that can't be merged and hence the files must be locked by the users before editing them. Is there a way to force the user to lock a file before editing? We are using Subversion and TortoiseSVN / VisualSVN. cadrian Two steps: put the svn:needs-lock property on those files. That way they are check out read-only when such a file must be modified, use the svn lock command and commit as usual links: http://svnbook.red-bean.com/nightly/en/svn.advanced.locking.html http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-locking.html Godsmith More specifically,

A problem has started occurring recently in which some new files added to the subversion repositories don't get pulled down to other clients after doing an Update. If I browse the repository with Tortoise I can see the file. I can then right click on it and select 'Update to revision', which will pull the file down to the client. Unfortunately this is very time consuming as there is no way to pull down all files in a folder - i.e. I have to do this for each file individually. The weird thing is, it doesn't occur with all files and it is not occurring on all client machines. I have tried