Closed omariom closed 5 years ago
Yep, we discovered this as part of an investigation into #1549. Long story short, we inject a module constructor into PresentationCore
via IL(D)Asm and had incorrect settings leading to the wrong parameters being used for the DebuggableAttribute
.
This was already fixed recently. Closing as a duplicate.
Is this bug related specifically to tooling in Visual Studio (e.g. XAML Designer, Code editing, etc...)? No
Problem description:
While looking at the jitted code of PresentationCore, found that the code was not optimized. Turned out the assembly has optimizations explicitly disabled.