Skip to content
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

[ClickOnce] Consider CopyToPublishDirectory property before publishing Content Items. #9486

Merged
merged 2 commits into from
Jan 18, 2024

Conversation

sujitnayak
Copy link
Contributor

@sujitnayak sujitnayak commented Dec 2, 2023

Fixes #
AB#1921153

Summary

For Blazor apps, ClickOnce is publishing the staticwebassets.json file which is marked as CopyToPublishDirectory = Never. There are local paths in this json file so when the app is installed on a different machine where the local paths don't exist, the app crashes on launch.

Changes Made

Now when we determine the Content Items to publish, we look at the CopyToPublishDirectory metadata and exclude items that have it set to Never.

Customer Impact

Customers with Blazor Apps using ClickOnce to publish are seeing a failure to launch the app after upgrading to 17.8. Due to ClickOnce changes we made in 17.8 as part of PR 9299, we are incorrectly publishing the staticassets.json file. This is being addressed in this PR.

Regression?

Yes

Testing

Blazor app publishing scenario verified.
CTI team has done a regression test pass with the private.

Risk

Low

@sujitnayak sujitnayak requested a review from John-Hart December 2, 2023 01:28
@ghost
Copy link

ghost commented Dec 2, 2023

Hello! I noticed that you're targeting one of our servicing branches. Please consider updating the version.

@sujitnayak sujitnayak changed the base branch from vs17.8 to vs17.9 January 5, 2024 00:07
@sujitnayak sujitnayak force-pushed the user/sujitn/1921153 branch from 0247baa to 18d6582 Compare January 5, 2024 00:36
@sujitnayak sujitnayak marked this pull request as ready for review January 5, 2024 05:18
Copy link
Member

@rainersigwald rainersigwald left a comment

Choose a reason for hiding this comment

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

Do you want to take this for 17.9 QB mode? If so we'll need the paperwork . . .

@sujitnayak
Copy link
Contributor Author

Do you want to take this for 17.9 QB mode? If so we'll need the paperwork . . .

Most likely since today is the last day for M2 approvals and the change I am making for the CR will incur another test pass.

@sujitnayak
Copy link
Contributor Author

Do you want to take this for 17.9 QB mode? If so we'll need the paperwork . . .

Bug has been updated with the QB mode template.

@ghost
Copy link

ghost commented Jan 12, 2024

Hello! I noticed that you're targeting one of our servicing branches. Please consider updating the version.

Copy link
Member

@JanKrivanek JanKrivanek left a comment

Choose a reason for hiding this comment

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

Looks good to me

@JanKrivanek JanKrivanek merged commit ad2a721 into dotnet:vs17.9 Jan 18, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants