[browser] Enable webcil in Wasm SDK

[maraf]

• Support webcil format in Wasm SDK, which is shared with blazor
• Enable webcil by setting msbuild property WasmEnableWebcil=true
• Tested only locally with manually constructed SDK

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

• TBD

TODO

• Fix publish

Author:	maraf
Assignees:	maraf
Labels:	arch-wasm, area-Build-mono
Milestone:	8.0.0

[maraf]

Failures are not related

[radical]

This needs a test in WBT.

[radical]

This needs a test in WBT.

.. that does build/publish, and runs the app. There are existing tests that run blazor apps.

[maraf]

I haven't done hooking Wasm SDK in WBT yet. It would use the pack from official build, which doesn't have the required changes. I haven't even investigated how difficult it would be.

We can either test it manually or postpone it to preview5 probably.

[radical]

I haven't done hooking Wasm SDK in WBT yet. It would use the pack from official build, which doesn't have the required changes. I haven't even investigated how difficult it would be.

Is this usable with the sdk currently, or are there other PRs to make this usable?

[maraf]

Is this usable with the sdk currently, or are there other PRs to make this usable?

This makes it usable in Blazor without any other change.
Yes, it depends on the SDK that needs manual tweaking at the moment. Also it requires aspnetcore from PR with unified boot

EDIT: steps to reproduce https://gist.github.com/maraf/a33651a9151fd129f0457e597cd54ee7

[lewing]

unified boot is open on sdk now, best case it will have made it through installer in 4-6 hrs dotnet/sdk#31912

[lambdageek]

I think after this installer codeflow PR dotnet/installer#16179 , the aspnetcore bits are in. so WBT should work now if I try this PR, right?

[maraf]

It requires SDK from dotnet/sdk#31519. Anyway I can show you what needs to be patched. It's much easier that few days before.

[lambdageek]

It requires SDK from dotnet/sdk#31519. Anyway I can show you what needs to be patched. It's much easier that few days before.

yea ok - if it's simpler to patch now, I'd like to try it. do we need that SDK PR to flow before we can review and merge this runtime PR? Would anything break if we merged this one early?

[maraf]

It's safe to merge anytime

[lambdageek]

LGTM
(I primarily looked at the C# code for the task and the .targets stuff. I didn't try a blazor build, but I'll try it later)

[lewing]

dotnet/installer#16197

[lambdageek]

dotnet/installer#16197

After this. I can confirm webcil is working with blazor.

I did the usual WBT setup, but also had to edit Microsoft.NETCoreSdk.BundledVersions.props in artifacts/bin/dotnet-latest/... to change to the 8.0.0-dev version of the pack (thanks to @maraf for the hint):

<KnownWebAssemblySdkPack Include="Microsoft.NET.Sdk.WebAssembly.Pack"
                             TargetFramework="net8.0"
                             WebAssemblySdkPackVersion="8.0.0-dev" />`

and setup a nuget.config to point to my artifacts/packages/Release/Shipping dir.

but after all that, dotnet new blazorwasm and then dotnet run and dotnet publish make versions of the blazor template that serve .webcil files and not .dlls.

@radical is it possible to make it so WBT sets up dotnet-latest so it can just use the Sdk Pack from artifacts instead of needing to edit the BundledVersions.props by hand?

[maraf]

I think he already has the change stacked up and was just waiting for everything to flow.