We have a solution called & # 39; MySolution & # 39 ;. We have another solution that tests this solution called & # 39; MyTests & # 39; That proves & # 39; MySolution & # 39 ;.
When in debug mode, & # 39; MyTests & # 39; refers to & # 39; Mysolution & # 39; with a route to the local DLLs.
In launch mode, & # 39; MyTests & # 39; refers to & # 39; Mysolution & # 39; through NuGet.
Only when the feature branches of & # 39; MySolution & # 39; merged into & # 39; dev & # 39 ;, the compilation server goes to NuGet.
During the development I update MySolution with a new functionality, I update MyTests to test this new functionality and it works and it is built and it happens and everything is good because it refers to the local MySolution DLL.
When I arrive at the compilation server, it cannot be compiled, since the new functionality is not found in the MySolution package (now NuGet refers to it). This fails in exactly the same way if I turn my Visual Studio into launch mode.
What approaches are available to the team to avoid this form of DLL / NuGet hell? Is there a proven method that involves something smart with the names of the function branches (that is, the MySolution function branches will be sent to NuGet but will be added with a version that the MyTests function branch will look for by default)?