ANCM in-process

[glennc]

Uber issue for supporting in-process hosting in ANCM.

Initial testing has shown that an in-process hosting option in ANCM will provide significant performance and diagnostic gains when running with IIS.

In-process will not be the default hosting model for some time.

[glennc]

@jkotalik outside of not being able to have multiple apps in a single app pool I am not clear what all the downsides to in-proc are. Are there other limitations?

[DamianEdwards]

Clarification regarding "default": it is intended that in-process would become the default for new ASP.NET Core projects targeting 2.1 or higher.

[jkotalik]

@glennc I don't think there are other main downsides from a customer standpoint, besides being windows specific.
@DamianEdwards are we still under the assumption that in-proc will be the default, but opt-in for 2.1?

[DamianEdwards]

The assumption is that new 2.1 projects use in-proc, existing apps or projects updated to 2.1 would not. We need to design how to make that happen.

[Tratcher]

It's a new project setting you would add to the template (launch settings?). New projects would get it but upgraded ones wouldn't have it.

On a different note, making this the default for 2.1 is aggressive from a quality perspective. The last schedule I saw did not include any public previews with a working tooling experience so we'll get minimal feedback before 2.1 releases.

The other new restriction is that the bitness of your app (and installed runtime) will now have to match the bitness of your app pool.

[John0King]

Does this allow us to direct copy/replace files without stop application pool first ?

[jkotalik]

@John0King Today you can drop an app_offline.htm in the application directory to stop your application. I'm assuming you are referring to shadow copying, which is not a change that will be done through this feature.