We have a solution called MySolution. We have another solution that tests this solution, called "MyTests," which tests "MySolution."
In debug mode, & # 39; MyTests & # 39; on & # 39; Mysolution & # 39; with a path to local DLLs.
In release mode, & # 39; MyTests & # 39; via NuGet on & # 39; Mysolution & # 39 ;.
Only if feature branches of & # 39; MySolution & # 39; in & # 39; dev & # 39; The build server will be transferred to NuGet.
During development, I'm updating MySolution with new features, updating MyTests to test these new features, and it works, and builds and persists, and all is well, as it points to MySolution's local DLL.
If I move to the build server, it can not be created because the new functionality is not included in the MySolution package (now referred to by NuGet). This will also fail if I put my Visual Studio in Sharing mode.
What approaches are available to the team to avoid this form of DLL / NuGet hell? Is there a best practice where the names of feature branches play a smart role (ie, MySolution feature branches are redirected to NuGet, but a version is attached by default in which the MyTests feature topic is displayed becomes)?