Skip to content

Publish directory inconsistent between Windows and Ubuntu #4891

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
schellap opened this issue Jan 25, 2016 · 8 comments
Closed

Publish directory inconsistent between Windows and Ubuntu #4891

schellap opened this issue Jan 25, 2016 · 8 comments
Assignees
Labels
Milestone

Comments

@schellap
Copy link

Ubuntu CLI is publishing to temp2, but Windows publishes to temp2/Debug/dnxcore50.

Repro

dotnet new
dotnet restore
dotnet publish -o temp2 -f dnxcore50 --runtime ubuntu.14.04-x64
dotnet.exe publish -o temp2 -f dnxcore50 --runtime win7-x64

Could you please fix it to be consistent? Is this by design?

Needed for:
dotnet/corert#717

dotnet publish -o temp2 -f dnxcore50 --runtime ubuntu.14.04-x64
Publishing temp for DNXCore,Version=v5.0/ubuntu.14.04-x64
Compiling temp for DNXCore,Version=v5.0
...
Published to temp2
Published 1/1 projects successfully
dotnet.exe publish -o temp2 -f dnxcore50 --runtime win7-x64
Publishing temp for DNXCore,Version=v5.0/win7-x64
Compiling temp for DNXCore,Version=v5.0
...
Published to temp2\Debug\dnxcore50
Published 1/1 projects successfully
@brthor
Copy link
Contributor

brthor commented Jan 25, 2016

@schellap The windows behavior you are seeing will be the correct behavior
Ubuntu builds are down in master on VSO currently which is the reason for the disconnect. dotnet/cli#1029 should bring us closer to fixing that but there are some other issues as well.

@andyleejordan
Copy link
Member

We're hitting this, broke our Windows CI build and also appears to have regressed on OS X.

@brthor Why is --output going to be (essentially) ignored (/ append to unnecessarily)? Is there a new command to tell it to publish the flat list of DLLs to the folder we specify?

@davidfowl
Copy link
Member

I'm fixing this as part of https://github.com/dotnet/cli/issues/987

@moozzyk
Copy link
Contributor

moozzyk commented Jan 27, 2016

👏

@andyleejordan
Copy link
Member

I am against this new behavior. We really liked that --output bin gave me ./bin/program. Very easy to use. Changing this means changing scripts, documentation, CI, and updating our developers and previewers for the new behavior.

Is there going to be a better way to publish?

@davidfowl
Copy link
Member

@andschwa It's going to be flat. The changes I'm making will make it the way it was. If you publish multiple runtimes to the same output folder it'll tell you or fail or something.

@andyleejordan
Copy link
Member

@davidfowl Perfecto! Thank you.

@TheRealPiotrP
Copy link
Contributor

@livarcocc

@msftgits msftgits transferred this issue from dotnet/cli Jan 31, 2020
@msftgits msftgits added this to the 1.0.0-rc2 milestone Jan 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants