Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

.NET Core doesn't depend on any installation?

I've been reading about .NET Core and it seems really cool.

There is just one thing that is making me think and I haven't read it anywhere: when I set my asp.net 5 web app to target .NET Core and deploy it, this app doesn't depend AT ALL on the .NET framework installed on the machine that's going to host it?

I mean, the assemblies deployed already contain the CLR, the BCL and the project dependencies? So I can have mutiple web apps hosted in one single machine with different versions of .NET Core, right?

like image 210
gabsferreira Avatar asked Jun 23 '15 19:06

gabsferreira


People also ask

Does .NET Core need to be installed?

You only need to install . NET Core components if you want to host a self-contained ASP.NET Core application from IIS, since you will need an IIS module to bootstrap the application. You can use this approach though to run newer or preview versions of the . NET Core runtime that you don't want to install globally.

Does .NET Core need to be installed on server?

NET Framework on the same machine. They are designed to allow them to be installed side-by-side. However you do need to install the . NET Core runtime onto the server to allow the code to be run because the OS has native dependencies that need to be present.

Which ASP.NET Core no longer depends on the system?

Fast: ASP.NET Core no longer depends on System. Web. dll for browser-server communication. ASP.NET Core allows us to include packages that we need for our application.

What are the disadvantages of .NET Core?

ASP.NET Core ConsIt will take a few years till existing products based on . NET Core will be fully updated. Though there are a lot of . NET developers on the market, ASP.NET Core framework is a huge step forward comparing to ASP.NET Framework and there are many changes and new concepts.


1 Answers

I mean, the assemblies deployed already contain the CLR, the BCL and the project dependencies?

They ship with whichever dependencies are in your project.json file. If you choose to deploy CoreCLR, the runtime will be shipped with your app in order for different apps to be able to run on whichever framework version they consume, side by side. The point is that all of the BCL is slowly packaged into separate NuGet packages which ship with your app, step by step removing the need to deploy the entire BCL.

like image 194
Yuval Itzchakov Avatar answered Sep 28 '22 01:09

Yuval Itzchakov