You are not logged in.
Just installed monodevelop-bin from AUR, created a new .NET console project and got the error "Could not restore packages". It cannot even build and run the default "Hello World!". The package console shows:
Getting restore information for project /home/ceidways/Projects/testing/testing/testing.csproj
/usr/share/dotnet/sdk/9.0.102/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.ImportWorkloads.props(14,38) : error MSB4236: The SDK 'Microsoft.NET.SDK.WorkloadAutoImportPropsLocator' specified could not be found.
Unable to create package spec for project. '/home/ceidways/Projects/testing/testing/testing.csproj'
I've followed the .NET setup page on the Arch wiki to the best of my ability, and have a dotnet dev environment and debugging working fine in vscodium.
Think I have everything dotnet-related installed:
pacman -Q | rg "dotnet"
dotnet-host 9.0.1.sdk102-1
dotnet-runtime 9.0.1.sdk102-1
dotnet-sdk 9.0.1.sdk102-1
dotnet-targeting-pack 9.0.1.sdk102-1
and I have dotnet tools in my path
echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/ceidways/.dotnet/tools
Offline
Mod note: moving to AUR Issues.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
DDG'ing for MSB4236: The SDK 'Microsoft.NET.SDK.WorkloadAutoImportPropsLocator' specified could not be found gives lots of results .
SO thread indicates you may have to set a MS specific env var, MSBuildSDKsPath , to solve it.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Online
Tried setting MSBuildSDKsPath to /usr/lib/mono/msbuild/Current/bin and /usr/share/dotnet/sdk/9.0.102/Sdks/ which didn't seem to do anything. Quite possibly the wrong location but I don't know where else.
The SO thread you posted might be a slightly different issue, unable to locate the sdk itself rather than the specific part of the sdk, it seems to locate the sdk just fine, because the error was from a file in the sdk that was already loaded, /usr/share/dotnet/sdk/9.0.102/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.ImportWorkloads.props, which seems to specify the file that it could not find.
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<!-- Import workload props -->
<Import Project="AutoImport.props" Sdk="Microsoft.NET.SDK.WorkloadAutoImportPropsLocator" />
</Project>
I found this SO thread with an essentially identical error message that suggested setting env variable MSBuildEnableWorkloadResolver=false, though this also had no effect.
Could monodevelop be setting its own env variables? Cant find any settings related to msbuild specifically, only .NET runtime set to Mono 6.12.0, and SDK Locations > .NET Core set correctly to 9.0.102 in /usr/share/dotnet/
Should Microsoft.NET.SDK.WorkloadAutoImportPropsLocator be an individual file somewhere? If so where?
Is there a different location that MSBuildSDKsPath should be set to?
Edit: also the ~/.dotnet/tools that the arch wiki suggests to add to path appears to not exist. I'm probably ignorant of something but is that normal?
Last edited by ceidways (2025-02-10 03:32:39)
Offline
I just realised a few things :
aur monodevelop-bin hasn't been updated in almost 2 years
MonoDevelop is no longer under active development, we recommend using Visual Studio Code with the C# DevKit extension as an alternative
Github source repo has been archived in 2021 .
Do you really need monodevelop ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Online
Not really, found it from googling "dotnet ide linux" I somehow didn't notice at first that it was stale, and when I did I was already knee deep in troubleshooting so I overlooked it.
Probably should have given up earlier, just downloaded jebrains rider which is working so far.
Thanks for your help though , and sorry for the mild time waste.
Edit: not sure whether to mark this post as [SOLVED] considering that the problem wasn't solved, the solution was just to give up and use a different software?
Last edited by ceidways (Yesterday 01:00:40)
Offline
[Gave Up] or [Abandoned] seems more relevant.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Online