upgrade-assistant
porting-assistant-dotnet-client
| upgrade-assistant | porting-assistant-dotnet-client | |
|---|---|---|
| 14 | 1 | |
| 1,074 | 143 | |
| 0.9% | 0.0% | |
| 3.2 | 8.2 | |
| 6 days ago | about 1 month ago | |
| C# | C# | |
| MIT License | Apache License 2.0 |
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
porting-assistant-dotnet-client
-
Visual Studio .NET Upgrade Assistant extension released (devblogs.microsoft.com)
You could try this out too https://github.com/aws/porting-assistant-dotnet-client
What are some alternatives?
try-convert - Helping .NET developers port their projects to .NET Core!
Privatest - Adding instance-level accessibility mode to C#
MinimalApiPlayground - A place I'm trying out the new ASP.NET Core minimal APIs features.
aws-dotnetcore-examples - A collection of independent .NET5 projects written in C# that demonstrate how to integrate with various AWS services using the AWS SDK for .NET [Moved to: https://github.com/drminnaar/aws-dotnet-examples]
designs - This repo is used for reviewing new .NET designs.
BestPracticeAnalyzer - A .NET analyzer for developers complaining about people not following "best practices"
Giraffe - A native functional ASP.NET Core web framework for F# developers.
aws-dotnet-examples - A collection of independent .NET5 projects written in C# that demonstrate how to integrate with various AWS services using the AWS SDK for .NET
Vue3WebpackBoilerplateV2 - Advanced setup for Vue.js 3 project using webpack with many custom components
Meziantou.Analyzer - A Roslyn analyzer to enforce some good practices in C#.
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.