try-convert VS UWP Community Toolkit

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.

GitHub/WCT/Controls/DataGrid (source code for the control)

Started programming by writing some apps for Windows Phone later UWP during university. A few years ago I started collaborating a lot on GitHub to some Microsoft projects, like the Windows Community Toolkit. There I created a lot of new APIs and libraries, like all the new animation APIs and pipeline brush APIs, etc. I then also proposed adding some general .NET APIs to it, and that's how the MVVM Toolkit was born, along with other libraries which are now moved to the .NET Community Toolkit. Fast forward until about late 2020, and they pinged me saying the new Microsoft Store (which hadn't been announced yet back then) was using several of those new APIs I had written, so we started collaborating more so that I could add more functionality they needed. After that shipped, at some point there was a new opening to which I applied, and here I am in the Microsoft Store team and also leading the .NET Community Toolkit 🙂

https://github.com/CommunityToolkit/WindowsCommunityToolkit (now multiplateform)

For instance, recently Chaochao opened a PR for the Windows Community Toolkit to open source the whole custom animation helpers he developed for the Store, which are used to implement the morphing animations you see when scrolling in a product page. You can see a GIF and the whole code here and in the linked PR.

Specifically I am looking for AsyncRelayCommand.cs. All documentation points to CommunityToolkit repo but I can not find it there. Link to source repo from the Nuget package also points to CommunityToolkit. I am not looking for samples.

The report itself is just markdown that is rendered with the Community Toolkit's MarkdownTextBlock.

That's interesting. It will need some documentation and to finish the renaming at some point, e.g. Span2D is in https://github.com/CommunityToolkit/WindowsCommunityToolkit but as you say doesn't require Windows.

Windows Community Toolkit