upgrade-assistant
try-convert
| upgrade-assistant | try-convert | |
|---|---|---|
| 14 | 13 | |
| 1,074 | 1,138 | |
| 0.9% | 0.2% | |
| 3.2 | 0.0 | |
| 6 days ago | 3 months ago | |
| C# | C# | |
| MIT License | MIT License |
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
try-convert
-
Understanding the .NET ecosystem: The evolution of .NET into .NET 7
dotnet upgrade assistant or dotnet try-convert can help with that.
- dotnet try-convert: https://github.com/dotnet/try-convert
-
converting framework4.8 webapps to NetCore (Net5,6,7). any apps available to help?
try-convert
- Winforms .Net Framework 4.6 Application to .Net 6
-
What shall I upgrade .Net Framework 4.5.2 to for my WinForm project?
Check out https://github.com/dotnet/try-convert
-
I'm used to .NET Framework. Should I try to learn .NET Core?
https://github.com/dotnet/try-convert (usually) makes this a breeze.
-
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).
-
.NET MAUI: Leveraging UIs Across Devices
That would mean you have pretty simple code then, relatively speaking. I helped write the underlying project conversion tool used in the Migration Assistant and found that there's a lot of big and incompatible differences well before you even get into which APIs you're using. Lots of enterprise apps end up using them, whether or not the authors of those apps are aware of it.
-
Advice: Modernizing Old Application Architectures
migrate to SDK-style project files - try-convert does wonders here
-
Help with trying to get a .NetFramework project running in VS2022
Are you using .NET SDK-style projects, or the old scary ones? The latter should load, but since you can't even create them anymore I would expect them to bit rot over time. The try-convert tool should be able to help with that (I wrote most of it, plus the F# support!)
-
Date, Time, and Time Zone Enhancements in .NET 6
there's https://github.com/dotnet/try-convert. Haven't tried it; I instead use https://github.com/hvanbakel/CsprojToVs2017, but I assume the former might be a better choice by now.
What are some alternatives?
MinimalApiPlayground - A place I'm trying out the new ASP.NET Core minimal APIs features.
NsDepCop - NsDepCop is a static code analysis tool that helps to enforce namespace dependency rules in C# projects. No more unplanned or unnoticed dependencies in your system.
designs - This repo is used for reviewing new .NET designs.
CsprojToVs2017 - Tooling for converting pre 2017 project to the new Visual Studio 2017 format.
Giraffe - A native functional ASP.NET Core web framework for F# developers.
mpv.net - 🎞 mpv.net is a media player for Windows with a modern GUI.
Vue3WebpackBoilerplateV2 - Advanced setup for Vue.js 3 project using webpack with many custom components
ReactiveUI - An advanced, composable, functional reactive model-view-viewmodel framework for all .NET platforms that is inspired by functional reactive programming. ReactiveUI allows you to abstract mutable state away from your user interfaces, express the idea around a feature in one readable place and improve the testability of your application.
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.
ClojureDart - Clojure dialect for Flutter and Dart
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
UWP Community Toolkit - The Windows Community Toolkit is a collection of helpers, extensions, and custom controls. It simplifies and demonstrates common developer tasks building .NET apps with UWP and the Windows App SDK / WinUI 3 for Windows 10 and Windows 11. The toolkit is part of the .NET Foundation.