Home/ Questions/Q 663787
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T23:31:40+00:00

We are using ankhsvn to check in our .net code, however I have two

  • 0

We are using ankhsvn to check in our .net code, however I have two issues with our setup that I want to resolve.

1\ I thought a key reason to have a tool like svn is that you can rollback to an earlier version of your codebase. If developers are just checking in code, then how can you get version 1.1 (say the current production build), out of subversion?

2\ In VS you have the concept of solutions, many solutions might use the same project. How do I make sure when a developer checks out a solution, they get the appropriate versions of the projects that belong to that solution?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team
    1. You need to learn about tags. The idea would be that when you reach a point that it’s time for release X, you’ll create a read-only /tag/release_X in your Subversion repository. You continue to work on /trunk or a /branch; if you need /tag/release_X, you simply check it out.
    2. I don’t know what concept of “solutions” is. If you mean you have a shared project that turns into a JAR or WAR or DLL or assembly that several projects use, you can check in the artifact and have other projects simply check it out like any other 3rd party JAR.

    I’d recommend reading the SVN Red Bean book.

    • 0