-
Notifications
You must be signed in to change notification settings - Fork 14
Build failed with NET6 #39
Comments
Having the same problem. |
I had this issue too... seems that there is a change after installing VS2022. On my machine I noticed dotnet build was also not working, I uninstalled my dotnet (32 bit from program files (x86)). And then all worked again. I think a possible solution would be to force libsassbuilder.exe to run only as x86 or x64. But I don't have time to investigate further, and it seems my problem is solved by uninstalling the dotnet-sdk from x86 mode. |
"C:\Program Files (x86)\dotnet\dotnet.exe" --info X64 has an sdk, the x86 does not have an sdk registered on my machine after I uninstalled VS2019 and installed VS2022. |
This is actually where the problem originates... for some it cannot find dotnet.exe, or no registered runtime. |
If you want this fix now before Johan can release a new version, you might want to look at the changes I made in the files. It is easy to do on your own machine to get going again:
%APPDATA%.nuget\packages\libsassbuilder\1.6.4\build\LibSassBuilder.props
See: https://github.com/johan-v-r/LibSassBuilder/pull/41/files |
thanks for the info. I don't think that temporary fix is workable in a dockerized CI environment though |
@adamhathcock I know it does not work for all situations. But for me at least it enabled me to continue working locally. And in a linux environment the whole x86/x64 issue might not be a factor. |
The exact error I get is:
if you had to rename the file from |
Maybe it's as simple as having to multi-target the exe for .net6? I guess I thought it would just work on the new runtime. Not sure why it wants net5 specifically |
The problem starts with half of the people having this issue that they have a x86 version of dotnet.exe without an x86 sdk or runtime, this is counter intuitive and a strange requirement. Other half of the problem could be solved with having the .dll run in both x86 and x64 environments. But before even getting to that point dotnet.exe already fails to start. |
Hi All - there's a new release v2.0.0 that targets .NET 6 |
Appears to work for me. Thanks for the quick update! |
It newly build on our CI with .NET 6! Thanks |
I finally came to upgrading my project, at my end this still fails:
On my machine I have both the 6.0 x86 and x64 installed now... however my dotnet.exe that is on my PATH first is the x86 version, not the x64. So it still fails when calling dotnet.exe like this. |
I know this issue is closed, but on my end this still depends on the order in the PATH of dotnet.exe. |
Hi @JelleHissink - I left a comment on that PR asking if that works for Linux as well? I think we might need to add the LibSassHost.Native.win-x86 dependency. Apologies I wasn't aware this was still an issue, will reopen. |
New version |
Good morning,
we migrated our Blazor WASM project to .NET 6 and now we are not able to compile anymore.
It seems that this library asks to use .NET 5 SDK instead of .NET 6 one.
Thanks
The text was updated successfully, but these errors were encountered: