Updating net applications
This is actually a recommended practice on Windows in order to provide port 80/443 forwarding which kestrel doesn't support directly. NET Core SDK on your Dev machine) the Asp Net Core Module is available in the IIS native module list: The Asp Net Core Module is a native IIS module that hooks into the IIS pipeline very early in the request cycle and immediately redirects all traffic to the backend ASP. All requests - even those mapped to top level Handlers like bypass the IIS pipeline and are forwarded to the ASP. While the IIS Site/Virtual still needs an IIS Application Pool to run in, the Application Pool should be set to use No Managed Code.For Windows IIS (or another reverse proxy) will continue to be an important part of the server even with ASP. Since the App Pool acts merely as a proxy to forward requests, there's no need to have it instantiate a . The Asp Net Core Module's job is to ensure that your application gets loaded when the first request comes in and that the process stays loaded if for some reason the application crashes.
The package mono-complete should be installed to install everything - this should cover most cases of "assembly not found" errors.
The package mono-dbg should be installed to get debugging symbols for framework libraries - allowing you to get line numbers in stack traces.
To try the latest planned changes, check the nightly packages download page.
NET Core applications and plan on running them on IIS, you'll find that . NET Core runs in the context of IIS and how you can deploy your ASP. The most important thing to understand about hosting ASP. NET application everything is hosted inside of an IIS Worker Process (w3wp.exe) which is the IIS Application Pool. NET application and your application is instantiated by the built-in ASP. NET application pipeline as requests come in from the native driver.
Please visit the Mono Develop website for more details about our cross-platform IDE.