views:

43

answers:

2

I have a .NET solution which was badly organised, so I moved some projects around to appropriate folders. In the solution, I simply fixed the paths to the new locations, and everything is working in my working copy.

I used AnkhSVN to commit the solution to the repository, which worked out fine as well.

However, when I look in the repo explorer, the folders inside are organised in the old way.

What do I need to do?

A: 

If you are using Visual Studio you are not creating folders but filters. Filters basically allow you to organize your solution visually but in the background the folders will stay in their original location.

Kolky
not true if you are using the 'show all files and folders' option, then the VisualStudio explorer behaves like a normal explorer
stijn
True, but this is not the default behaviour!
Kolky
This behavior differs between different project types. C# and VB projects usually have the same layout on-disk and in-project, while VC++ really uses filters. (There is no standard or even a generic API that defines if filters are folders)
Bert Huijben
+2  A: 

Subversion uses metadata files in your solution folder structure to keep track of where stuff is, and where it maps to in the repository - these files are typically held in .svn or _svn folders in each solution folder and subfolder. Even though you may have physically moved things around in your working copy, those metadata files still point to the original structures in the repository.

What you could do (and please, anyone with deeper Subversion knowledge than I pipe-up if there's a smarter / better option) is re-organise the folder structure in the repository through RepoBrowser. Once you've got things where you want them in there, you can check-out a new working copy. The metadata files will then reflect the new repository structure.

Jonners
Tried this, it worked. Seems a bit manual, but it works.
Carlos
Agreed, it's a manual process and I don't know if there's a smarter way to do it - I think the intent is that the Subversion repository structure should be the 'right' layout, and it should be independent of however you might want to map your working copy structure. The flipside is that you can't change the repository structure just by tweaking your working copy - you've got to re-organise the 'master' and take a new copy.
Jonners