In ASP.NET Core 3.0 and higher, RazorViewEngineOptions.AllowRecompilingViewsOnFileChange is not available. Surprised that refreshing a view while the app is running did not work, I discovered the following solution: Add Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation NuGet package to the project Add the following in Startup.cs: services.AddControllersWithViews().AddRazorRuntimeCompilation(); Here’s the full explanation for the curious.
Yes, ConfigurationManager.AppSettings is available in .NET Core 2.0 after referencing NuGet package System.Configuration.ConfigurationManager. Credits goes to @JeroenMostert for giving me the solution.
Installing Microsoft.NET.Test.Sdk package from nuget package manager solved my issue.
The expression parameter (x in this case) of the factory delegate is an IServiceProvider. Use that to resolve the dependencies: _serviceCollection.AddSingleton<IService>(x => new Service(x.GetRequiredService<IOtherService>(), x.GetRequiredService<IAnotherOne>(), “”)); The factory delegate is a delayed invocation. Whenever the type is to be resolved, it will pass the completed provider as the delegate parameter.
You can use [FromQuery] to bind a particular model to the querystring: https://docs.microsoft.com/en-us/aspnet/core/mvc/models/model-binding e.g. [HttpGet()] public IActionResult Get([FromQuery(Name = “page”)] string page) {…}
I found the solution, in the following official documentation “Migrate from ASP.NET Core 2.2 to 3.0”: There are 3 approaches: Replace UseMvc or UseSignalR with UseEndpoints. In my case, the result looked like that public class Startup { public void ConfigureServices(IServiceCollection services) { //Old Way services.AddMvc(); // New Ways //services.AddRazorPages(); } public void Configure(IApplicationBuilder app, … Read more
If it’s a framework-dependent application (the default), you run it by dotnet yourapp.dll. If it’s a self-contained application, you run it using yourapp.exe on Windows and ./yourapp on Unix. For more information about the differences between the two app types, see the .NET Core Application Deployment article on .NET documentation.
Update 2020: Do note that ASP.NET Core 3 and higher now depend on .NET Core and can no longer be used on .NET Framework. The below description is for ASP.NET Core 1.x-2.x; the layer separation still holds true for ASP.NET Core 3.0 but the ASP.NET Core layer can no longer be used on top of … Read more
I will try to further clarify your doubts and extend Jon Skeet answer. .NET Standard is a specification, so a library compiled for a specific .NET Standard version can be used in different .NET Standard implementations. As said in my other comment, a good analogy for the relationship between .NET Standard and other .NET Standard … Read more
As a general rule, converting a Web Forms or MVC5 application to ASP.NET Core will require a significant amount of refactoring. HttpContext.Current was removed in ASP.NET Core. Accessing the current HTTP context from a separate class library is the type of messy architecture that ASP.NET Core tries to avoid. There are a few ways to … Read more