Last post Dec 02, 2015 12:57 PM by maherjendoubi
Dec 02, 2015 10:52 AM|lilpug|LINK
i am getting quite confused with the various different frameworks of aspnet 5. when i develop most of my web applications it will be on IIS, does this mean i should stick to using the .net 4.6.1 framework or should i be using the dnxcore50?
is the .NET framework going to become obsolete due to the dnxcore stuff in the future or will the .Net framework continuing to expand into newer version .Net 5, 6 etc as an underlining framework and does that mean aspnet 5 is just applying different framework
types to be used for different OS systems etc?
Dec 02, 2015 11:25 AM|maherjendoubi|LINK
when i develop most of my web applications it will be on IIS, does this mean i should stick to using the .net 4.6.1 framework or should i be using the dnxcore50?
If you use Windows, .net 4.6.1 is the full Framework. You can also use dnxcore50. IIS is only a reverse proxy to launch you dnx where your dnx46 or dnxcore50.
The .NET Framework is becoming a little by little a big set of nuget packages. You install only the package that you need.
Hope that help!
Dec 02, 2015 12:07 PM|lilpug|LINK
so for future stability i should be using 4.6.1 for now and then when the .NET frameworks starts to break into smaller modules just re-include the modules that have been segmented in the future?
Dec 02, 2015 12:15 PM|maherjendoubi|LINK
Exact, the goal one day is to install what we need from nuget. Even the whole Framework .NET will be available in the future versions on nuget and can be installed from there.
Dec 02, 2015 12:46 PM|lilpug|LINK
will this be available to dnxcore5 as well in the future or only 451 and 461?
Dec 02, 2015 12:57 PM|maherjendoubi|LINK
For dnxcore5 already done it's package designed system starting from the coreclr that you install from nuget feed.
But, for the full .NET Framework 451, 461 is getting more and more modular (nuget packages) in the future.