You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm on a Windows 8.1 machine and trying to publish for osx.10. I've installed the latest dotnet tools via dotnet-win-x64.latest.msi.
When running dotnet-publish --framework dnxcore50 --runtime osx.10.10-x64 it runs fine, i get a dnxcore50\osx.10.10-x64\ folder with all the dll's and dylib as expected and a AppName.exe file. And as you probably guessed the exe file is just the windows corehost.exe, same thing if i publish for ubuntu. Basically it always uses the host os corehost.
If i publish from a mac the same bug manifests itself, i get a mac corehost if i target win7-x64.
Is this a known bug, are there any workarounds?
Thanks
The text was updated successfully, but these errors were encountered:
teodimache
changed the title
dotnet-publish runtime always uses host os corehost
dotnet-publish --runtime RID always uses host os corehost
Dec 18, 2015
one work around should be manually copying corehost from the target runtime package as you only need that , everything else is managed. I haven't seen this issue although the team will know better , if they are not already on holidays 😄
…0200609.2 (#4605)
Microsoft.Build.Localization , Microsoft.Build
From Version 16.7.0-preview-20309-01 -> To Version 16.7.0-preview-20309-02
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Hi,
I'm on a Windows 8.1 machine and trying to publish for osx.10. I've installed the latest dotnet tools via dotnet-win-x64.latest.msi.
When running dotnet-publish --framework dnxcore50 --runtime osx.10.10-x64 it runs fine, i get a dnxcore50\osx.10.10-x64\ folder with all the dll's and dylib as expected and a AppName.exe file. And as you probably guessed the exe file is just the windows corehost.exe, same thing if i publish for ubuntu. Basically it always uses the host os corehost.
If i publish from a mac the same bug manifests itself, i get a mac corehost if i target win7-x64.
Is this a known bug, are there any workarounds?
Thanks
The text was updated successfully, but these errors were encountered: