3/12/2016

.NETCore1.0BornToProgram

.NETCore1.0
LastUpdated:30012016
Note:ASP.NET5isnowASP.NETCore1.0.and.NETCore5isnow.NETCore1.0.
In this aritcle we will discuss What is .NET Core 1.0 , Limitations and Issues with .NET
Framework.How.NETCore1.0willdealwiththoseissuesandAdvantagesof.NETCore1.0.
Latest version of Visual Studio is VisualStudio2015. With this release, Microsoft has forked .NET
into two streams. One is .NET Framework, now at version 4.6 , it is latest release of the familiar
.NETplatform.It'sasystemcomponentandworksonWindows.Theotheris.NETCore1.0,anew
moremodularframeworkdesignedfromthegrounduptobecrossplatform.
Actully there are two forks of Asp.Net (/Asp.Net/WhatisAsp.Net/) in Visual Studio 2015. One is
ASP.NET4.6andtheotherisASP.NETCORE1.0.
As ASP.NET 4.6 is latest release of familiar ASP.NET , it works on Windows and requires .NET
FrameworkasallpreviousversionsofASP.NET(i.eASP.NET4.5,ASP.NET4,...).
ASP.NET CORE 1.0 is a significant redesign of ASP.NET. It is built from ground up to provide an
optimizeddevelopmentframeworkthatisbothopensourceandcrossplatform.ASP.NETCORE1.0
can run cross platform (Windows,Mac,Linux). .Net Core 1.0 is basis of ASP.NET Core 1.0 , it is
.NETCORE1.0thatallowsASP.NETCORE1.0tobecrossplatform.

Whatis.NETCore1.0
.NET Core 1.0 is a modular runtime and library implementation that is subset of .Net Framework
http://borntoprogram.com/.Net/.NetCore/

1/4

3/12/2016

.NETCore1.0BornToProgram

(/.Net/.NetFramework/). As .Net Framework (/.Net/.NetFramework/) has two parts Framework

classlibraries(FCL)andCommonLanguageRuntime(CLR),the.NETCore1.0alsohastwoparts
1. .NET Core Libraries (CoreFX) These libraries are largely the same code as the .NET
FCL(Frameworkclasslibraries).Butthedependencieshasbeenremovedsothatsmallerset
oflibrariescanbeshiped
2. .NETCoreCommonLanguageRuntime(CoreCLR)It is a small runtime and built from the
same codebase as .Net Farmework CLR. It has the same GC (Garbage Collector) and JIT
(JustInTime) compiler , but it doesn't have other features like Code Access Security. It is
deliveredonNugetviaMicrosoft.CoreCLRpackage.
TheCoreCLRruntimeandCoreFXlibrariesaredistributedviaNuget.

LimitationsandIssueswith.NETFramework
Microsoftstartedtoworkon.NETFramework(/.Net/.NetFramework/)inlate1990s.Ithaschangeda
lot since then. But it still has limitations. As .Net Core 1.0 is basis of ASP.NET Core 1.0, we will
discussissueswith.NETFrameworkwhenusingitwithASP.NET
When we create Asp.Net application using Asp.Net 4.6 ( or any version of ASP.NET except
ASP.NETCore1.0),theremustbe.NETFrameworkinstalledonWebServer(/Web/Whatisa
WebServer/)wherewedeployourAsp.Netapplication.
.NET Framework can be installed only on Windows. It means that if we want to deploy our
ASP.NET 4.6 application on WebServer then we must buy Windows Hosting. We can't run
ASP.NET4.6application(orapplicatincreatedusingpreviousversionofASP.NET)onLinuxor
Macoperatingsystemwhiletargeting.NetFramework.
.Net framework is monolithic (all or nothing approach) and heavy. When we install .NET
FrameworkwenotonlygettheruntimebutalsotheentireFrameworkClassLibrary(FCL)with
it.Evenifourapplicationdoesn'tneedallthefeaturesofFCL,weareforcedtohaveentireFCL
onWebServer.
Since .Net Framework is monolithic ,it takes long time to release new version of .Net
Framework. It requires regorous reviews of any changes to maintain the compatibility of
existing applications. The combatibility issue tends to slow down the developement of the
runtime.IfourapplicationdependesonOperatingSystemruntimethenthereisalwaysriskthat
anupdatetotheOperatingSystemcouldbreaktheapplication.

Advantagesof.NETCORE1.0
Here we will discuss how .NET CORE 1.0 tackle the issues we discussed above and what are the
otheradvantagesofusing.NETCORE1.0
WecandeployCoreCLRwithourApplication,soourapplicatoinisnotdependentoninstalled
version of .NET Framework. .NET Core (CoreCLR + CoreFX libraries) is shipped by NuGet,
meaningwecanshipaprivateversionofthe.NetCoreFrameworkforourspecificapplication.
ActuallynowwecanhostmultipleapplicationeachtargetingdifferentversionofCoreCLRand
updatethemindividually.Itmeansthatotherapplicationversionscan'tchangeourapplications
behavior.It also eliminates the risk that updating the operating system could break the
application.
Anotherimplicationisthatthosedevelopersworkingonthe.NetCoreitselfhavealittlemore
http://borntoprogram.com/.Net/.NetCore/

2/4

3/12/2016

.NETCore1.0BornToProgram

freedomtomakechangeswithoutbreakingdeployedapplications.
.CoreFXLibrarieshasbeenbuildinawaythatthereareminimumsetoflibrarydependencies.
This means that with CoreCLR we can ship only the CoreFX libraries that is needed by our
application..CoreFX Libraries are not included by default as part of the .NET Core install It
allows us the developers to import just the parts of the Framework that we need for our
projects. The componentised design for CoreFX means that unnecessary code is kept to a
minimum. .NET Core is designed to use the standard library in a more sophisticated way
whereas.NETFrameworkisanallornothingmonolith
We can target single set of CoreFX that is supported by multiple platforms. One of the main
limitationsoftheNETFrameworkwasthatitfailedtosharecodeacrossplatforms.NETCore
willprovidedeveloperswithalibrarywhichcanbedeployedovervariousplatforms
.NETCoreiscrossplatform.NETCoreisnotonlyavailableontheWindowsplatformbutalso
on Mac and Linux. What is means that Web Developers now can build ASP.NET Web
applicationsthatcanrunonanysystem(Windows,Mac,Linux)
TheNETFramework,whichincludesdesktopGUIlibrariesandsupportforolderversionsofASP.NET
willremainstiedtoWindows,butthenew.NETCoresubsetwillbeofficiallysupportedonLinuxand
Mac as well. ASP.NET Core 1.0, is compatible with both .NET Core and the .NET Framework. On
Windows, the developer can choose which runtime to use. Crossplatform ASP.NET Core 1.0 must
use.NETCore.

.NETCore1.0isnotfor
ASP.NET Core 1.0 applications can target .NET Core 1.0 , but it is not for Desktop applications ,
ASP.NETWebFormapplications
The.NETCoreprojectdoesnotcoverdesktopapplicationssuchasthosebuiltwithWindows
PresentationFoundation(WPF)orWindowsForms.becausetheseframeworkshavetoomany
Windowsspecificdependencies.
We can't create ASP.NET WEB Forms application that can target .NET Core 1.0 . ASP.NET
Core 1.0 just includes (Web API and MVC). In future it may have SingleR or Web Pages but
ASP.NETWebFormswillnotbepartofASP.NETCORE.
For updates Like, Follow and Share us using the footer below or by Visiting Contact Us
(/Home/Contact/)page.

RelatedTopics
.NetFramework(/.Net/.NetFramework/)
Getting Started With ASP.NET Core MVC 1.0 (ASP.NET Core 1.0) (/Asp.NetMVC/Getting
Started/)

(http://clicky.com/100895171)
http://borntoprogram.com/.Net/.NetCore/

3/4

3/12/2016

http://borntoprogram.com/.Net/.NetCore/

.NETCore1.0BornToProgram

4/4