using JsonPatch packages not working in blazor-wasm

[tallichet]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I have a client API project which uses Microsoft.AspNetCore.JsonPatch nuget to be able to call PATCH requests with JsonPatchDocument<>.

When upgrading to version 10 either with Microsoft.AspNetCore.JsonPatch or Microsoft.AspNetCore.JsonPatch.SystemTextJson, my blazor-wasm project is not compiling anymore. It seems the JsonPatch is having a link to aspnet SDK.

The build error:

>C:\Program Files\dotnet\sdk\10.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(544,5): error NETSDK1082: There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'.

Expected Behavior

IMO, this package should work in blazor wasm projects

Steps To Reproduce

Create a Blazor Web App with in Auto mode.
Add reference to Microsoft.AspNetCore.JsonPatch 10.0.0 in the App.Client project
Build

Exceptions (if any)

No response

.NET Version

10.0

Anything else?

No response

[MihuBot]

I'm a bot. Here are possible related and/or duplicate issues (I may be wrong):

• no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'. #53671
• Fix for: There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'. #55132

[acoudene]

Hello,

I have the same problem.

Here a minimal repro project as a simple Blazor where client part just referencing JsonPatch assembly in .Net 10.
BlazorJsonPatch10CompilationError

In summary, if I use in Client WebAssembly:
<PackageReference Include="Microsoft.AspNetCore.JsonPatch" Version="10.0.0" />

Then I will get this error:
1>C:\Program Files\dotnet\sdk\10.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(544,5): error NETSDK1082: There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'.

But no error if I put this previous one:
<PackageReference Include="Microsoft.AspNetCore.JsonPatch" Version="9.0.11" />

[danroth27]

@joperezr @mikekistler Did we accidentally introduce an ASP.NET Core framework reference to our JSON Patch support in .NET 10?

[acoudene]

@joperezr @mikekistler Did we accidentally introduce an ASP.NET Core framework reference to our JSON Patch support in .NET 10?

If this dependency in csproj: <Reference Include="Microsoft.AspNetCore.Http.Abstractions" Condition="'$(TargetFrameworkIdentifier)' == '.NETCoreApp'" /> with this property inside Microsoft.AspNetCore.Http.Abstractions : <IsAspNetCoreApp>true</IsAspNetCoreApp> and the fact that <IsPackable>false</IsPackable> could be the issue?

[mikekistler]

Did we accidentally introduce an ASP.NET Core framework reference to our JSON Patch support in .NET 10?

Honestly it never crossed my mind that someone would use this outside the context of an ASP.NET Core app. Was that a requirement?

[danroth27]

Honestly it never crossed my mind that someone would use this outside the context of an ASP.NET Core app. Was that a requirement?

Yeah, it's not uncommon to use JsonPatchDocument to create PATCH requests that you then send with HttpClient, although I don't know that we've ever officially documented that as a scenario. This does appear to be related to the Microsoft.AspNetCore.Http.Abstractions dependency.