Difference between using the ASP.NET Core Web Application (.NET Core) with net461 set as the only framework and using the (.NET Framework) template

With the release of .NET Core RC2 Microsoft made it so there are now 3 Web Application templates:

  • ASP.NET Web Application (.NET Framework) — The old
  • ASP.NET Core Web Application (.NET Framework) — the new, to be hosting on Windows only
  • ASP.NET Core Web Application (.NET Core) — Linux, OSX, Windows

I am trying to use the new Core Web Application template but without trying to target Linux, OSX, Windows so it seems like the ASP.NET Core Web Application (.NET Framework) is perfect for me. It took me a while but I learned that in order to add a class library that will work with this project type you need to add a Class Library (.NET Core) and change the frameworks section to only be net461 to match the Web Application.

"frameworks": {
    "net461": { }
}

My Question:

What is the difference between creating a ASP.NET Core Web Application (.NET Core) and in project.json making net461 the only target framework

and

just creating a ASP.NET Core Web Application (.NET Framework) project which only includes net461 by default.

Are there other difference that I am not aware of like the way the the projects are published, etc.?

What's the difference between Class Library and .NET Core Class , NET Core) template and target netstandard1.3 or higher in your library. To do that, I added a project reference in the ASP. NET Core) with net461 set as the only framework and using the (.NET Framework) template. With the release of . NET Core RC2 Microsoft made it so there are now 3 Web Application templates: ASP� ASP.NET Core is a redesign of ASP.NET 4.x. This article lists the differences between them. ASP.NET Core. ASP.NET Core is an open-source, cross-platform framework for building modern, cloud-based web apps on Windows, macOS, or Linux. ASP.NET Core provides the following benefits: A unified story for building web UI and web APIs.

First see the difference in project.json files when you create ASP.NET Core Web Applications targeting different frameworks.

As per your question, if you change the framework in ASP.NET Core Web Application(.NET Core) project.json only to have net461 and save, it'll restore the packages and will give the following error.

If you remove Microsoft.NETCore.App dependency and saves the file, It'll again restore the dependencies and won't give any error.

If you notice the first image, this has finally become a ASP.NET Core Web Application with .NET Framework.

Can a .NET Core Web app consume .NET Framework class libraries , Difference between using the ASP.NET Core Web Application (.NET Core) with net461 set as the only framework and using the (.NET Framework) template. Microsoft has just announced .NET 5, which will be available in 2020. .NET 5 will replace .NET Core and is the future of .NET Framework and .NET Core. .NET 5 will not support ASP.NET Web Forms, WCF, or WWF. UWP also does not have a major role to play in the future. Read here to learn more about the future of .NET.

I was confused at first as well. The main difference is that ASP.NET Web Application (.NET Framework) is the normal asp.net that we have been using. It contains App_Start folder web.config, Global.asax etc.. (Like MVC5,You get the idea..).

Whereas ASP.NET Core Web Application (.NET Framework) is a core framework(MVC6). (Not dependent on System.Web). Brand new project.json.. startup.cs and program.cs etc... And it supports all the old libraries of .net framework as well.

Use ASP.NET Core APIs in a class library, App shared framework, which is installed with the . As of .NET Core 3.0, projects using the Microsoft.NET.Sdk.Web MSBuild SDK implicitly� The ASP.NET MVC is used to build Web applications in .NET Framework. 2] .NET Core The .NET Core is the new open-source and cross-platform framework to build server applications that run on Windows, Linux and Mac operating system. The .NET Core supports UWP and ASP.NET Core only. UWP is using to build Windows and mobile applications. ASP.NET

with .net core, you can run your web pages application in Linux or mac os whereas the .net will only be good for windows, i.e. less portable.

Choose between .NET Core and .NET Framework for server apps , However, there are fundamental differences between the two and your choice Use .NET Framework for your server application when: Your app currently uses . It's a Windows component, and only one version can exist on a NET Framework. ASP.NET Core cannot be used for ASP.NET Web Forms. So now you can build web application using ASP.NET Core 1.0 and you can target .NET Framework 4.6 and/or .NET Core. The .NET Framework 4.6 runs on top of Windows operating system, where .NET Core 1.0 is a cross platform framework and runs on top of Windows and Non-windows operating systems.

Choose between ASP.NET 4.x and ASP.NET Core, NET Core vs. ASP.NET 4.x and how to choose between them. This article lists the differences between them. framework for building modern, cloud-based web apps on Windows, macOS Multiple versions per machine, One version per machine Use .NET Core runtime, Use .NET Framework runtime� Getting Started with .NET Core course: https://www.iamtimcorey.com/p/getting-started-with-net-core Patreon: https://www.patreon.com/IAmTimCorey Mailing List:

Custom templates for dotnet new, Web � Mobile � Cloud The dotnet new command isn't only the way to use a template, but also NET Core 2.0, you can create your own custom templates for any files, including console apps, class libraries, unit test projects, ASP. The <TargetFramework> setting must be set, even though the binary� ASP.NET Core is one of the key components of .NET Core to build Web applications, using ASP.NET. Jeff Fritz from Microsoft writes in his article, Should I Use ASP.NET Core or MVC 5 : "Both frameworks will still be supported in at least 4 years.

Getting started: .NET Core with command line > xUnit.net, Getting Started with xUnit.net. Using .NET Core with the .NET SDK command line NET Core, showing you how to write and run your first set of unit tests. generated templates may differ for you, depending on which version you're using. The former is the unit testing framework, and the latter is the library that enables� Others don’t apply to the new application patterns targeted by .NET Core and may never be available. The following list shows the most common technologies not found in .NET Core: ASP.NET Web Forms applications: ASP.NET Web Forms are only available in .NET Framework. ASP.NET Core cannot be used for ASP.NET Web Forms.

Comments
  • This is all true but it doesn't address the question. In short, he's asking for a comparison of the 2 ASP.NET Core options, not the "old" ASP.NET option.