How to check if a project is Blazor Webassembly Final version - blazor-client-side

I installed the latest Blazor WebAssembly SDK on VS 2019 and Upgraded a 3.2 preview version to it, But I am not sure if the project is 3.2 final, How to check it?

Related

Can .NET 5 Runtime run .NET 3.1 application?

I have an exe built using .NET Core 3.1. If the installer is run on a system that has .NET 5 runtime installed, it is still prompting the user to install .NET Core 3.1.
How to make this exe run on a system just having .NET 5 runtime installed?
You cannot run a .NET 3.1 app on the .NET 5 runtime. A 3.1 app requires that you install the runtime for .NET 3.1 as well. Major version changes indicate a new runtime (e.g. .NET Core 2 requires the .NET Core 2.x runtime, .NET Core 3 requires the .NET Core 3.x runtime).
Note that you can write code for an app that runs on both .NET 3.1 and .NET 5 but they are compiled separately, produce separate binaries and dependencies and the appropriate version would need to be deployed onto the target machine based upon the runtime that is installed.
.NET and .NET Core official support policy

Mobile blazor bindings

Can I use .net standard 2.1 with the last Mobile blazor bindings -Version 0.5.50-preview? I also want to use Xamarin forms 5 in the project. Is it possible to use Mobile blazor bindings with the Xamarin Forms 5?
Yes you could.
To get started, all you need is the .NET Core 3.0 or 3.1 SDK, Visual Studio or Visual Studio for Mac, and the ASP.NET and web development and Mobile development with .NET (Xamarin.Forms) workloads installed.
Install the templates by running this command from a command/shell window:
dotnet new -i Microsoft.MobileBlazorBindings.Templates::0.5.50-preview
And then create your first project by running this command:
dotnet new mobileblazorbindings -o FirstMobileBlazorBindingsApp
Open the solution (SLN file) in Visual Studio and mark either the Android or iOS project as the StartUp Project.
The more you could refer to the official doc.

The current .NET SDK does not support targeting .NET Core 3.1

I have downloaded and install Visual Studio 2019 and have dotnet core 3.1 installed.
As I am starting to play around with VS, I have just created a simple project using VS built-in Web App Template and try to run without debugging.
It gives the error of "The current .NET SDK does not support targeting .NET Core 3.1. Either target .NET Core 3.0 or lower, or use a version of the .NET SDK that supports .NET Core 3.1."
May I know how it can be resolved?
Thanks.
Regards,
Andrew
If you already have the correct .NET Core 3.1 SDK installed it could be caused by a file called global.json. This file allows to configure which SDK is used:
The global.json file allows you to define which .NET Core SDK version
is used when you run .NET Core CLI commands. Selecting the .NET Core
SDK is independent from specifying the runtime your project targets.
The .NET Core SDK version indicates which versions of the .NET Core
CLI is used.
Delete the file or change the defined SDK to 3.1:
{
"sdk": {
"version": "3.1.100",
"rollForward": "latestPatch",
"allowPrerelease": false
}
}
If you already have VS 2019 version more then v16.4, then magicandre1981 answer will be helpful.
But, I would suggest you to check your VS version as well. as I have invested lots of hours and checked my version much later.
Minimum compatibility visual studio version for .net Core 3.1 is Visual Studio 2019 (v16.4). I updated it and it worked.
Release update:
https://dotnet.microsoft.com/download/dotnet-core/3.1
For me, it was an environment variable. Not sure what set it (maybe some lame chocolatey package or something.)
I had environment variable MSBuildSDKsPath set as C:\Program Files\dotnet\sdk\2.0.3\Sdks
Removing that environment variable fixed the issue for me. (Actually, I renamed the environment variable to OLD_MSBuildSDKsPath, just in case ;) )
I was having vs 17 vs 19 both
I was trying to open code developed in visual studio 2019 into 2017.
Opening that project in VS 19 solved the issue for me
I am using VS 2022 and have a parallel installation of VS 2019 on my PC.
And I noticed that .NET 3.1 SDK (LTS) had to be installed (both 32 and 64 bit packages) to support an existing EF code first project (running with EF 3.x). Without it, the migration did not work and I got an error message like the one mentioned in the question.
Note that they can be installed in parallel with other versions (I have .NET 5 and .NET 6 on my PC installed as well).
You can find the required packages here: https://aka.ms/dotnet-download

is Blazor Component Utilities compatible with Core 2.1 or 2.2?

is Blazor Component Utilities compatible with Core 2.1 or 2.2 ?
When I try to compile a 2.1 or 2.2 compatible project I'm always seeing
/usr/local/share/dotnet/sdk/2.1.802/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(5,5):
Error NETSDK1064: Package BlazorComponentUtilities, version 1.1.0 was not found. It might have been deleted since NuGet restore. Otherwise, NuGet restore might have only partially completed, which might have been due to maximum path length restrictions. (NETSDK1064) (ultaLINK)
However with Core 3.0 and preview and above I don't get this error. Anyone know why?
https://www.nuget.org/packages/BlazorComponentUtilities/
The website here says dotnet 2.0 is compatible, so....
No it's not you need to use dotnet core 3.0
If I remember well 1st preview was built with .Net Core 2.1, but since preview 5 is .Net core 3.0.
If you want to work with blazor you should have .net core 3.0. You can use VS 2019 or download manually from https://dotnet.microsoft.com/download/thank-you/dotnet-sdk-3.0.100-windows-x64-installer

Application migration from .net core 2.1 to 3.0

I'm trying to upgrade my project to .net core 3.0 when it used to be running with asp core 2.1.
The application compile fine but as soon as i start it, the application crash on the app.usespa() function in startup.cs ...
Does someone has already encountered this issue ?
When i create a sample project from scratch with angular it runs well ...
Thanks in advance,
Razgort
One of your library is still not upgraded to 3.x.
use NUGET to update all your libraries to be compatible with 3.x

Resources