Dr. David E. V.
Posted
I really love WinHost
I really love WinHost, but the "work around" to use ASP.NET Core is unacceptable. If you advertise that you run ASP.NET Core, you should run it in native Framework-Dependent Deployment (FDD) mode, not in a work-around, Self-Contained Deployment (SCD) mode. The SCD method creates HUGE deployment artifacts, which take 30-60 seconds to load, even on a Premium account footprint. My customers don't accept that lack of response time. I am deploying my next application site to Azure. The cost may be more, but the enhanced response time and ability to publish in FDD mode is worth the change in scenery and the increased cost.
Response from Winhost· Sep 22, 2017
Hi David. First of all, we love you too, and we hear what you're saying. But we do support Framework-dependent .NET Core on the web servers. We recommend Self-Contained Deployment for anyone who wants to use very recent versions of .NET Core, because we'll never be completely up-to-date with those latest versions. The problem with Core form our perspective: their rapid development cadence is skewed toward virtual server "cloud" platforms like Azure that can be updated every few weeks or 10 days or whenever the Microsoft engineers feel like dropping the latest version. But on a traditional server platform like we run - we can't update a framework on a hundred servers every couple of weeks. It isn't feasible. And more than that, it isn't responsible on a shared platform. We have to test updates before we run them, or we risk the health of our entire platform. We tried to keep up at first, but by the time we'd finish testing the latest version of Core they would have released another version. So it's untenable for us. The .NET Core "slow development" version that we use, the one geared toward enterprise and platforms like ours - that version lags behind the latest bleeding edge version. By design. It's behind so they can ensure its stability. So that's where we're at with Core. We're sorry if we left you feeling like we promised something that we couldn't deliver. That's never our intention. But again, we do support Framework-dependent .NET Core on the web servers. Just not the very latest version(s).