.NET
Microsoft Technologies based on the .NET software framework.
3,437 questions
I can't Migrate from .Net Framework 4.8 to .Net 8 (As happens to the vast majority)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 26%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZ%3C/text%3E%3C/svg%3E)
zequion
111
Reputation points
I have several Asp.net, Winforms and Wpf projects and use several dll projects that are common in C#.
I am trying to migrate from .Net Framework 4.8 to .Net 8. I am finding that there is a long series of basic commands that are not available in .Net and that I cannot remove because it would take a long time to achieve it, perhaps years.
I have used the Update assistant and the Microsoft.Windows.Compatibility nuget package and it doesn't solve anything for me.
.NET Portability Analyzer is not supported in Visual Studio 2022 IS THIS A JOKE?
The vast majority of projects that have been carried out so far are using the .Net Framework with no real possibility of migrating .Net. Am I the only one who says it? Have Microsoft not found out that it is science fiction to reprogram everything to .Net and that they are not updating .Net Framework 4.8? In what remote galaxy are they alien to reality?
Why can't I use a dll compiled in .Net 8 and other dlls compiled in the .Net Framework even if they work slower?
What do we do with other people's dlls, such as screen controls that are from other manufacturers, some of which have closed their company? They are never going to create a Nuget package or we can't wait for them to do so to build the entire project.
Do we throw it all away because Microsoft doesn't care about compatibility?
How can you abandon Asp.Net WebForms because they created Blazor? It is a perfectly acceptable technology and they are turning their backs on the millions of people they have convinced to use it !!
Where is the documentation that goes command by command saying: "This command is no longer supported, change it to this other one?" They just say that the command is not supported and that's it? And how do I get the program working again? I've read that Microsoft says: "Contract that command from another manufacturer." That's about being unpresentable people who don't care about the work of millions of people.
Do I have to spend the next 30 years with .Net Framework 4.8 for which they do not provide maintenance?
What do we have to do Microsoft? I at least want a technical answer from someone responsible who has their feet on the ground.
-.NET Framework technologies not available in .Net: https://learn.microsoft.com/es-es/dotnet/core/porting/net-framework-tech-unavailable
-List of Unsupported APIs: https://learn.microsoft.com/es-es/dotnet/core/compatibility/unsupported-apis
.NET
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 85%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJX%3C/text%3E%3C/svg%3E)
Jiale Xue - MSFT 34,506 Reputation points Microsoft Vendor2024-04-30T08:47:05.5733333+00:00 Hi @zequion , Welcome to Microsoft Q&A,
I totally understand your frustration. Migrating a large project from .NET Framework to .NET is indeed a daunting task, especially when there are a lot of dependencies and third-party libraries involved. Let’s break down your concerns and see how we can address them:
It is true that not all APIs and features available in the .NET Framework are directly compatible with .NET. As you found the information.
Unfortunately, mixing assemblies targeting .NET and .NET Framework in the same project is not supported. However, you can encapsulate the functionality of existing .NET Framework libraries into .NET Standard or .NET Core libraries. You may want to take a phased approach and gradually migrate these libraries to .NET. :
Third-party dependencies, especially those without ongoing support, can pose significant challenges. In this case, you may need to continue using the .NET Framework, or look for alternative libraries that support .NET.
Rather than trying to migrate everything at once, consider a phased approach. Start by migrating smaller, simpler components and gradually move to larger components.
If you have any questions later, you are welcome to ask them in time.
Sign in to comment