Persistent error with dotnet cli and installing maui workspace
I've tried time and again now without joy. There is precious little info on this issue out there (on Google), all I could really find were some open issues on Github.
Everyone tell me to install the workspace using
dotnet workload install maui, but even with variants specifying a NuGet source, I still end up with a list of errors about not being able to update or read the advertising manifest for microsoft.*
I have only just not uninstalled. NET 8 because I've seen articles from MS people saying maui is ready for. NET 8.15 Replies
do u not have visual studio community?
@Ubuntu Victim
well then open your visual studio installer
and install it from there
and you be done
that is all u have to do
nothing else
Sorry, I don't, only vscode
well then im out sorry 😛 I dont use vscode for c# waste of time imo
I was trying to avoid installing VS just for this
I am not sure u have a path in the cli for that
I use Rider but their docs also say to use the cli
you're on windows?
I'll check paths, thanks
I'm actually on Linux and Windows but I have only tried Windows so far
well the suggestion on the ms page was
but u said u already tried it
did u install the SDK?
like when u type dotnet --version what u get
if feels like u might have installed the runtime instead
I did try that, yes.
dotnet --version gives me 8.2.201, suggesting I do have the SDK installed.
I'm trying to install the SDK again now, just in case something is wrong thereaside from that that command should work, not sure it would work on linux thou given maui does not support linux, even thou its for development
and I would guess u might not be able to run the emulators maui requires from inside a vm
or that it might require extra steps
I haven't tried Linux yet, and I'm not using a vm. I just tried again after installing sdk 8.0.201, and I'm still getting the same list of errors. If it helps any, here is a sample:
Oh man, I'm using a very, very tight 'firewall' called PortMaster. It defaults to block non-local network connections for all process except ones it knows, and it only knows VS, not the cli. Now I'm just grumpy because the cli workload install requires a
--skip-sign-check flag to skip validating the nuget signatureswait u shouldn't need to skip it
but u can add dotnet cli to the rules no?
Yeah, it's an amazing app, I can add the cli app, add a profile for all dotnet apps and Ides, the connection type, and the IP and port.
It took me about 3 weeks to get my dev machine working smoothly again after installing it, but all that is saved in profiles I will be sharing publicly.
But I digress. Thank you for all your help. :plus_one: 👍🏻
no worries didnt really do anything just another day of talking
do a /close if its resolved thou 🙂