Nuget Package Manager VS Avalonia

- https://github.com/NuGet/Home/issues/8843

GitHub Issue

Similar issue here: https://github.com/dotnet/sdk/issues/28971. Following the breadcrumbs it looks like it may be a NuGet issue, reported here: https://github.com/NuGet/Home/issues/12227

Your issue appears to be related to not having the appropriate permissions to the Nuget folder (so says the error). There is an existing Bug/Ticket open on the Nuget github for this exact issue. There are a few solutions and/or workarounds listed through the conversation that you can try: https://github.com/NuGet/Home/issues/12162. Unfortunately I do not have a Mac to validate the solutions or the issue myself.

sounds like ur terminal has no internet connection here is a setup for configuring a proxy

The NuGet team is actively working on adding support for CPVM in .NET SDK 7.0.100/VS 17.4. There was a spec for the initial work that you can read at NuGet/Home, and they're looking to polish up and incorporate that work soon.

How do you currently feel about attaching the experience to install or when restoring packages? Various ecosystems do this and some get flak for it because of how many transitive dependencies and known vulnerabilities in comparison to others. I'm mostly curious because I'm working on a similar proposal here:

https://github.com/NuGet/Home/pull/11549

There's definitely a fine balance of noise, but how do you feel about it?

WPF is not the best example of open source, as some components are still closed source. Though it only runs on Windows, a closed source operating system, so perhaps that is not so important.

https://github.com/dotnet/wpf/issues/2554

That said, there are cross platform, open source .NET UI frameworks out there, including one that is inspired by WPF:

https://avaloniaui.net/

You might also want to look at AvaloniaUI[0] for a cross platform .NET GUI library. It is similar to WPF but much nicer to work with.

[0] https://github.com/AvaloniaUI/Avalonia

Production user here. There's no money gotchas. They're above reproach. In fact, I've received considerable free support from their devs on GitHub Issues [1].

The Avalonia business model is based on selling XPF, which runs WPF (Windows-only) apps on other platforms. That's very interesting to big corps with existing codebases.

See my comment [2]

[1] https://github.com/AvaloniaUI/Avalonia/issues

[2] https://news.ycombinator.com/item?id=39246988#39249128

Yes, but the portable GUI frameworks by Microsoft themselves are generally not very good, and they tend to be abandoned after a couple of years.

Avalonia is developed outside of the Microsoft corporate madness and seems to be slowly becoming the defacto cross-platform framework because it is expected to last a bit longer than a manager's attention span: https://avaloniaui.net/

Not my comment, but relevant here "The problem with compiling Skia to WASM is you'll lose any benefits of hardware graphics acceleration on the device."

(From https://github.com/AvaloniaUI/Avalonia/discussions/6831#disc... )

It's a bit of a hit and miss as of today. CLI, back-end and natively compiled libraries (think dll/so/dylib or even .lib/.a - you can statically link NAOT binaries into other "unmanaged" code) work best, GUI - requires more work.

Avalonia[0] and MAUI[1] have known working templates with it, but YMMV.

[0] https://github.com/lixinyang123/AvaloniaAOT / https://github.com/AvaloniaUI/Avalonia/ / honorable mention https://github.com/VincentH-Net/CSharpForMarkup

[1] https://github.com/dotnet/maui (try out with just true in csproj - it is known to work e.g. on iOS)