-
Couldn't load subscription status.
- Fork 5.2k
[browser] Use WebAssembly SDK for runtime tests #120330
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
base: main
Are you sure you want to change the base?
Conversation
|
@javiercn Does it ring any bell?
|
TBD
Fixes to #103025
TODO
<Content Link="..."copy the assembly to the publish output early enough, so that it gets picked up toWasmAssembliesToBundleand so the AOT compiler gets itNetCoreServerandRemoteLoopServerGetCurrentProjectBuildStaticWebAssetItemsWasmExtraFilesToDeployfrom testsWasmFilesToIncludeInFileSystem- We needed coreVfs for runtimeConfig, but we have that solved now by embedding it into the boot manifest. I think we can drop coreVfs. The challenge is that VFS items hastargetPathas well, so SWA standard properties aren't enoughIncludeSatelliteAssembliesInVFSbrowser-wasm linux Release LibraryTests_EATProxyProjectForAOTOnHelix.projis usingWasmApp.LocalBuild.props/targetsWasmAppDir<OutputType Condition="'$(OutputType)' == ''">exe</OutputType>inMicrosoft.NET.Sdk.WebAssembly.Browser.propsis too relaxed as at the point the default value oflibraryis already supplied by general SDK propsStartupHookForFunctionalTest.csprojWasm.Advanced.Sample.csprojhasWasmAssembliesToBundleitem is emptyStartupHookForFunctionalTestconflicting SWAMicrosoft.CSharp.wasm