-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Description
Regression info:
Worked well on 17.14.13 Preview 1 + 10.0.100-preview.7.25380.108
Install STEPS
Win11 x64 24h2 ENU
VS Enterprise 2022 preview:17.14.13 Preview 1
RC1: 10.0.100-rc.1.25418.116 (runtime-10.0.100-rc.1.25418.116)
REPRO STEPS
Testing on Windows with VS -
1.Go to Tools -> options -> Debugging
Under General
a. Uncheck 'Enable Just My Code'
b. Check 'Suppress JIT optimization on module load (Managed only)'
Under Symbols
a. Check 'Microsoft Symbol Servers'
2.Create a new ASP.NET Razor project by doing
mkdir razor
cd razor
dotnet new razor
3.Open project in vs and add this line of code on Program.cs file
Console.WriteLine("x " + 3);
4.Place a breakpoint on that line (F9).

5.Run the application until it hit that breakpoint (F5). It will load symbols from the Microsoft symbol server, and may take a few seconds to hit the breakpoint. You should see 20-30 lines of ‘Loaded XXX Symbols loaded’.
6.Step into the concatination method (F11). it will step into ToString()

7.Step out of Concat (Shift F11).Then step into the WriteLine method(F11).This tests CoreCLR symbols AT THIS POINT IT SHOULD SHOW YOU THE SOURCE CODE FOR Concat().

8.Step out of Concat (Shift F11). Then step into the WriteLine method(F11). You may see the pop up as above, select the first option from it.
This tests CoreFX symbols AT THIS POINT IT SHOULD SHOW YOU THE SOURCE CODE FOR Console.WriteLine().
Expected Result:
CoreFX symbols (Console.WriteLine().) are displayed in step8.

Actual Result:
CoreFX symbols(Console.WriteLine()) are missing in step8.

Note:
Also happens on ASP.Net symbols
Put breakpoint on this line
F5 to continue debugging. The breakpoint you added above will get hit.
Now F11.You may see the pop up as above, select the first option from it.
This tests ASP.Net symbols.

But it displays as below ASP.Net symbols missing

- Work well on VS 18.0 preview1.0[10918.69.main] + 10.0.100-rc.1.25418.116 (runtime-10.0.100-rc.1.25418.116)