Creating your first gRPC .NET Core Client and Server App using Visual Studio or Visual Studio Code
the main goal of this release is to facilitate migrating existing applications that use EF 6 to .NET Core 3.0
Visual Studio tooling (e.g. XAML and WinForms Designers, app publishing tools) for WinForms and WPF development with .NET Core 3.
Microsoft has announced that the .NET Core 2.0 will be considered "end of life" and thus no longer supported as of October 1, 2018. .NET Core 2.0 is considered a non-LTS release, and as such Microsoft only commits its support for three months after a successor has been released. In this case, with .NET Core 2.1 having been released May 31, .NET Core 2.0’s end has come.
At Microsoft Build Live today, we are sharing a first look at our plans for .NET Core 3. The highlight of .NET Core 3 is support for Windows desktop applications, specifically Windows Forms, Windows Presentation Framework (WPF), and UWP XAML. You will be able to run new and existing Windows desktop applications on .NET Core and enjoy all the benefits that .NET Core has to offer.
Based on the results of the performance test, .Net Core 2.0 can execute up to 3x faster than Go.
پروژه ای سورس باز برای نوشتن اپلیکیشن هایی که با الگوی CQRS و Eventsourcing پیاده میشوند . در مقایسه با SimpleCQRS به روز‌تر با قابلیت‌های مدرن‌تر شده و از .Net Core هم پشتیبانی میکند.
Helper classes to set up and run as windows services directly on .net core. A ServiceBase alternative.
بله در برنامه هایی که هنوز به .net 7 ارتقا داده نشده اند نیز رخ میدهد.
البته فقط در متد هایی باعث خطا خواهد شد که به نحوی از system.data.sqlclient استفاده کرده اند (مانند context.database.(executeRawSql و سایر کد‌ها که با ef core و linq نوشته شده، خطایی تولید نخواهند کرد.
یک نکته‌ی تکمیلی
RandomNumberGenerator ای که در این مطلب بحث شد، از NET Core 3.1. به بعد ساده‌تر شده و به همراه متد GetInt32 نیز هست:
public int GetRandomNumber() => RandomNumberGenerator.GetInt32(1, 1000000);