The project paths that are stored in the solution will be per user overridable in the near future. (Best guess +- January 2009). This is part of the enlistment support planned for some time. It is recommended to share the solution file (especially on websites as the .sln actually contains the project references). AnkhSVN can’t redesign the Visual Studio project model, but we will try to implement optional parts of the SCC specification with some more user configuration options than other products. (e.g. allow customizing most user project paths, while TFS and VSS only allow editting enlist enabled projects).
Please contact me via the firstname.lastname@example.org list if you have further questions.
Currently a patch file can’t express all information in a working copy. A new feature partly available in subversions trunk should make it possible to fully capture all changes (including copying and renaming files) in the new svnpatch format.
A full implementation of this feature will probably require Subversion api changes that are scheduled for 1.7 or 1.8.
Fix is planned for the next release
We currently recommend that we add files like this with operation ‘none’ to the project (or to a special project for these files: e.g. solution folder or C++ makefile project).
We are looking into extending this for future versionsgbjbaanb commented
Surely you can just add a new folder in the solution and add the files to that, then Ankh can manage them just like the others, and you can see their status etc as for any other file. I add readme and other files to my solution in a 'Documents' project folder, it works well and is a much better fit than extending Ankh to track files not under visual studio control.
Can you add an issue on our issuetracker to track this feature request?