With this newest Blazor release we’re pleased to announce that Blazor is now in official preview! Blazor is no longer experimental and we are committing to ship it as a supported web UI framework including support for running client-side in the browser on WebAssembly.
Here’s the list of what’s new in this preview:
- Razor Components renamed back to server-side Blazor
- Client-side Blazor on WebAssembly now in official preview
- Resolve components based on
@using
- _Imports.razor
- New component item template
- Reconnection to the same server
- Stateful reconnection after prerendering
- Render stateful interactive components from Razor pages and views
- Detect when the app is prerendering
- Configure the SignalR client for server-side Blazor apps
- Improved SignalR reconnect features
- Configure SignalR client for server-side Blazor apps
- Additional options for MVC service registration
- Endpoint routing updates
- New template for gRPC
- Design-time build for gRPC
- New Worker SDK
.NET Core SDK | .NET Core Runtime | Compatible Visual Studio | MSBuild | Notes |
---|---|---|---|---|
2.1.5nn | 2.1 | 2017 | 15 | Installed as part of VS 2017 version 15.9 |
2.1.6nn | 2.1 | 2019 | 16 | Installed as part of VS 2019 |
2.2.1nn | 2.2 | 2017 | 15 | Installed manually |
2.2.2nn | 2.2 | 2019 | 16 | Installed as part of VS 2019 |
3.0.1nn | 3.0 (Preview) | 2019 | 16 | Installed manually |
پ.ن.
اگر با VSCode و یا Rider کار کنید، هیچگاه متوجه وجود این مسایل نخواهید شد!
همانطور که میدونید برنامهنویسها برای اینکه توی صنعت نرمافزار حرفی برای گفتن داشته باشند همیشه باید خودشون رو بروز نگه دارند. گاهی این بروزرسانی شامل یادگیری ویژگیهای نسخهی جدید یک تکنولوژی و گاهی شامل یادگیری یک تکنولوژی جدیده. که این دومی سختتر و پیچیدهتر از یک بروزرسانی ساده است. توی لینک زیر کمی در مورد بروز شدن در سال 1398 نوشتم.
سرفصلهایی برای معتبر باقی ماندن به عنوان یک توسعه دهندهی NET.
First it is important to recognize that the .NET Framework is not the same as .NET Core. The .NET Framework is effectively now in maintenance mode , and all innovation is occurring in the open source .NET Core now and into the future. So step one to remaining relevant is to understand .NET Core (and the closely related .NET Standard).