try-convert VS Net8CoreApiBoilerplate

dotnet upgrade assistant or dotnet try-convert can help with that.

- dotnet try-convert: https://github.com/dotnet/try-convert

try-convert

Check out https://github.com/dotnet/try-convert

https://github.com/dotnet/try-convert (usually) makes this a breeze.

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).

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.

migrate to SDK-style project files - try-convert does wonders here

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!)

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.

Since the legacy project is still in use, I had to be careful not to break anything while improving it. For example, I had to keep up with inserting data into a Logging table from both the old and new systems. I had to implement a hack using constant sequence resets to achieve this goal, which you can see in this file: https://github.com/Uraharadono/Net7CoreApiBoilerplate/blob/master/Net7CoreApiBoilerplate.DbContext/Interceptors/LoggingInterceptor.cs

I used this approach when I was upgrading my legacy project. The good thing was that I fought and won to centralise user management through all of our systems. Here is a link to boilerplate repo if you want to skim through code: https://github.com/Uraharadono/Net7CoreApiBoilerplate

The starter project is full of custom components that I came up with, including Tabs, Toggle, Xhr File Upload, AutoComplete, and my own custom data grid system called "Sephiroth grid." These components work exceptionally well with .Net, and I even have another repository (https://github.com/Uraharadono/Net7CoreApiBoilerplate) that you can use to quickly set up a working development environment.