I have two c# solutions, first solution is a dll and the second solution is a windows application that references the dll file as an project reference.
The solutions have a custom VCS checkout directory so that the referencing of the dll solution still works in teamcity. I also have triggers that start a build when I commit to one of the solutions. For both solutions I'm using the AssemblyInfo patcher to generate file version numbers for each build.
So this works all fine. I trigger a build of the dll file, it patches the AssemblyInfo with a new version (ie. 1.2.3) and it builds the dll. After that a build of the application that depends on the dll is triggert. BUT this thime the build process builds a new dll and does not use the already build one with the patched AssemblyInfo. The second solution builds also without any problems, but the file version of the dll file is then 1.0.0 because of the rebuild.
How can I tell teamcity to use the existing build of the first solution and do not build a new one when the second solution build starts so that the file version information that was patched in the build of the first solution stays intact.
I also configured snapshot dependencies with the option "Do not run new build if there is a suitable one" enabled but this seams to be getting ignored.