.Net serves different HTML depending on the browser

The .Net framework has the capability to evaluate the user agent and, accordingly, render the web page for that specific browser version.

The problem here is that .Net, following the Microsoft long "I know best" record history, thinks it knows better than developers what the developers what to do. The outcome: the application may actually not work, at least as expected, on some browsers.

I got this yesterday, as I had to maintin compatibility with Internet Explorer 6 in a .Net 4 application and, some how, Internet Explorer 6 wasn't working. What is even wierd is that the same application on .Net 1.1, the maintenance branch, was working fine! Plus, against .Net official documentation, Internet Explorer 6 should work because it is set as the default minimum, but in reallity it didn't!

After some research, I've came across with the solution. Using the ClientTarget property from the Page class, I've just foced to assume everyone is using, at least, Internet Explorer 6.

./M6

The 7 Deadly Sins of Startups

A small "guide of mistake" for startups. Interesting and worth reading: The 7 Deadly Sins of Startups.

./M6

The best interface is no interface

I've came across a great post about user interfaces and how they help us or, at least, not get on our way.

A must read for all UX, designers, developers and everyone with a special interest in interfaces: The best interface is no interface.

./M6

Meld on Mac OS X

Meld is great. It's, currently, the best graphical comparison tool open source (and even freeware) has to offer.

To run in on Mac OS X using Mac Ports, you should really follow this small tutorial: Running Meld on  OSX 10.7 Lion.

./M6