Should point out the obvious disadvantage with Windows Containers

This article pretty much says, use .Net 5 if possible but in some scenarios, you need to use Windows Containers.

1. Dotnet core 2/3 might be a more sensible choice over .Net 5, there are many breaking changes so .Net 5 is not always an option
2. Windows server containers are MUCH larger than Linux running dotnet core and this should be stated since it is a significant factor in deciding when to migrate to containers and or migrate an app to a new framework. If you have eg. 20 netfx apps, containerizing them might be out of the question (320GB for 1 instance of each).

Other options are leaving some apps as they are on vanilla Windows Servers running on IIS and possibly migrating side-by-side using a proxy to send some pages to a new containerised "microservice" while maintaining old pages in the old app in IIS.

---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: 5cd6c575-bd46-941d-138a-c705043f16e6
* Version Independent ID: 5b6081ff-c221-851f-a3fb-63d4f2aa1b44
* Content: [When to choose .NET Framework for Docker containers](https://docs.microsoft.com/en-us/dotnet/architecture/microservices/net-core-net-framework-containers/net-framework-container-scenarios)
* Content Source: [docs/architecture/microservices/net-core-net-framework-containers/net-framework-container-scenarios.md](https://github.com/dotnet/docs/blob/main/docs/architecture/microservices/net-core-net-framework-containers/net-framework-container-scenarios.md)
* Product: **dotnet-architecture**
* Technology: **microservices**
* GitHub Login: @nishanil
* Microsoft Alias: **nanil**