Thanks as always Marco.

Is there any update to this Marco? We are getting a lot of pressure to offer .net core.

We have seen in some situations where leaving the appPool set does not work. I would also have to say it is a performance drain if the appPool is not set to none. as the original asp.net pipelines are still being processed during requests.

The changes required for solid to support .net core are simple, provided that you have setup your server correctly.

From solid's code though, they would simply need to the change the application pool to one that is defined as either no managed code or what ever you have referenced your new application pool as.

@marco + trevor - this should be an easy addition on your end

Unfortunately this isn't an easy addition.

You can take a look at the IIS code in the Server sln, the way it's scripted requires to re-write alot of codes and soap calls.

therefor alot of time is required to make this small change.