Last post May 03, 2017 01:13 AM by bruce (sqlwork.com)
Mar 31, 2017 01:56 PM|BitShift|LINK
So Im getting my arms around all the changes with .NET core and one thing that struck me is the new architecture dealing with app pools.
After reading these two articles, Im wondering if we are being forced down this path of having our app code hosted in Kestrel and dealing with the IIS-Kestrel interactions?
For the most part, our team will never need to host on anything other than Windows and will often need enough other libraries / services etc such as Windows Workflow, that the full framework is needed.
Can I target the newer framework with an MVC application and still host my app with an application pool targeting the latest framework, and simply avoid Kestrel?
Our team is perfectly happy with MVC5 and the 4.5x framework configured App pools. Can we target 4.6x and avoid Kestrel ?
May 03, 2017 01:13 AM|bruce (sqlwork.com)|LINK
in short NO.
you can not run asp.net core in an IIS app pool. asp.net core runs on .net core, which does not support app pools, nor is app pool support planned. MVC 5 is the last version of MVC to run native on IIS. It should be supported for several years, but don't
expect many enhancements, except for third party nuget packages (but over time, many may not support the old framework).
asp.net core was written to run on a new high performance pipeline. IIS does not support this pipeline, so it will always proxy to the asp.net core pipeline. Also the new signal/r code will also run on this pipeline. MS is working on making kestrel first
class so IIS is not required, but this is still a ways out.
check this chart:
for the first time asp.net is faster than node.js
note: a release of .net standard 2.0 is scheduled this year. this is be the new common shared framework for .net core, and .net standard. as other libraries are ported to this new standard there may be more sharing between.