Skip to content

Fix publishing self-contained ASP.NET apps #3002

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

Merged
merged 6 commits into from
Mar 3, 2019

Conversation

dsplaisted
Copy link
Member

@dsplaisted dsplaisted requested a review from a team March 2, 2019 00:23
@@ -71,6 +71,7 @@ void AddAsset(string assetPath, string assetType)
assetPath.EndsWith(".map", StringComparison.OrdinalIgnoreCase) ||
assetPath.EndsWith(".txt", StringComparison.OrdinalIgnoreCase) ||
assetPath.EndsWith(".xml", StringComparison.OrdinalIgnoreCase) ||
assetPath.EndsWith(".json", StringComparison.OrdinalIgnoreCase) ||
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be an include list instead of exclude list?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason it's not an include list is because native assets can have a variety of extensions and I'm not sure if we know what that list is.

Eventually we would like the runtime packs to include a manifest which lists the managed and native files in the pack explicitly, so we don't have to glob for them at all.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

native assets can have a variety of extensions and I'm not sure if we know what that list is.

Can't we look at the fixed set of runtime packs we have now? Is it not .dll,.exe,.so,.dylib?

Switching to include list until we have the manifests seems reasonable to me to err on the safer side.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But I'm ok with this more targeted fix to unblock things with the least change given that we have an even safer medium term plan.

This version should have a version of the x86 ASP.NET Core runtime pack
which is published to the feeds.
@dsplaisted
Copy link
Member Author

FYI @nguerrera @dotnet/dotnet-cli I had to make a few small fixes to get everything to pass: b81ebc6 and 663bab6. I'm going to go ahead and merge.

@dsplaisted dsplaisted merged commit c60af5f into dotnet:master Mar 3, 2019
wli3 pushed a commit that referenced this pull request Feb 7, 2020
….4 (#3002)

- Microsoft.DotNet.Cli.Runtime - 5.0.100-alpha1.19480.4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants