.net-core-2.0

I know that C# version depends on .NET Framework . But .NET Core which version uses? Particularly .NET Core 2? C#7? .NET Core 2.0 references Roslyn 2.3, which corresponds to Visual Studio 2017 version 15.3 and supports C# 7.1. The C# what's new version history page gives a list of all versions plus their associated Visual Studio and .NET core version: C# 7.3 Visual Studio 2017 version 15.7, and in the .NET Core 2.1 SDK 2.1.300 RC1 C# 7.2 Visual Studio 2017 version 15.5, and in the .NET Core 2.0 SDK. C# 7.1 Visual Studio 2017 version 15.3, and in the .NET Core 2.0 SDK. C# 7.0 Visual Studio 2017

I've been trying to get my TypeScript files compiled to JavaScript files in my CI build process on VSTS. Once the JavaScript files have been generated then my gulp file process can process them to the wwwroot folder. The project builds fine in Visual Studio 2017 with VS obeying the tsconfig.json file by compiling the file on change and then the Task Runner running the gulp file on detected changes and build. All the correct files are genereated when building or publishing locally in Visual Studio. When trying to set up my build process in VSTS as part of my CI/CD process the C# code is built

I'm working on a .NET Core CLI app that needs to reference a 3rd party NuGet package that has not been published with a netcoreappX.X target. I've run the Analyze Project Portability tool on it and got 100% compatibility, which is expected, as this is a relatively simple library. The problem then comes in the form of this annoying NuGet warning: Warning: NU1701 Package 'XXXXXX 1.0.0' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETCoreApp,Version=v2.0'. This package may not be fully compatible with your project. Is there a way to hide this warning

I have followed a few tutorials and have gotten this to work at work but for some reason I am not able to get the UI to display but the Swagger Json is created. Last tutorial I looked at is here . My setup is like so: Nuget Package: Swashbuckle.AspNetCore(1.0.0) ConfigureServices Method: services.AddSwaggerGen(options => { options.SwaggerDoc("v1", new Info { Title = "MediatR Example", Version = "v1", Description = "Trying out the MediatR library to simplify Request and Response logic.", TermsOfService = "WTFPL", Contact = new Contact { Email = "", Name = "", Url = "https://github.com

I'm using dotnet core I want to setup a LinkedIn authentication on the site since there is no default authentication builder for LinkedIn as facebook, google and twitter I decided to use the generic implementation as follows: services.AddAuthentication().AddOAuth("LinkedIn", c => { c.ClientId = Configuration["linkedin-app-id"]; c.ClientSecret = Configuration["linkedin-app-secret"]; c.Scope.Add("r_basicprofile"); c.Scope.Add("r_emailaddress"); c.CallbackPath = "/signin-linkedin"; c.AuthorizationEndpoint = "https://www.linkedin.com/oauth/v2/authorization"; c.TokenEndpoint = "https://www.linkedin

I'd like to implement a page internal to my application that appears when the blazor router is unable to find a matching route. Currently, all requests are routing to index.html so I'm unable to handle errors through iis as I may normally. If I enter an invalid route, I will be shown a blank page (which is actually index.html ) and receive a console error: 'Router' cannot find any component with a route for '/some/Nonexistent/Route'. It seems like I should be able to handle this since the blazor router is able to recognize that there is no route defined which matches the requested route