The real news here is that this is considered special. In most other languages, they'd have forked the source, fixed it, recompiled it for their own uses and submitted a pull request or patch. I'm a big .NET fan, but the fact that we have to jump through such hoops to find and fix a bug, and then still have near certainty that we're going to have to reapply the patch for many updates to come, well, that's just a bit…
---Author here--- I should disclose that I actually work for Microsoft, and still chose the hard way. Fuck the police!
I found a bug in the .NET framework and fixed it by hand-altering the DLL
21–30 of 124 posts
Re: I found a bug in the .NET framework and fixed it by hand-altering the DLL
#22The real news here is that this is considered special. In most other languages, they'd have forked the source, fixed it, recompiled it for their own uses and submitted a pull request or patch. I'm a big .NET fan, but the fact that we have to jump through such hoops to find and fix a bug, and then still have near certainty that we're going to have to reapply the patch for many updates to come, well, that's just a bit…
Re: I found a bug in the .NET framework and fixed it by hand-altering the DLL
#23Re: I found a bug in the .NET framework and fixed it by hand-altering the DLL
#24Should have just used dotPeek instead of ilspy and writing IL code by hand. Recompiling would have certainly been easier. http://www.jetbrains.com/decompiler/
AWESOME TIP, stoked to try it out, thanks!
Re: I found a bug in the .NET framework and fixed it by hand-altering the DLL
#25The real news here is that this is considered special. In most other languages, they'd have forked the source, fixed it, recompiled it for their own uses and submitted a pull request or patch. I'm a big .NET fan, but the fact that we have to jump through such hoops to find and fix a bug, and then still have near certainty that we're going to have to reapply the patch for many updates to come, well, that's just a bit…
Normally if you find a bug in the core you might try to monkeypatch but many times that won't work so you have to suck it up and just work around it.
Re: I found a bug in the .NET framework and fixed it by hand-altering the DLL
#26I did this once with GCC. "But GCC's open source!" you say. Well, GCC is next-to-impossible to compile for a target other than the host, especially if the target isn't x86 or ARM; and GCC maintainers insist on precise test cases to vet a bug, even if the issue is immediately obvious from reading the source code and the bug only occurs in certain very complex situations. (/me looks forward to the day Clang/LLVM become…
Re: I found a bug in the .NET framework and fixed it by hand-altering the DLL
#27Earlier quoted context omitted.
---Author here--- I should disclose that I actually work for Microsoft, and still chose the hard way. Fuck the police!
Out of curiosity, would you have been able to read the actual source if you wanted?
Re: I found a bug in the .NET framework and fixed it by hand-altering the DLL
#28The real news here is that this is considered special. In most other languages, they'd have forked the source, fixed it, recompiled it for their own uses and submitted a pull request or patch. I'm a big .NET fan, but the fact that we have to jump through such hoops to find and fix a bug, and then still have near certainty that we're going to have to reapply the patch for many updates to come, well, that's just a bit…
What they're doing here is monkeypatching the language runtime. That's not trivial in most languages, least of all ones which typically rely on a centralized install of that language runtime to function. The way they did this, only the program that needs this fix is actually using their monkeypatched Expressions library; other code on the same system - other libraries in the same application, even - will continue to…
monkey patching refers to dynamic modifications of code/behaviour at runtime.
this is simply editing a file on the disk, which people cracking software have been doing for about 30 years (using exactly the same method).
Re: I found a bug in the .NET framework and fixed it by hand-altering the DLL
#29Earlier quoted context omitted.
> and still chose the hard way Chose? Unless you work on the team that made that DLL, it's likely you'd be jumping through hoops even internally.
i'm glad someone who works at the company like you was able to enlighten us as to microsoft's internal practices oh wait
Re: I found a bug in the .NET framework and fixed it by hand-altering the DLL
#30The real news here is that this is considered special. In most other languages, they'd have forked the source, fixed it, recompiled it for their own uses and submitted a pull request or patch. I'm a big .NET fan, but the fact that we have to jump through such hoops to find and fix a bug, and then still have near certainty that we're going to have to reapply the patch for many updates to come, well, that's just a bit…
---Author here--- I should disclose that I actually work for Microsoft, and still chose the hard way. Fuck the police!