Publish Profile Uses Wrong ProjectDir if Web Project References Another in Same Solution

Oct 13, 2025 by orovajewels.com 146 views

Publish Profile Uses Wrong ProjectDir if Web Project References Another in Same Solution

Issue Description

When working with multiple web projects in the same solution, where one project references another, the publish profile may use the wrong project directory. This issue is particularly problematic when using command-line MSBuild calls and custom publish profiles.

Understanding the Problem

In a typical scenario, a command-line MSBuild call is used to build and deploy a web project. The call includes parameters such as the solution file, target project, configuration, and publish profile. However, when multiple web projects are present in the same solution, and one project references another, the publish profile may use the wrong project directory.

Diagnostic MSBuild Trace

To diagnose the issue, a diagnostic MSBuild trace can be used. The trace reveals that the WebPublishPipelineProjectDirectory property is set to the project directory of the last project in the dependency hierarchy that is parsed for web setup. This is in reverse order of the build process, resulting in the publish profile being used from the wrong project directory.

Error Message

The error message indicates that the publish profile is set to a specific file, but it cannot be found in the expected location. This is because the PublishProfileRootFolder property is set to the project directory of the last project in the dependency hierarchy, rather than the target project being deployed.

Steps to Reproduce

To reproduce the issue, follow these steps:

Setup a solution with two web projects.
Have the first web project set a direct project reference to the second web project.
Put the web deploy in the first project's publish profile.
Try to build from the command-line using the first project's publish profile. It will fail with an invalid path.

Expected Behavior

The expected behavior is that the publish profile should always look in the target project being deployed for publish profiles, not in the project that happens to be parsed last.

Actual Behavior

The actual behavior is that the publish profile gets its settings for the publish profile path from the last project in the dependency hierarchy that happens to be parsed for web setup, which is in reverse order of the build process.

Analysis

The analysis of this issue reveals that the PublishProfileRootFolder property is set to the project directory of the last project in the dependency hierarchy, rather than the target project being deployed. This results in the publish profile being used from the wrong project directory.

Versions & Configurations

The versions and configurations used to reproduce this issue are:

.NET Framework projects (old-style .csproj)
Single solution with multiple web projects
One project referencing another project
Command-line MSBuild call with custom publish profile

Solution

To resolve this issue, the PublishProfileRootFolder property can be set to the full path of the correct web project's publish folder. This ensures that the publish profile is used from the correct project directory.

Setting PublishProfileRootFolder

To set the PublishProfileRootFolder property, use the following command-line MSBuild parameter:

/p:PublishProfileRootFolder="C:\Path\To\Correct\Web\Project\Publish\Folder"

This sets the PublishProfileRootFolder property to the specified path, ensuring that the publish profile is used from the correct project directory.

Conclusion

In conclusion, the publish profile uses the wrong project directory when a web project references another project in the same solution. This issue can be resolved by setting the PublishProfileRootFolder property to the full path of the correct web project's publish folder. By following the steps outlined in this article, developers can ensure that their publish profiles are used from the correct project directory, even in complex solution configurations.
Publish Profile Uses Wrong ProjectDir if Web Project References Another in Same Solution: Q&A

Q: What is the issue with publish profiles when multiple web projects are in the same solution?

A: When multiple web projects are in the same solution, and one project references another, the publish profile may use the wrong project directory. This is because the PublishProfileRootFolder property is set to the project directory of the last project in the dependency hierarchy that is parsed for web setup, rather than the target project being deployed.

Q: What is the expected behavior of publish profiles in this scenario?

A: The expected behavior is that the publish profile should always look in the target project being deployed for publish profiles, not in the project that happens to be parsed last.

Q: What is the actual behavior of publish profiles in this scenario?

A: The actual behavior is that the publish profile gets its settings for the publish profile path from the last project in the dependency hierarchy that happens to be parsed for web setup, which is in reverse order of the build process.

Q: How can I reproduce this issue?

A: To reproduce the issue, follow these steps:

Setup a solution with two web projects.
Have the first web project set a direct project reference to the second web project.
Put the web deploy in the first project's publish profile.
Try to build from the command-line using the first project's publish profile. It will fail with an invalid path.

Q: What is the solution to this issue?

A: The solution to this issue is to set the PublishProfileRootFolder property to the full path of the correct web project's publish folder. This ensures that the publish profile is used from the correct project directory.

Q: How can I set the `PublishProfileRootFolder` property?

A: To set the PublishProfileRootFolder property, use the following command-line MSBuild parameter:

/p:PublishProfileRootFolder="C:\Path\To\Correct\Web\Project\Publish\Folder"

This sets the PublishProfileRootFolder property to the specified path, ensuring that the publish profile is used from the correct project directory.

Q: What are the versions and configurations that are affected by this issue?

A: The versions and configurations that are affected by this issue are:

.NET Framework projects (old-style .csproj)
Single solution with multiple web projects
One project referencing another project
Command-line MSBuild call with custom publish profile

Q: Is this issue a bug?

A: The issue is not necessarily a bug, but rather a limitation of the current implementation of publish profiles in MSBuild. However, setting the PublishProfileRootFolder property to the correct path is a workaround that can be used to resolve the issue.

Q: Can I use this workaround in my production environment?

A: Yes, you can use this workaround in your production environment. However, it's recommended to test the workaround in a non-production environment first to ensure that it doesn't cause any issues.

Q: Are there any other solutions to this issue?

A: Yes, there are other solutions to this issue. One possible solution is to refactor the solution to avoid project references between web projects. Another possible solution is to use a different deployment strategy, such as using a separate deployment project or using a third-party deployment tool.

Q: Can I get more information about this issue?

A: Yes, you can get more information about this issue by checking the MSBuild documentation and the .NET Framework documentation. You can also search for online resources and forums where developers have discussed this issue and provided workarounds.