Blog Home  Home Feed your aggregator (RSS 2.0)  
PHP vs ASP.NET and Atlas Control Toolkit - Manuel Abadia's ASP.NET stuff
 
# Sunday, April 30, 2006

I have finished a project that started as an enhancement of a “nearly finished” PHP web site. When somebody tells me that they have something “nearly finished” the first thing that comes to my mind is that what they haven’t been able to finish it. It’s very easy to start adding functionality to a web site but the difficult thing to do is to finish it, so everything fits in properly with a decent design. Unfortunately I was right. There was a lot of work to do and most of the things that were done need to be rebuilt.

It was my first contact with PHP. It was straightforward to do anything in PHP as I had done some things years before in Perl, ASP and JSP. After a day working with PHP I had the feeling that I was just loosing time, something like programming an ERP in assembler. It’s a lot of work that could be done easier and with more confidence that the code works as expected in another development environment.

As I really hate loosing time I proposed to use ASP.NET even if I have to change what was “done” in my free time. It was difficult to change his mind but finally he accepted (I was very very stubborn).

It’s true that you really miss something when you don’t have it. I have realized how the ASP.NET programming model has changed my mind when developing web applications and that the change is for good. The only thing that I really liked from my LAMP experience was how easy is to do paging with MySQL.

As I saved a lot of time switching to ASP.NET I tried some controls of the Atlas Control Toolkit. I found quite easy to “AJAXize” an application using the UpdatePanel and the Atlas Control Toolkit but I also find out that it really was an alpha release. I used the ReorderList, the CascadingDropDown, the AutoCompleteExtender and the TextBoxWatermark and I found a bug in each one.

Now that things have calmed down a bit I’ll try to post a cool tip next week about using TableAdapters and custom paging but this long weekend (monday is holiday here) it's time to relax.

Sunday, April 30, 2006 4:20:34 PM (Romance Daylight Time, UTC+02:00)  #    Comments [2]   ASP.NET  | 
Tuesday, July 25, 2006 9:16:53 PM (Romance Daylight Time, UTC+02:00)
As a result, the ASP.NET site will now begin to favor IE and be less compatible with newer browsers like Firefox and the ACID-compliant browsers. Not off the bat, I'm sure, but MS has shown no interest to make ASP.NET support non-IE browsers. You won, but site visitors lose.
Northpaw
Tuesday, July 25, 2006 10:06:41 PM (Romance Daylight Time, UTC+02:00)
Most standard ASP.NET controls render xhtml compliant mark up so the site will work in non IE browsers. Certainly in Atlas, non IE browsers are handled as second level citizens (first they make it work for IE and then they create compatibility layers for firefox, opera and safari) but if they fix Atlas, it should work on 98% of the browsers. If more browsers keep surfacing probably they will have to rethink the "compatibility layer" or have a ton of programmers making compatibility layers for each browser...
All comments require the approval of the site owner before being displayed.
Name
E-mail
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.