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

[wasm] Wasm.Build.Tests - use the new sdk with templates #85498

Closed
wants to merge 15 commits into from

Conversation

radical
Copy link
Member

@radical radical commented Apr 28, 2023

@radical radical added arch-wasm WebAssembly architecture test-enhancement Improvements of test source code area-Build-mono labels Apr 28, 2023
@ghost ghost assigned radical Apr 28, 2023
@ghost
Copy link

ghost commented Apr 28, 2023

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

Issue Details
Author: radical
Assignees: -
Labels:

arch-wasm, test-enhancement, area-Build-mono

Milestone: -

Copy link
Member

@maraf maraf left a comment

Choose a reason for hiding this comment

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

What is the intended scope of this PR?
Do you want to take over also my templates PR?
Do you want to address the JS API needed changes?

@@ -7,7 +7,7 @@

<ItemGroup>
<ProjectReference Include="$(RepoTasksDir)Microsoft.NET.Sdk.WebAssembly.Pack.Tasks\Microsoft.NET.Sdk.WebAssembly.Pack.Tasks.csproj" />
<PackageFile Include="build\*.props;build\*.targets;build\*.web.config" TargetPath="build" />
<PackageFile Include="Sdk\*.props;Sdk\*.targets;Sdk\*.web.config" TargetPath="Sdk" />
Copy link
Member

Choose a reason for hiding this comment

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

This didn't worked for me. How is it that it works now? Will it still work in blazor without workload?

@@ -178,6 +179,10 @@
"kind": "Sdk",
"version": "${PackageVersion}"
},
"Microsoft.NET.Sdk.WebAssembly.Pack": {
Copy link
Member

Choose a reason for hiding this comment

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

What is the consequence of this change? Will it still work in blazor without workload?

import { dotnet } from './_framework/dotnet.js'

const { setModuleImports, getAssemblyExports, getConfig } = await dotnet
.withStartupOptions({})
Copy link
Member

@maraf maraf May 3, 2023

Choose a reason for hiding this comment

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

I'm tackling with this in my original PR. It shouldn't be in the template

Copy link
Member Author

Choose a reason for hiding this comment

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

I can remove this from this draft PR when your changes land.

@radical
Copy link
Member Author

radical commented May 3, 2023

What is the intended scope of this PR?

Anything needed to update the wasmbrowser template to use the wasm sdk.

Do you want to take over also my templates PR?

Do you mean #85311 ? The template, and the WBT parts should get covered here. Anything else that you want to change/fix like the withStartupOptions stuff, you can do that part.

<!-- WASM projects defaults to browser-wasm -->
<RuntimeIdentifier Condition="'$(RuntimeIdentifier)' == ''">browser-wasm</RuntimeIdentifier>
<UseMonoRuntime>true</UseMonoRuntime>

Copy link
Member

Choose a reason for hiding this comment

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

This file has a slight change in SDK dotnet/sdk#32170

@ghost
Copy link

ghost commented Jun 3, 2023

Draft Pull Request was automatically closed for 30 days of inactivity. Please let us know if you'd like to reopen it.

@ghost ghost locked as resolved and limited conversation to collaborators Jul 3, 2023
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-Build-mono test-enhancement Improvements of test source code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants