-
Notifications
You must be signed in to change notification settings - Fork 10.3k
[Announcement] : AspNetCoreModule V1 removed from Windows Hosting Bundle #7095
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It wasn't obvious to me from the announcement exactly what this would break, if anything. If I'm running .NET Core 2.0 (yes I know), 2.1, and eventually 3.0 web apps on the same server, should I be concerned about upgrading with the latest Windows Hosting Bundle installer causing any problems with the applications? |
Since releases of ANCM were never publicly talked about, could you please clarify what ASP.NET Core versions each of the ANCM versions supports? i.e. is ANCM v1 required only for ASP.NET Core 1.x, and ANCM v2 can run ASP.NET Core 2.x and 3.x? |
@jeremycook added a section about what exactly breaks. Existing 2.1/2.2 application would not be affected by this. |
AspNetCoreModule V1 is supported with ASP.NET Core 2.1/2.2 AspNetCoreModule V2 is supported with ASP.NET Core 2.2/3.0/onward |
Cool, thanks! So basically, v2 added the in-process support I guess? Btw. it’s still possibly to install both v1 and v2 on the same machine by installing the Hosting Bundle for e.g. both 2.1 and 3.0, right? |
Yes
Yes |
Suggest to release the |
We periodically close 'discussion' issues that have not been updated in a long period of time. We apologize if this causes any inconvenience. We ask that if you are still encountering an issue, please log a new issue with updated information and we will investigate. |
Discussion thread for aspnet/Announcements#339
The text was updated successfully, but these errors were encountered: