- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
I recall this issue from way back, haven't encountered in a while
However
i finally moved to win 11 (all worked fine on win10)
on win11 machine when recompiling after walking through code and exiting
the debugger i am guessing does NOT properly release the exe
i have a few silly workarounds of exiting, logging out, or standing on head
However
There must be an easier resolution?
surprised search didn't bring this up since it was BIG many years ago
thanks in advance for any hints
brian
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
soooo....
Update: Visual Studio had a major update Version 17.14.9 (July 2025)
I just installed and it now seems to release all files so can walk thru debug and then recompile
링크가 복사됨
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
adding running latest IFORT on Visual Studio 2022
for some reason it locks down the debug exe so can't rebuild
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
In task manager is the exe still active? Use a application like "lockhunter" if necessary set a prebuild task to unlock the exe.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
will check out lockhunter. but no, the exe is not still active.
But
the project has 3 DLLs and expecting one of them win11 isn't releasing
or
MSVS 2022 isn't releasing since doesn't occur on win10/msvs 2019.
thanks for the tip will keep digging
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
soooo....
Update: Visual Studio had a major update Version 17.14.9 (July 2025)
I just installed and it now seems to release all files so can walk thru debug and then recompile
