At work, we have a program written sometime in mid-2000's (.NET Framework 2.0). It's used to calculate the mileage our field guys drive, for reimbursement purposes. It was last updated in 2012.
It broke in December. They just told me this last week.
Turns out it's using mapquest API, which changed...you guessed it...in December. The mapquest api calls are hardcoded into the program (rather than using config files) so I have to recompile the whole thing from scratch.
The code is compiled binaries, we don't have access to the source, and we don't have a working relationship with the company that wrote it. I'm expected to fix it.
dotPeek decompiler to the rescue! Look at all that pretty source code.
Oh look, you tried to make things complicated by divorcing some code from the main dll, and hiding them in the GAC? That's fine. I can find those and decompile them too.
Blah--.Net 2.0 bugs/idiosyncrasies converting to 4.0, and the 2.0 web.config is a nightmare. That's ok. I've worked in both. I know what program references to add, and what I can cut out of the config file.
Oh wait, you have strongly typed data classes, but no XSD files for me to compile from? No problem...I'll switch them all to generic data classes. You're not even using the strongly typed objects properly anyway, which would have made my job so much harder. Oh look, I found some bugs you left in the program. Those parts that
never worked? They're working now.
Screw you, computer. I am your God, and you will do as I command.
Not bad for 8 hours of work.