J
John Rivers
Hello,
I am in the process of evaluating ASP.NET
So far I am not impressed at all.
It seems to me that a basic evaluation of the PROs and CONs
of using things like HTML Server Controls, Data Controls, User Controls
etc. all breaks down the same way: lots of cons very few pros.
I understand that microsoft wants to make their development environment
easy for beginners, but they seem to expect
professional developers to use this rubbish as well.
-------------------------------------------------------------------
DataGrid & UserControls
-------------------------------------------------------------------
Pros
----
- saves me having to spend 1 minute typing simple code (ie: loop and
method)
- apparently saves me from worrying about about format (yeah, right)
Cons
----
- stops me from using OO programming conventions for html rendering
- risk of change in newer versions of asp.net
- takes time to learn when we have suitable skills already (ie: we know
html and can write code)
- this sort of declarative / over-encapsulated approach always results
in messy workarounds
- very inefficient pagination implementation - couldn't use in
production server
- lots of extra files to worry about (usercontrols, datasets)
- ASPX pages don't compile until called so takes longer to debug
Am I the only one who will be avoiding these "features"?
John Rivers
I am in the process of evaluating ASP.NET
So far I am not impressed at all.
It seems to me that a basic evaluation of the PROs and CONs
of using things like HTML Server Controls, Data Controls, User Controls
etc. all breaks down the same way: lots of cons very few pros.
I understand that microsoft wants to make their development environment
easy for beginners, but they seem to expect
professional developers to use this rubbish as well.
-------------------------------------------------------------------
DataGrid & UserControls
-------------------------------------------------------------------
Pros
----
- saves me having to spend 1 minute typing simple code (ie: loop and
method)
- apparently saves me from worrying about about format (yeah, right)
Cons
----
- stops me from using OO programming conventions for html rendering
- risk of change in newer versions of asp.net
- takes time to learn when we have suitable skills already (ie: we know
html and can write code)
- this sort of declarative / over-encapsulated approach always results
in messy workarounds
- very inefficient pagination implementation - couldn't use in
production server
- lots of extra files to worry about (usercontrols, datasets)
- ASPX pages don't compile until called so takes longer to debug
Am I the only one who will be avoiding these "features"?
John Rivers