Setup projects are already supported. But this project type requires that you mark it as managed by Subversion before it shows glyphs.

(The Visual Studio SDK doesn’t document projects must or must not support SCC without a hooked SCC provider; so some projects do (C#, VB, C++, etc.) and some projects don’t (Setup, Sql, etc.)

Subversion promotes merging on conflicts over pre-emptive locking.

If you have files where this doesn’t work (like some document formats) you can add a svn:needs-lock property which will require users to obtain an exclusive subversion lock before editting and committing this file. AnkhSVN will handle files with this property in the same way as Visual Sourcesafe handles all its files.

Fully locking out other clients can only be handled on the repository side. This svn:needs-lock handling is probably the best we can do on the AnkhSVN level.

Can you add an issue on our issuetracker to track this feature request?

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 users@ankhsvn.open.collab.net list if you have further questions.