Reputation: 533
There are a lot of articles all over the Internet about deploying of .NET Core applications to IIS server, but i still can not find clear answers to the following questions:
Thanks.
Upvotes: 3
Views: 965
Reputation: 239430
It's not managed code, which is to say that IIS is not loading a module to run it as it would with a traditional ASP.NET application, but the lifetime is still tied to the app pool like any other website hosted by IIS. Long and short, configure the app pool how you want it.
Again, the app pool is what matters in terms of starting and stopping. Each of your Core apps should be running in their own app pools, which then means you can independently start/stop each one on their own.
Yes, you can still use Web Deploy. Deployment is really totally separate from what is being deployed. The initial configuration of the site in IIS and the actual build that happens during publish takes care of all the Core-specific differences. Web Deploy is just moving files.
Upvotes: 1
Reputation: 466
I don't believe I'm an expert on this issue, but I can share my experiences hosting .net core web api behind IIS.
OT, Compared to Kestrel, my app (and all my POC apps) gets ~40% more rps when hosted on IIS.
Upvotes: 0