dotnet / dotnet/msbuild

PublishProfileFullPath doesnt support relative paths

Open
#12,833 4 comments 0 reactions 0 assignees View on GitHub
backlog triaged
Dominant language
C#
Stars
5.5k
Forks
1.5k
Avg merge
1d 8h
Merged PRs (30d)
141

Description

### Issue Description

When working with PublishProfileFullPath properties, relative paths should be support. Only supporting absolute path which include drive doesn't work in 99% of environments where repositories can be cloned to individual locations and also CLI can tun on different repo ENVs

msbuild /restore /t:Publish /p:PublishProfileFullPath=PublishProfile.pubxml

Should lead to situation where PublishProfile.pubxml is resolved from same location where msbuild is running from. While relative path should be supported too. What we are trying to achieve is to have single publishing profile which is shared for whole solution which consist from lot of individual csprojs. Only way how to do that today is to duplicate PublishProfile.pubxml inside each project location under Properties\PublishProfile and than use PublishProfile instead of PublishProfileFullPath. Not being able to specify publish profile while publishing whole solution is making publishing of such solutions as ineffective as it get.

### Steps to Reproduce

msbuild /restore /t:Publish /p:PublishProfileFullPath=PublishProfile.pubxml

### Expected Behavior

msbuild will resolve PublishProfileFullPath if defined as relative path

### Actual Behavior

msbuild cant resolve relative paths from PublishProfileFullPath

### Analysis

_No response_

### Versions & Configurations

Any msbuild version

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.