Показаны сообщения с ярлыком Asp.Net Core. Показать все сообщения
Показаны сообщения с ярлыком Asp.Net Core. Показать все сообщения

пятница, 27 ноября 2020 г.

Asp.Net Core 5

 https://docs.microsoft.com/en-us/dotnet/core/dotnet-five

https://devblogs.microsoft.com/aspnet/announcing-asp-net-core-in-net-5/

https://docs.microsoft.com/ru-ru/aspnet/core/migration/31-to-50?view=aspnetcore-5.0&tabs=visual-studio

https://devblogs.microsoft.com/dotnet/announcing-net-5-0/

https://www.infoworld.com/article/3533053/whats-new-in-microsoft-net-5.html

https://www.theregister.com/2020/11/11/aspnet_core_50_released_with/

https://habr.com/ru/company/microsoft/blog/493390/

https://www.clariontech.com/blog/microsoft-announces-.net-5-a-brief-overview

https://www.telerik.com/support/whats-new/aspnet-core-ui

https://www.dotnetcurry.com/dotnetcore/dotnet-5-new-features

AspNet Core, .Net Core, Version, Win 7

 


Win 7 .Net Cor 3.1

Setup 3.1

VS2017
Unfortunately .NET Core 3 requires MSBuild 16 which only comes with VS 2019

Visual Studio 2017 doesn't support .NET Core 3. You need Visual Studio 2019 16.3 or higher. You can find this information in the .NET Core 3.0 announcement.


Get started Asp.Net Core


Magic commands:

dotnet new webapp -o aspnetcoreapp
dotnet dev-certs https --trust
cd aspnetcoreapp dotnet watch run


Get Version

dotnet --list-sdks
dotnet --list-runtimes

  • Исполняемый файл dotnet
    C:\program files\dotnet\dotnet.exe

  • Пакет SDK для .NET
    C:\program files\dotnet\sdk\{версия}\

  • Среда выполнения .NET
    C:\program files\dotnet\shared\{тип среды выполнения}\{версия}\




воскресенье, 5 апреля 2020 г.

ASP.NET Core WebSockets support

OWIN in ASP.NET Core? ASP.NET Core vs selfhost ASP.NET

https://docs.microsoft.com/ru-ru/aspnet/core/fundamentals/owin?view=aspnetcore-3.1



Yes. In fact, all ASP.NET Core applications are self-hosted. Even in production, IIS/Nginx/Apache are a reverse proxy for the self-hosted application.
In a reasonably standard Program.cs class, you can see the self-hosting. The IISIntegration is optional - it's only necessary if you want to integrate with IIS.
public class Program
{
    public static void Main(string[] args)
    {
        var config = new ConfigurationBuilder()
            .AddCommandLine(args)
            .AddEnvironmentVariables(prefix: "ASPNETCORE_")
            .Build();

        var host = new WebHostBuilder()
            .UseConfiguration(config)
            .UseKestrel()
            .UseContentRoot(Directory.GetCurrentDirectory())
            .UseIISIntegration()
            .UseStartup<Startup>()
            .Build();

        host.Run();
    }
}

https://stackoverflow.com/questions/35997873/migrating-from-owin-to-asp-net-core

  • Middleware is quite similar between Katana and Core but you use HttpContext instead of IOwinContext.
  • Startup.cs is similar but there's much more DI support.
  • WebApi has been merged into MVC
  • DelegatingHandler is gone, use middleware instead.
  • HttpConfiguration has been split up into Routing and MvcOptions.

SignalR Asp.Net Core