Blog Home  Home Feed your aggregator (RSS 2.0)  
Microsoft bug fixing policies - Manuel Abadia's ASP.NET stuff
# Wednesday, June 13, 2007

Something that is really annoying is the list of little bugs or problems that pollute the .NET Framework and doesn’t seem to get fixed (mostly because of remotely backward compatibility reasons). Others problems are simple solved as “won’t fix“, without giving any explanation.

For example, take a look at this one:

If you use a TreeView, invalid XHTML gets generated because a script tag is added without specifying the type. They only need to add type="text/javascript" to the generated script. It is clearly a bug and it won’t break anything. However, it is marked as “won’t fix”. WTF?

Sometimes one can be lucky and they actually fix the bug (or at least they told you that they will fix it) but this seems to be the exception rather than the rule. For example, I submitted this bug some time ago and it seems it will be fixed:

However, the list of unresolved issues that clearly need to be fixed is big and growing, but a lot of them aren't addressed. IMHO this should change. I prefer to have a remote possibility of having something that works to stop working because of bug fixes than keep going with thousand of bugs and work arounds for not solving them. Also, I'd like to have updates more often. To wait a year for a service pack for the framework is too much.

Wednesday, June 13, 2007 4:09:57 PM (Romance Daylight Time, UTC+02:00)  #    Comments [0]   ASP.NET | Microsoft .NET Framework  | 
All comments require the approval of the site owner before being displayed.
Home page

Comment (Some html is allowed: a@href@title, strike) where the @ means "attribute." For example, you can use <a href="" title=""> or <blockquote cite="Scott">.  

[Captcha]Enter the code shown (prevents robots):

Live Comment Preview
Copyright © 2020 Manuel Abadia. All rights reserved.
DasBlog 'Portal' theme by Johnny Hughes.