Theme: Enterprise and LTS

[jamshedd]

.NET 6.0 will be a Long-Term Support (LTS) release. We see many enterprises prefer our LTS releases over Current releases for their longer support (relative to Current releases), they pick an LTS version so they don’t have to move forward every year. This is not very different from what we see with OS LTS versions – enterprise customers go from one LTS to the next and skip the in-between SAC releases. Since .NET 6.0 will be the successor to 3.1 LTS we expect customers presently using 3.1 LTS and wanting to target the next LTS will pick 6.0 LTS. We will support 3.1 through December 2022, so once .NET 6.0 ships, customers will have 1 year to plan for, rebuild and test their apps and complete their deployment. Customers that cannot migrate their apps to 6.0 in this timeframe will probably ask us to provide longer support.

If customers can successfully complete their migration forward in this 1-year period everyone benefits. So, it is in everyone’s interest that we do everything we can to enable customers to come forward to 6.0 as easily, smoothly and quickly as possible.

Epics under this Theme:

• Enterprises have a first class experience acquiring and deploying .NET 6.0.
• .NET Core is supported in air-gapped environments/private clouds.
• Enterprises get first-class support when using .NET 6.0 on Linux.
• Linux package support is reliable and complete
• .NET Core can be reliably built from source
• Path to migrate an app from Framework to .NET 6.0 is well understood and streamlined
• Ensure positive experience for .NET acquisition using Linux package managers runtime#54519

[weedkiller]

Build in Drop in options for ASP web MVC & cloud apps Identity with Tenant, Users, Groups (Like LDAP), Authentication and UI management.

Multitenant Groups Management is not trivial and still missing in .NET unlike JAVA JSR native support.

This complexity of this implementation leaves the apps on .NET framework vulnerable, this reference or template implementation should be provided by Microsoft (so that people can refer security threats to Microsoft) and not to the developer to implement this is, its beyond his scope - this is serious security issues.