Julian- After migrating from one repository in CVSNT to individual repositories under VisualSVN, our users wanted all the projects back under one repository. You can definitely do this -- you just need to create a top-level repository and specify the parent directory within it when you import from a dump file. For example:
export to dump file: C:\VisualSVN\bin\svnadmin dump C:\svn\ProjectA > D:\svn\ProjectA.dmp import from dump file: C:\VisualSVN\bin\svnadmin load --parent-dir ProjectA D:\svn\SingleRepository < D:\svn\ProjectA.dmp Note that you will need to create the parent directory under the top-level repository, which is easily done with a right-click in the VisualSVN management module. When you do checkouts, you just have to navigate to the directory you actually want (as you are used to doing). I'm not sure if that will give you the URL you want, but there may be some more fiddling that will take care of this. HTH, David Beahm Julian Easterling wrote: > I currently have a custom SVN/Apache installation set-up that uses > https://server/svn/projectname/trunk. It is only one repository and > each different "projectname" is just a folder under the one repository > located at https://server/svn/. Each time I look at VisualSVN, I > notice that the install requires that each folder at my "projectname" > level to be a repository. I have a lot of "projects" and do not want > to have to create repositories for each new one nor do I want to > create a "svn" repository so that my URLs would be > https://server/svn/svn/projectname/trunk... > > Is there a way to have VisualSVN to work with just the base > Repository? If not, is there any plans to add this as a feature? If > there are no plans to add this feature, is it possible to "extract" > the authentication modules for use in a custom SVN/Apache > installation. > > Julian Easterling > >
