Getting "You need to find some_random_file_here.cs to view the source for the current call stack frame" since my last update to VS2022 17.7.0

Question

Getting "You need to find some_random_file_here.cs to view the source for the current call stack frame" since my last update to VS2022 17.7.0

KakCAT CAT 21

Since I updated to VS2022, I'm continually getting the following message when before just an exception happened, or just stepping out of async functions, or stepping in functions I don't have the source to (before, the step in was just converted into a step through, which was far more convenient than current behavior)

"You need to find Task.cs to view the source for the current call stack frame"

How can I disable that?

Thanks in advance.

User's image

KakCAT CAT 21 Reputation points

2023-08-10T20:12:29.86+00:00

It seems to happen, at least, on a ASPNETCore projects, WPF project and WinUI3 project.
Viorel 121.3K Reputation points

2023-08-11T07:56:58.6033333+00:00

(Removed)

1 answer

Your answer

KakCAT CAT 21 Reputation points

2023-08-10T20:12:29.86+00:00

It seems to happen, at least, on a ASPNETCore projects, WPF project and WinUI3 project.
Viorel 121.3K Reputation points

2023-08-11T07:56:58.6033333+00:00

(Removed)

Answer 1

Tianyu Sun-MSFT 34,306 Microsoft External Staff

Hello @KakCAT CAT ,

Welcome to Microsoft Q&A forum.

In case some default VS settings were accidently changed during the updating process, please try to check following options or reset VS settings(run devenv /ResetSettings in VS developer command prompt):

1.Tools > Options > Debugging > General > Enable Just My Code.

2.Tools > Options > Debugging > General > Enable source server support.

Please also try to clean your solution/project cache about debugging and check again.

1.Close VS, delete the hidden .vs folder in solution folder, restart VS and rebuild the solution/project.

2.Debug > Delete All Breakpoints > reset breakpoints.

Sincerely,

Tianyu

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

KakCAT CAT 21 Reputation points

2023-08-14T08:24:27.9066667+00:00

Hi, thanks for the tips. Unfortunately none of them worked except resetting the environment, that right now I can't do (my setup is quite costumized and would take some time to get every back as it was)

For some reason, I think it's a problem with the new auto-decompilation feature, but I've disabled it as it says here ( https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes#auto-decompilation-for-external-net-code ) but I keep getting that message.
Tianyu Sun-MSFT 34,306 Reputation points Microsoft External Staff

2023-08-15T07:07:31.8266667+00:00

Hi @KakCAT CAT ,

Thanks for your reply.

I agree. After you disabled the auto-decompilation feature, did you try to remove the .vs folder and rebuild your project? Besides, is this option: Tools > Options > Debugging > General > Enable address-level debugging > Show disassembly if source is not available unchecked?
KakCAT CAT 21 Reputation points

2023-08-19T21:03:55.2333333+00:00

It seems that the combination of removing "Automatically decompile to source when needed" and then cleaning .vs did the trick, at least for the moment...
Tianyu Sun-MSFT 34,306 Reputation points Microsoft External Staff

2023-08-24T09:50:33.1966667+00:00

Hi @KakCAT CAT ,

The hidden .vs folder contains some debugging related cache, so after deleting it, when you open VS(this project), VS will generate a new .vs folder which contains the new debugging settings.

Did the same issue appear again after you unchecked the "Automatically decompile to source when needed" option and removed the hidden .vs folder?

Share via

Getting "You need to find some_random_file_here.cs to view the source for the current call stack frame" since my last update to VS2022 17.7.0

1 answer

Your answer