Incorrect "dotnet publish" behave with -o key #114

New Issue

fergalmoran · 2025-08-09T17:15:03Z

fergalmoran commented

2025-08-09 17:15:03 +00:00

Originally created by @strofimo on 3/26/2018

Steps to reproduce:

Create SPA react redux project by "dotnet new reactredux" command
Run "npm install" command
Run "dotnet publish -c Release -o _Result/build1" command. Check that _Result/build1 folder contains proper set of files/folders.
Run "dotnet publish -c Release -o _Result/build2" command. Check _Result/build2 folder and find _Result folder inside with all previous builds.

P.S. this behave don't reproduced for simple console application.

*Originally created by @strofimo on 3/26/2018* Steps to reproduce: 1. Create SPA react redux project by "dotnet new reactredux" command 2. Run "npm install" command 3. Run "dotnet publish -c Release -o _Result/build1" command. Check that _Result/build1 folder contains proper set of files/folders. 4. Run "dotnet publish -c Release -o _Result/build2" command. Check _Result/build2 folder and find _Result folder inside with all previous builds. P.S. this behave don't reproduced for simple console application.

fergalmoran closed this issue

2025-08-09 17:15:03 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#114