Krzysztof Koźmic
-
3 votesduplicate ·
Adminsrijken
(Admin, AnkhSVN & SharpSvn Projects) responded
Krzysztof Koźmic
shared this idea and gave it 3 votes
·
-
58 votesstarted ·
Adminrhuijben
(Bert Huijben, AnkhSVN & SharpSvn Projects) responded
Support for (optionally) automatically running TortoiseSVN pre-commit and post-commit hooks will be added within the next few weeks.
Krzysztof Koźmic
gave this 3 votes
·
-
46 votescompleted ·Adminrhuijben
(Bert Huijben, AnkhSVN & SharpSvn Projects) responded
Current AnkhSVN versions have support for our own issuetracker addin api.
The Visual Studio SDK license requires that addins of addins such as AnkhSVN are proper addins of Visual Studio themselves (E.g. sub-addins have to accept the Visual Studio SDK license).
A sample implementation to use as the basis of your own addin is in the works.
Krzysztof Koźmic
gave this 1 vote
·
-
12 votescompleted ·Adminrhuijben
(Bert Huijben, AnkhSVN & SharpSvn Projects) responded
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?
Krzysztof Koźmic
shared this idea and gave it 3 votes
·
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.