Closed moozzyk closed 4 months ago
@moozzyk Is this a portable desktop app?
@pakrym Might this be related to the half portable work?
@moozzyk post project.json
please
I only get this behavior when i don't have "Microsoft.NETCore.Platforms" : "1.0.1-*"
in my dependencies.
@pakrym - updated the report with project.json @brthor - I don't know what is portable desktop app vs. non-portable desktop app and how I express one vs. the other in the project.json.
@moozzyk try adding "Microsoft.NETCore.Platforms" : "1.0.1-*"
to common or net451
specific dependencies
After adding a dependency on "Microsoft.NETCore.Platforms" : "1.0.1-*"
publish works even if runtime is not win7-x64
Hum, I had not realized this dependency was required even for .NET Desktop (in my defense, the fact it has NETCore
in its name is... misleading)
Would you recommend adding this dependency in a portable app that is supposed to work on both .NET Desktop and .NET Core? (the original project.json
, that uses the portable model, can be found here: https://github.com/openiddict/openiddict-core/tree/dev/samples/Mvc.Server/project.json)
@moozzyk should we add the dependency "Microsoft.NETCore.Platforms" : "1.0.1-*" at the common level or at a framework level. Also please let me know for now if I can use the dependency change or publish it using win7-x64.
For now I would add "Microsoft.NETCore.Platforms" : "1.0.1-*"
since this seems to fix the issue. I guess when this bug is resolved it will be clear whether you need to keep "Microsoft.NETCore.Platforms" : "1.0.1-*"
.
@piotrpMSFT backlog? I'm pretty sure it's not coherent with what @davidfowl said earlier today about the fact this package won't be required for apps and that it should be fixed for RTM.
https://github.com/aspnet/Templates/issues/544#issuecomment-218216692
@moozzyk Reviewing issues for Pub IIS. This seems like too much of an edge case to sweat for the Common Errors section (if even still a problem), correct?
@GuardRex - Correct, I don't think this belongs to common errors.
yep ... not "common" enough for "common errors" :smile:
@GuardRex @moozzyk isn't this "bug" fixed in RTM, anyway?
@PinpointTownes - I have not verified and the issue is still open so I assume it's not fixed.
Yeah ... I was just going by lack of closure. I raised this b/c I'm reviewing Home, Hosting, IISIntegration, and ANCM repo issues for the Pub to IIS doc. I'm trying to review a lot of issues for this doc update.
So this issue is still open, and while I assume the basic issue is fixed as I didn't encounter the issue for win*-x64
, I did for win*-x64-corert
, so I assume this is still topic is still relevant?
Due to lack of recent activity, this issue has been labeled as 'stale'. It will be closed if no further activity occurs within 30 more days. Any new comment will remove the label.
This issue will now be closed since it has been labeled 'stale' without activity for 30 days.
Steps to reproduce
Publish a web application for full desktop using non-win7-x* RID:
dotnet publish -f net451 -r win8-x64
The application will not have libuv.dll and therefore it will fail at runtime.
Expected behavior
Since there is not libuv for win8-x64 the one for win7-x64 should be published to the output.
Actual behavior
Because libuv.dll was not published the application fails with:
Environment data
dotnet --info
output: