Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I found a bug in the .NET framework and fixed it by hand-altering the DLL

blog.nullspace.io

Post reply on HN
Print view View original

91–100 of 124 posts

Re: I found a bug in the .NET framework and fixed it by hand-altering the DLL

#91

Post by Pxtl »

allegory wrote: post #70
stusmith1977 wrote: post #33

In situations like this, you can report the bug to Microsoft Connect: 1. Submit bug report. 2. Wait six months. 3. MS tech will post a comment, "this will be fixed in the next release". 4. Wait two more years. 5. Bug report will be closed as "won't fix".

This. One bug in IE9 clickOnce launching thanks to them changing how download prompting works. 1. Reported to connect whilst in preview release status. Closed. Reported again. Closed. FULL test cases provided. 2. We're a gold partner with a £500k spend a year on licenses. Partner support. 19 hours on the phone over 6 months, blame shifting between the IE and .net teams and a daily call to get the case closed without…

Yup. Its funny as a dot net dev you learn to really love a few ms things and really hate the others. C# is a brilliant language. Entity framework is an awesome ORM. But anything to do with deployment? IIS? So very much rage. I'm in charge of the build process on my team and I'm quickly becoming "that guy in the corner who swears all the time".

Re: I found a bug in the .NET framework and fixed it by hand-altering the DLL

#92

Post by seanmcdirmid »

sjf wrote: post #34
wwwwwwwwww wrote: post #18

Earlier quoted context omitted.

i'm glad someone who works at the company like you was able to enlighten us as to microsoft's internal practices oh wait

Apply some common sense, you think they let MS employees just commit to any codebase they like? And this is leaving aside all the annoying steps of locating their repository, figuring out how to build it, testing, finding out the right person to send the patch to, going through code review.

Actually...I heard Google has developed a lot of infrastructure to allow for this: one repository, you can submit changes that are then automatically routed for review and test and such.

Re: I found a bug in the .NET framework and fixed it by hand-altering the DLL

#93

Post by seanmcdirmid »

Alupis wrote: post #15
diminish wrote: post #12

Earlier quoted context omitted.

Aren't you allowed to send a git (err tfs) pull request there at least within the company?

I've read several places that even Microsoft is not standardized on a source control management, some use tfs, some svn, some git, etc.

I know of some teams even still using visual source safe for legacy reasons.

Re: I found a bug in the .NET framework and fixed it by hand-altering the DLL

#95

Post by antics »

xpaulbettsx wrote: post #78
antics wrote: post #9

Earlier quoted context omitted.

---Author here--- I should disclose that I actually work for Microsoft, and still chose the hard way. Fuck the police!

You chose the really hard way, the reference source is public - http://referencesource.microsoft.com :P

---Author here---

It wasn't that hard. It took us about 30 minutes (thanks largely to the fact that Bart is a genius.) Besides, that's not actually the source of this DLL. We are on .NET native, and for that matter, a bleeding-edge build that's only available here at MS.

Re: I found a bug in the .NET framework and fixed it by hand-altering the DLL

#96

Post by InclinedPlane »

stusmith1977 wrote: post #33

In situations like this, you can report the bug to Microsoft Connect: 1. Submit bug report. 2. Wait six months. 3. MS tech will post a comment, "this will be fixed in the next release". 4. Wait two more years. 5. Bug report will be closed as "won't fix".

Hah. I filed a bug via MS Connect years ago and it was eventually fixed in release. It may take time, but it sometimes works.

Re: I found a bug in the .NET framework and fixed it by hand-altering the DLL

#98

Post by locusm »

Pxtl wrote: post #91
allegory wrote: post #70

Earlier quoted context omitted.

This. One bug in IE9 clickOnce launching thanks to them changing how download prompting works. 1. Reported to connect whilst in preview release status. Closed. Reported again. Closed. FULL test cases provided. 2. We're a gold partner with a £500k spend a year on licenses. Partner support. 19 hours on the phone over 6 months, blame shifting between the IE and .net teams and a daily call to get the case closed without…

Yup. Its funny as a dot net dev you learn to really love a few ms things and really hate the others. C# is a brilliant language. Entity framework is an awesome ORM. But anything to do with deployment? IIS? So very much rage. I'm in charge of the build process on my team and I'm quickly becoming "that guy in the corner who swears all the time".

Your still not cursing as much as the guy building msi installers though...

Re: I found a bug in the .NET framework and fixed it by hand-altering the DLL

#99

Post by overgard »

rubyrescue wrote: post #2

My knowledge of the GAC is out of date but isn't a bit of a security hole that you can replace that DLL?

I don't think it's a replacement, since signing the new DLL would require a new key. (GAC DLL identity basically comes down to name + signing key. So even if you call it System.Whatever, it has a unique identity)

Re: I found a bug in the .NET framework and fixed it by hand-altering the DLL

#100

Post by wffurr »

Permit wrote: post #63

I know a lot of people here balk at the idea of paying for tooling, but Red Gate's Reflector[1] is absolutely amazing for situations like this. Not only is it a decompiler, but it allows you to decompile at debug-time and step into third party libraries. Assuming they haven't been obfuscated, this is an extremely useful tool. I've used it to track down a number of issues within Visual Studio itself and within some of…

You are justifying closed-source tools by using a closed-source tool to debug your closed-source tools?
Post reply on HN