No Breakpoints with Visual Studio 17.10.x for assemblies dependent on Avalonia #15999
Unanswered
LaurentInSeattle
asked this question in
Q&A
Replies: 2 comments 1 reply
-
And still same problem with VS 17.10.02 released earlier today (June 11th) |
Beta Was this translation helpful? Give feedback.
0 replies
-
Any comments or suggestions ??? This is a big issue here... |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
I am using Microsoft Visual Studio Community 2022 (64-bit) Version 17.10.1 for my current Avalonia mini-project, which is NOT using AOT, at least for now. It's using the official Avalonia nugets in version 11 along with .Net 8.
Since VS version 17.10.0 it is not possible to have breakpoints being hit in all assemblies that have a dependency on Avalonia.
Changing project settings to use compiled bindings or not does not change anything.
Same C# code compiled on a Mac with Jet Brains Rider (Free trial) works fine and all breakpoints get hit, Avalonia dependent or not.
On the PC+VS, adding the line Debugger.Break() ; causes the debugger to break, and then stepping and inspecting do work as expected.
Any idea ? or workaround ?
Thanks!
L.
Beta Was this translation helpful? Give feedback.
All reactions