upgrade-assistant
MinimalApiPlayground
upgrade-assistant | MinimalApiPlayground | |
---|---|---|
14 | 4 | |
1,074 | 644 | |
0.9% | - | |
3.2 | 0.0 | |
6 days ago | over 1 year 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
MinimalApiPlayground
-
C#10 e ASP.NET 6, oque esperar dessa dupla?
Github com exemplo de uso: DamianEdwards/MinimalApiPlayground
- ASP.NET Core 6: Minimal APIs y Carter
-
Maybe it's time to rethink our project structure with .NET 6
I think there are some example here, https://github.com/DamianEdwards/MinimalApiPlayground/tree/main/src/MinimalApiPlayground and https://gist.github.com/davidfowl/ff1addd02d239d2d26f4648a06158727
- Minimal APIs at a glance in .NET 6
What are some alternatives?
try-convert - Helping .NET developers port their projects to .NET Core!
Carter - Carter is framework that is a thin layer of extension methods and functionality over ASP.NET Core allowing code to be more explicit and most importantly more enjoyable.
designs - This repo is used for reviewing new .NET designs.
MiniValidation - A minimalist validation library for .NET built atop the existing features in `System.ComponentModel.DataAnnotations` namespace
Giraffe - A native functional ASP.NET Core web framework for F# developers.
haxe - Haxe - The Cross-Platform Toolkit
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.
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
BedrockFramework - High performance, low level networking APIs for building custom servers and clients.