You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tested this on bare metal install of windows and also clean install of windows in a VM, in both cases it detects all .NET versions up to 4.8 then sits there until I abort, the longest case just over 6 hours, whilst sitting there I see no i/o or cpu activity from the process.
Seems hitting enter causes it to exit as well, so is it finishing but just not auto exiting? The bare metal also has newer versions of .NET which dont show, hence me waiting.
Seems by design this is only for older versions of .NET so i guess its just about the exit behaviour.
The text was updated successfully, but these errors were encountered:
chrcoluk
changed the title
Sites for hours until I abort after finding 4.8 version.
Sits for hours until I abort after finding 4.8 version.
May 31, 2023
chrcoluk
changed the title
Sits for hours until I abort after finding 4.8 version.
Doesnt automatically exit.
May 31, 2023
¿Have you read the README file at the main page of this repo? This is the first thing you should do...
This program by default stops after finding the last version of .NET so that you can just double click on it to run it without having a lightning-fast command line opened and closed. If you add the -b, /b or --b switch, that it doesn't stop. That switch is there if you want to use it in a batch file.
Tested this on bare metal install of windows and also clean install of windows in a VM, in both cases it detects all .NET versions up to 4.8 then sits there until I abort, the longest case just over 6 hours, whilst sitting there I see no i/o or cpu activity from the process.
Seems hitting enter causes it to exit as well, so is it finishing but just not auto exiting? The bare metal also has newer versions of .NET which dont show, hence me waiting.
Seems by design this is only for older versions of .NET so i guess its just about the exit behaviour.
#3 (comment)
The text was updated successfully, but these errors were encountered: