Skip to content
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

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

Closed
5 tasks
pranavkm opened this issue Feb 8, 2022 · 9 comments
Closed
5 tasks

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

pranavkm opened this issue Feb 8, 2022 · 9 comments
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions

Comments

@pranavkm
Copy link
Contributor

pranavkm commented Feb 8, 2022

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

Details

TBD

Issues

@ghost
Copy link

ghost commented Feb 9, 2022

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
Copy link

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
Copy link

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
Copy link
Contributor

slang25 commented Feb 18, 2022

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

@pranavkm
Copy link
Contributor Author

@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
Copy link

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

@twsouthwick
Copy link
Member

@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
Copy link

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
Copy link
Member

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.

@ghost ghost locked as resolved and limited conversation to collaborators Jul 4, 2022
@amcasey amcasey added area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions and removed area-runtime labels Aug 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions
Projects
None yet
Development

No branches or pull requests