Support custom directory structure
Add support for custom directory structure, like this one :http://blog.jpboodhoo.com/DirectoryStructureForProjects.aspx where not all files are part of the solution, or where .sln file is not even in the root folder.
Krzysztof Koźmic
shared this idea
Currently it is required that the solution is located somewhere inside your workingcopy. Placing it in the root (or above your projects) can be usefull for finding the solution, but is not required. It is not even required that you commit your solution (but we recommend you do).
Can you explain what you are trying to do, what you can’t do today?
2 comments
-
Tobias
commented
I fully agree!
We also need complexer directory structures then default,
especially the need of *custom* subdirs (see example).
We want to use Ankh to add an existing Project
to a complete custom path to the repository.Example: Our project is named ProjectA
and We want a repository structure like this:/root/container/projectA/doc/trunk
/root/container/projectA/scr/trunkand so on for depending projects...
Currently I cannot use Ankh to add an existing Project to
/root/container/projectA/scr/trunk !
To do this is not trivial at the moment and I can't see a good reason for that!Please add this little bit of code to ankh, It should not be that hard..
-
Krzysztof Koźmic
commented
I'm talking about situation where sln IS part of solution but is not in the root like:
root/src/app/MyApp.sln
I may also have
root/lib/(some files)
root/tools/(some files)
To update lib or tools, currently I have to go out of VS and use Tortoise, because those files are not part of the VS solution (although they are part of solution in the wider sense).
I'd love if Ankh could track these too.
