search

gustavnavar / Grid.Blazor

Grid component with CRUD for Blazor (client-side and server-side) and ASP.NET Core MVC
GNU Lesser General Public License v2.1
692 stars 133 forks source link

Blazor shared appears to only support .net core 2.1 while Blazor Grid supports .net core 3.1 #214

Open cashmore1 opened 3 years ago

cashmore1 commented 3 years ago

Restoring Nuget packages i get failures with BlazorGridShared restoring into my .Net Core 3.1 project. It states that is supports it but the dependency of Blazor shared only supports .net core 2.1 according to the nuget package spec. Is there plans to support 3.1?

gustavnavar commented 3 years ago

GridBlazor targets .Net Standard 2.1. So any .Net Core 3.1 project (and .Net 5.0) should work with any issues.

What package and version fails in your project?

cashmore1 commented 3 years ago

The error that im getting is from a nuget package restore. I get the following error:

Errors in \WebSite\WebSite.csproj NU1202: Package GridShared 3.1.12 is not compatible with netcoreapp3.1 (.NETCoreApp,Version=v3.1). Package GridShared 3.1.12 supports: netstandard2.1 (.NETStandard,Version=v2.1)

My website targets .net core 3.1

gustavnavar commented 3 years ago

Is it as Blazor Server project or a Blazor WASM?

cashmore1 commented 3 years ago

I'm using the Blazor Server.

cashmore1 commented 3 years ago

This was happening in our ci/cd environment where we were running a nuget restore command before the builds to ensure that all packages were updated. When I remove that command and simply let the build of the site take care of restoring what's missing I don't get the errors. The grid works fine and all components build. It appears that there may be something going on with the nuget.exe and restore command that's not allowing an assembly that's targeted for .net core 3.1 use an assembly that's targeted for .net standard 2.1 or something else weird.

gustavnavar commented 3 years ago

I can run nuget.exe restore in my projects with no issues. I'm using the last versio (5.7.0.6726). Maybe you can download the last version of nuget. Another source of problems can be the `nuget.config files that you are using. But I don't think tht the source of the problem be the nuget packages. I would report this issue to the nuget team.