Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`PublishProfileFullPath` is ignored in `dotnet publish` command.

See original GitHub issue

Hi team,

I have:

Created a new .NET Core 3.1 console application on my Windows 10 with .NET SDK 3.1.402.
Executed the following command: dotnet publish -p:PublishProfileFullPath=WhateverHere
Publishing succeeded.

The issue is that specified PublishProfileFullPath (docs) is invalid and dotnet publish is fine with that.

Note: WhateverHere can be really whatever. An existing path, not existing path, not path at all.

Could anybody help me understand why is that?

Cheers!

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:30 (15 by maintainers)

Top GitHub Comments

2reactions

vijayrkncommented, Jan 27, 2021

In your csproj, if the first line contains “Microsoft.NET.SDK.Web”, then you are using the websdk that contains the fallback.

1reaction

joeloffcommented, Jan 27, 2021

Got it. Ok. I’ll add this item to our backlog

Top Results From Across the Web

dotnet publish command - .NET CLI

dotnet publish - Publishes the application and its dependencies to a folder for deployment to a hosting system. Synopsis .NET CLI Copy.

c# - dotnet publish with /p:PublishProfile

The PublishProfile is only the name, any directory before it is disregarded. PublishProfile property is treated as a file name and the directory ......

dotnet publish seems to ignore Working Directory

I'm trying to set up a simple pipeline that will publish on of the web projects using the dotnet publish command.

[Solved]-dotnet publish with /p:PublishProfile=?-.net-core

The PublishProfile is only the name, any directory before it is disregarded. PublishProfile property is treated as a file name and the directory...

10 commands you don't want to be without in .Net Core

Here's a full list of commands that runs restore implicitly: dotnet new; dotnet build; dotnet build-server; dotnet run; dotnet test; dotnet publish; dotnet...