Closed cdibbs closed 2 years ago
This part is particularly interesting:
No SDKs were found.
I've never seen that before, and it doesn't even really make sense to me from a dotnet --info
call - I'm not sure how anything to do with the environment would hide the SDKs.
Is it possible you've encountered this problem or something like it?: https://github.com/dotnet/installer/issues/12616
@daveaglick Yep, and the first comment about deleting the x86 folder solved it for me. In hindsight, I suppose the big clue was in the output I pasted above. Notice that the first list of runtimes points to the Program Files (x86)
folder while the second points to the regular Program Files
folder. So, it seems like the tool gets tripped up when dotnet.exe is installed for more than one architecture.
Cool - glad it's resolved for you. This looks like an upstream bug with dotnet
itself, which makes sense given that Buildalyzer just shells out to that (and relies on what it outputs to figure things out). Since this is an exceptional situation, unless you think there's something we can do on this end, I'm going to close it as out of scope for Buildalyzer.
Context:
This code used to work prior to recent VS and framework updates (I don't remember the specifics of the updates which were recommended by VS 2022). It walks through .csprojs and builds them with the following options:
The error appears to be due to incomplete information in
dotnet --info
when run from within ProcessRunner:Running from within Powershell produces more complete output:
Any help would be appreciated. Thanks!