WPF - Blazor hybrid - staticwebassets.runtime.json content root path problem

[gdar91]

Description

When publishing a WPF Blazor Hybrid app (that uses BlazorWebView) to a ClickOnce server, a staticwebassets.runtime.json file is added to the output. The problem is it contains content root paths from a developer machine, which then causes the application to crash, complaining about the path.

Configuration

.NET 7.0.14, on Windows 10 x64.

Regression?

It seems that it is a regression, because in previous versions of .NET 7 and Visual Studio, it didn't use to output the staticwebassets.runtime.json file at all.

If I make the app delete this file during launch, then it solves the problem, but I still consider it a workaround.

[javiercn]

@gdar91 thanks for contacting us.

Can you provide details on the Visual Studio version you are using as well as the exact SDK versions?

Both, the ones where it worked and the ones where it stopped working.

If you pin the SDK to an older version where it worked using a global.json, does it work with the current Visual Studio version you are using?

Hi @gdar91. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[gdar91]

@gdar91 thanks for contacting us.

Can you provide details on the Visual Studio version you are using as well as the exact SDK versions?

Both, the ones where it worked and the ones where it stopped working.

If you pin the SDK to an older version where it worked using a global.json, does it work with the current Visual Studio version you are using?

I'm currently using .NET 8.0.100 and Visual Studio 17.8.3, and it doesn't work on them.
I have also tried to downgrade the .NET version to 7.0.103 (using a global.json), as it was the version that used to work fine, but it didn't help. I wanted to downgrade Visual Studio to 17.7, as it was the version where it used to work, but it didn't let me go that far back, so I downgraded it to 17.8, which also didn't help.

[javiercn]

@gdar91 thanks for the additional details.

This seems to be a regression on the Click Once functionality that is impacting us somehow. From what you are telling us, this will affect not only .NET 8.0 apps, but previous versions too.

[javiercn]

@mkArtak parking this in 8.0.x so that we can keep track of it, but I do not think this is something we've regressed, since from what the issue indicates, something else have cause this issue as apparently this was working before. There was a similar issue reported in AzDo recently I believe.

[Mr-MooMoo]

I can confirm - I face the same error with net8 / VS 17.8.3. and publish via ClickOnce. Solution was working before moving to net8 & VS 17.8.3

[SoulsideJourney]

It's working on VS 17.7.6 and broken since 17.8.0
.NET 7.0
#53027