upgrade-assistant
sscli20_20060311
| upgrade-assistant | sscli20_20060311 | |
|---|---|---|
| 14 | 1 | |
| 1,074 | 24 | |
| 0.9% | - | |
| 3.2 | 10.0 | |
| 6 days ago | over 6 years ago | |
| C# | C# | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
upgrade-assistant
- .NET Framework 3.x Upgrade
-
Questions about upgrading our projects from .NET Framework 4.6.1 to .NET 6.0/Standard 2.0
You may wish to look into the tooling MS provides to help you upgrade your projects in this exact scenario: https://github.com/dotnet/upgrade-assistant
-
Visual Studio .NET Upgrade Assistant extension released (devblogs.microsoft.com)
there's already open source cli tool https://github.com/dotnet/upgrade-assistant
- Any interest in a tool to *help* the .NET Framework --> .NET Core/6 conversion process?
- converting framework4.8 webapps to NetCore (Net5,6,7). any apps available to help?
-
.NET MAUI and .NET 6/7 we feel the assembly hell again
There are a few tools that can help in the process. Years back I used a tool named Project2015to2017: https://github.com/hvanbakel/CsprojToVs2017. Since then, Microsoft also released a tool: https://github.com/dotnet/upgrade-assistant. There was also this tool but it looks like it has been discontinued: https://github.com/microsoft/dotnet-apiport
- Sanity check, please!
-
Moving from .NET Framework to .NET 6
I'm looking to move one of our software suites from .NET Framework 4.7 to .NET 6. A lot of online guides recommend starting with the Microsoft conversion tools to ease/speed up the process. There seem to be two tools that are used for it try-convert and upgrade-assistant. However, I'm not sure I understand the difference between them and when should I use which tool (assuming that it matters).
-
20 Years of .NET
Where's the issue? https://github.com/dotnet/upgrade-assistant/issues
sscli20_20060311
-
20 Years of .NET
It was pretty much always open source and cross platform. The original version wasn't even developed on windows: https://github.com/SSCLI/sscli20_20060311
Although being open source and free doesn't necessarily make it open and accessible. The core CLR team do not listen to customers, particularly ones who complain about not wanting telemetry by default in there, ones who open bugs in the HTTP stack which spam logs for months and months and months and complete deadlocks and crashes.
Open Source has only completely absolved Microsoft of any responsibility to support their products to actual paying customers, who are told to open github issues now which are auto-closed after being ignored.
What are some alternatives?
try-convert - Helping .NET developers port their projects to .NET Core!
MinimalApiPlayground - A place I'm trying out the new ASP.NET Core minimal APIs features.
designs - This repo is used for reviewing new .NET designs.
Giraffe - A native functional ASP.NET Core web framework for F# developers.
Vue3WebpackBoilerplateV2 - Advanced setup for Vue.js 3 project using webpack with many custom components
porting-assistant-dotnet-client - The 'Porting Assistant for .NET' is a standalone compatibility analyzer that helps customers to port their .NET Framework (“.NET”) applications to .NET Core on Linux.
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
CsprojToVs2017 - Tooling for converting pre 2017 project to the new Visual Studio 2017 format.
dotnet-apiport - This repo contains .NET Portability Analyzer (VSIX and Console) libraries and tools
haxe - Haxe - The Cross-Platform Toolkit
YARP - A toolkit for developing high-performance HTTP reverse proxy applications.