The Publish Artifact task created a drop for me and this is how it looks. Relying on a single file for all parameters simplifies management on Azure. I have made use of the publish profile XML file because I wanted a single file to govern the complete behavior while on Azure Devops. I also have a Publish Artifact task which is configured to use the staging directory variable. In the Azure Dev Ops build pipeline scenario, I have redirected the output to a folder under $(Build.ArtifactStagingDirectory). Relative path - From the solution root dotnet publish ConsoleAppCore\ConsoleAppCore.csproj /p:PublishProfile=ConsoleAppCore\Properties\PublishProfiles\FolderProfile.pubxmlĪbsolute path - From any location dotnet publish "C:\work\ConsoleAppCore\ConsoleAppCore.csproj" "/p:PublishProfile=C:\work\ConsoleAppCore\Properties\PublishProfiles\FolderProfile.pubxml"Īrguments= $(System.DefaultWorkingDirectory)\ConsoleAppCore\ConsoleAppCore.csproj /p:PublishProfile=$(System.DefaultWorkingDirectory)\ConsoleAppCore\Properties\PublishProfiles\FolderProfile.pubxml -configuration $(BuildConfiguration) -output $(Build.ArtifactStagingDirectory)\ConsoleAppCore-Publish\ I used Visual Studio IDE to generate a publish profile with the name FolderProfile.pubxml and then the following commands worked for me: NET Core console application ConsoleAppCore.csproj.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |