[Theme] Add support for migrating .NET Framework apps to .NET Core

[pranavkm]

This issue tracks several related items involved in our ongoing effort to help migrate .NET Framework apps to .NET Core.

Details

TBD

Issues

• Add missing documentation for integrating Owin-based apps with ASP.NET Core Provide documentation to use Owin correctly with ASP.NET Core  #39943
• VS tooling to support YARP based migration insert AzDo issue here
• Produce adapters for System.Web.HttpContext Produce a System.Web.HttpContext adapter based on ASP.NET Core HTTP types #40001
• Identify way to share session state with "backend" System.Web app - [Migration] Figure out a story for sharing session state with ASP.NET apps #40079
• Support sharing auth state with "backend" System.Web app - [Migration] Support sharing auth state with "backend" System.Web app #40083

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[alexkozler]

Can you guys confirm VB is effectively abandoned for newer .NET?
There's not really any viable roadmap I've seen to migrate from .NET 4.8 in VB to .NET 5/6/7 in VB... so the only real option is a complete and total rewrite from scratch.

[KathleenDollard]

We have not abandoned VB in newer versions of .NET.

Before .NET Core, ASP.NET stopped supporting VB except for WebAPI (there is no Razor engine). If you are writing web apps there are ways to work around this. Overall the experience of changing to newer .NET is about the same for a C# or VB project.

If you have a more specific issue or concern, VS Feedback is one venue you can use for a more focused discussion.

[slang25]

Is an approach like IISCrossover being considered in scope for this theme? I think this would really help unblock many teams.

[pranavkm]

@slang25 we are working on a solution using YARP instead. We'd initially considered IISCrossover, but realized that outside of a few limited scenarios we need to solve the same problems with it that we also run in to with YARP. Given YARP is production-ready, we decided to base our solution on it.

[VenkateshSrini]

Is there a tool that you are planning to do this migration or is this going to be only documentation updates

[twsouthwick]

@VenkateshSrini There's some VS tooling to enable the YARP integration as well as some runtime changes being explored. The list in the first comment contains the areas being explored currently as part of this theme. For more details on them, you can click on the associated link.

[gumbarros]

Can you guys confirm VB is effectively abandoned for newer .NET? There's not really any viable roadmap I've seen to migrate from .NET 4.8 in VB to .NET 5/6/7 in VB... so the only real option is a complete and total rewrite from scratch.

You can use this extension to convert your VB code to C# and then convert it to .NET Core:
https://marketplace.visualstudio.com/items?itemName=SharpDevelopTeam.CodeConverter

[adityamandaleeka]

Update: we've just released a preview of this work, with more to come. Here's a blog post with more information (including a video of a BUILD talk about it): https://devblogs.microsoft.com/dotnet/incremental-asp-net-to-asp-net-core-migration/

The work is being done in https://github.com/dotnet/systemweb-adapters so please file your issues/requests about it there. I'll close this issue now.