winetricks VS awesome-avalonia

Step 1: Install Whisky + Winetricks with Homebrew.

See https://github.com/Winetricks/winetricks/issues/1863 for some suggestions. The normal way to fix your situation, taking into account the previous posts, would be to just back up the saves, nuke the prefix, and start from scratch.

Support for the commonly-used tool Winetricks

When it comes to wine everything is the same except the steam part. When it comes to that you need to install winetricks package. The link is here https://github.com/Winetricks/winetricks.

Sounds like it could be a missing module problem, maybe try https://github.com/Winetricks/winetricks.

Sounds like it's time to get familiar with the wine-staging options to hide wine-specific exports:

https://github.com/Winetricks/winetricks/blob/b46dd63e024a16...

i changed to lutris. Game runs well there too. Finally i got Winetricks working there but its meh. Mangohud shows only wine version 5. and i get this error when i try to install vcredist19. (i get spammed with errors) https://github.com/Winetricks/winetricks/issues/1770

If you want to automate the process you have to set it up yourself, as described on their github: https://github.com/Winetricks/winetricks

Wine is a very cool project dedicated to getting Windows apps running on other systems. You'd really want Wine and Winetricks which handles a lot of setup for games for you.

WPF and Xamarin dev here who wrote a new (not ported) codebase on Avalonia.

- Avalonia has a guide just for people like you and me [1].

- Avalonia's flavor of XAML has small divergences from WPF that will have you hitting their docs often. There are some nice quality-of-life improvements, for example you can bind a Button click handler directly to a method without ICommand. The major concepts are the same e.g. data binding, dependency properties.

- Coming from WPF, it's possible you've used MVVM and dependency injection. You'd be going against a strong cultural grain to not use them in Avalonia. But I would be surprised if your WinForms app is architected remotely similarly, so it may be a design challenge extracting coherent ViewModels and properties from the ball of mud that many WinForms apps become.

- For macOS, read up on notarization [2] and, if you're publishing to the Mac App Store, the review process.

- I recommend starting with example apps (look in the Showcase) or with the Avalonia template solution which just runs out of the box.

- The Avalonia team iterates quickly. Expect to upgrade NuGets frequently, and don't get too far behind. There was recently a big jump from version 10 to 11. Good for you for starting after that.

- Not Avalonia specifically but if you're not used to .NET Core check out #nullable enable. Can't live without it now, but was confusing at first.

- Be sure to check out all of the official and community libraries [3]. I bet my design big on `ReactiveUI` and it's gone well.

[1] https://docs.avaloniaui.net/docs/get-started/wpf/

[2] https://docs.avaloniaui.net/docs/deployment/macOS

[3] https://github.com/AvaloniaCommunity/awesome-avalonia

I hear you. We’ve a decent datagrid and a load of OSS components that you can find here.

You can see a lot here and, for example, here

You can find more 3rd party controls here for example : https://github.com/AvaloniaCommunity/awesome-avalonia

More about Avalonia production apps here.

You could use Avalonia. This is xaml crossplatform and will be better supported than wpf. You can get the templates for dotnet new Avalonia. It's xaml, fast templates and there is a designer op github, can't fidn it atm. Some examples