ASP.Net 2.0 a third language ?

Just few thoughts for the day after reading some excellent articles in the latest MSDN magazine regarding ASP.Net 2.0

I still have to find some time to play with the Technology Preview, but MSDN help me to catch up with the new .Net.

I have anyway some concerns (not too important thankfully) about the way MS implement more on more <asp:something tags.
I have in mind for example the new sqlDatasource and I am worrying about the number of parameters that we can now implement. It looks for me like a way back to the bad time of code spaghetti.
I know about the master pages, and the eventual separation between design and code, but are we not going ahead to a third language with .Net ?

A kind of ASP.Net# if you know what I mean. I have also the feeling that a lot of laziness will emerge from this. Giving all the trust to the framework regarding the performances, and the security aspect, is it something really we want ?

I imagine also that this new <asp: approach could create a third kind of developer, with less concerns on the fundamentals, but more incline to easy job.

Of course I like more controls, but I prefer to not use too much parameters in my web pages, I rather prefer the code approach for this. So the numerous (maybe some overdose there) articles on ASP.Net 2.0 show IMO too much the 'easy' to see in your face tags, and not maybe enough of the scene behind.

A last thing too, and surely it's a bit extreme, but don't you think that at some stage the <asp: tags shouldn't be presented for normalisation to the WWW authorities for validation ?

 

1 Comment

  • Agree, Microsoft is making Asp.Net a toy, easy to use framework for people who do not understand programming. It never was a proffesional framework (splitting a file into two does not equal separation of code and presentation) but now it's definitelly heading the VB way. Just think about what partial types will let you do, a single class implemented in five different files. Same with the asp:sql tag, declaring a connection in every single page that uses a connection, as opposed to declaring it (the parameters) in a data access code.



    I'm starting to give up on .Net, Microsoft definitelly doesn't care about doing things right, they care about doing them simple so monkeys can use them.

Comments have been disabled for this content.