KB:MSBuild Unable to Located Nested csProj files on remote SLN

There is a known limitation with MSBuild when there is a referenced project has nested referenced project from another solution, MSBuild will fail but the same SLN will work fine from the Visual Studio IDE since VS works a little differently. 

This is an unfortunate behavior. We wish the behavior for a ProjectReference to a not-in-the-solution project was to inherit the Configuration of the project that references it, to avoid this confusion.
However, this could result in confusing behavior of its own: the not-in-solution project could be built multiple times (in parallel) with different configurations.
Since we currently build only once, adding the possibility of parallel builds (and just changing the configuration of the not-in-solution project) could break users, so we're unwilling to make this change now.

The current behavior can be worked around by explicitly specifying the configuration using SetConfiguration metadata or by adding the referenced project to the solution.

References:
https://developercommunity.visualstudio.com/t/projectreferences-dont-work-for-projects-outside-s/276809
https://github.com/dotnet/msbuild/issues/1556

Comments

Popular posts from this blog

KB: Azure ACA Container fails to start (no User Assigned or Delegated Managed Identity found for specified ClientId)

Electron Process Execution Failure with FSLogix

KB:RMM VS DEX (Remote Monitoring Management vs Digital Employee Experience)