-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fix DebuggableAttribute in InjectModuleInitializer post-build targets #1744
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Curious why this needs to be specified and it isn't just persisted from the source. Is that a bug in ILAsm or ILDasm? Have we filed that issue? |
I'll have to check with later versions of .NET IL(D)Asm/ILAsm. We're pegged to .NET 4.6.2 due to an issue with the MSBuild tool locator, but also due to this bug with round-tripping in .NET 4.8. We only just found out about these in the last couple of days, but we'll be sure to file the appropriate issues on both teams. |
In the disassembled IL, this attribute is commented out and it indicates this will be added automatically. When I did a recombination of |
I see, makes sense. |
Approved by tactics, merging. |
Addresses #1549
In the
ReconstituteDll
target, we call ILAsm to merge a module constructor into the assembly we previously disassembled. We need to enable JIT optimizations here so that we get an appropriateDebuggableAttribute
on the assembly and don't cause perf problems.@vatsan-madhavan who helped debug and find this fix.