.NET 6 is not .NET Framework, it is .NET Core
You can see : Overview of porting from .NET Framework to .NET
MIgration from .NET framework 4.8 to .NET framework 6
We have custom applications built on .NET framework 4.8 and these have WCF services as well.
What are the things we need to do to migrate to .NET framework 6? Is there any documentation to help us achieve this seamlessly?
What are the things we need to keep in mind for this migration?
2 answers
Sort by: Most helpful
-
Castorix31 86,316 Reputation points
2022-03-31T17:25:28.017+00:00 -
Bruce (SqlWork.com) 68,311 Reputation points
2022-03-31T21:24:15.017+00:00 WCF may be one of your issues. While there is limited WCF client support in core, there is no server support. You should migrate to another technology. Microsoft recommends gRpc, or you can switch to REST (webapi).
you should also check if there are net core, or .netstandard 2.0+ versions for the NuGet packages you use.
the migration approach I often use, is to convert all library projects to .netstandard 2.0 first. This makes them compatible with .net 6, but keeps you to one code base during the conversion. then just the main project needs converting at the end.