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 not support the FrameworkReference of Microsoft.AspNetCore.App #18874

Open
SongOfYouth opened this issue Nov 21, 2024 · 3 comments
Open
Labels
difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/needs-information Indicates an issue needs more information in order to work on it. triage/untriaged Indicates an issue requires triaging or verification

Comments

@SongOfYouth
Copy link

Current behavior

When build a net9.0-browserwasm project, add a FrameworkReference in .csproj:

  <ItemGroup>
    <FrameworkReference Include="Microsoft.AspNetCore.App" />
  </ItemGroup>

it raise an error:
dotnet\sdk\9.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(495,5): error NETSDK1082: There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'.

Expected behavior

can be built noninductively.

How to reproduce it (as minimally and precisely as possible)

No response

Workaround

No response

Works on UWP/WinUI

None

Environment

Other

NuGet package version(s)

No response

Affected platforms

WebAssembly

IDE

Visual Studio 2022

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response

@SongOfYouth SongOfYouth added difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification labels Nov 21, 2024
@jeromelaban
Copy link
Member

Thanks for the report.

This is done on purpose as the tooling included in aspnetcore is not compatible with the wasm environment. Could you explain why you need this?

@jeromelaban jeromelaban added the triage/needs-information Indicates an issue needs more information in order to work on it. label Nov 26, 2024
@SongOfYouth
Copy link
Author

Thanks for the report.

This is done on purpose as the tooling included in aspnetcore is not compatible with the wasm environment. Could you explain why you need this?

I have used some abstractions of aspnetcore to create webapi request code on client at net8 or earlier,since netstandard is not avaliable begin net8. now i removed them.

@github-actions github-actions bot removed the triage/needs-information Indicates an issue needs more information in order to work on it. label Nov 27, 2024
@jeromelaban
Copy link
Member

If you removed them, you do not need the framework reference anymore, correct?

@jeromelaban jeromelaban added the triage/needs-information Indicates an issue needs more information in order to work on it. label Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/needs-information Indicates an issue needs more information in order to work on it. triage/untriaged Indicates an issue requires triaging or verification
Projects
None yet
Development

No branches or pull requests

2 participants