svn - Auto-versioning DLLs in Visual Studio 2008 -

We are trying to resolve some conventions to handle the dependency with the Czech code in svn. The previous method was basically a free one for everyone, which meant that projects could not be checked and made without negligible with references (most projects are C #).

We are fixing this one step at a time, and are now checking in a separate svn repository in binary, the builds are different from the SVN modification numbers they do, so you have < There may be a path like code> svnrelease / libraryA / r1000 / libraryA.dll . One thing that came up is a scenario such as: Library relies on A Library B, Project P relies on Library A, but directly refers to Library B. If the library refers to the amendment of 1000 B, but the direct reference to Project P is revised 2000?

I suggested to include the revision number in the DLL file names, when they are checked in the release SVN repo, so many versions can be in coexistence. One co-worker had suggested that VS2k8 could handle it automatically. So if in Library A project, you set it to version 1.8, VS In the name "Output" LibraryWit_8, and in Project P, you can put a reference to "$ (release) \ Library A \ $ (version)". It can resolve I did not get any information about this possible? And if not, is my method of including the version name in my DLL binary file justified?

(I know from the scenario that the refactoring code may be necessary, but I am looking for a short term solution, we sort the stuff. It is also possible to use GAC , But for now we want to be able to share DLL with each app.)

I Generally giving each project a "Lib" directory (or more often, each solution) in which I put those assemblies on which solutions depend. This means that each solution is independent of other solutions. Ok, at least like; Dependency within each LibyDiary directory is still good to play with each other. But it provides a situation where every solution can be updated separately without breaking other solutions.