Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes = #4
Technical Reasons for Avalonia Instead of MAUI
MAUI requires the Microsoft.NET.Sdk.Maui workload to be installed
Your dev container didn't have this workload available
Installing workloads in dev containers can be problematic
Avalonia works with the standard Microsoft.NET.Sdk - no special workload needed
2. Build Environment Compatibility
MAUI SDK resolution failed with: "The SDK 'Microsoft.NET.Sdk.Maui' specified could not be found"
Avalonia packages are available directly from NuGet without SDK requirements
This makes Avalonia more portable across different CI/CD environments
3. Cross-Platform Support (Your Requirements)
✅ Avalonia works equally well on Windows and Linux (tested, proven)
MAUI on Linux requires additional setup and has fewer platform optimizations
Your original app was Linux-based (GtkSharp), so Avalonia is a natural fit
4. Dependencies
Avalonia: Clean NuGet packages only
MAUI: Requires workload installation + platform-specific tooling
Why This Was Better For Your Case
Since you specified:
✅ Extract colors.xml on first run → Both support this equally
✅ ApplicationData folder → Both support this
✅ CommunityToolkit.Mvvm → Both support this
✅ Native color picker → Both support this
❌ Works on Windows & Linux → Avalonia is simpler here (no extra setup)
If You Want to Switch Back to MAUI
If you prefer MAUI, you would need to:
Install the MAUI workload:
Update .csproj to use Microsoft.NET.Sdk.Maui SDK
Convert Avalonia XAML → MAUI XAML (similar but slightly different)