ASP.NET WebForms评估 [英] ASP.NET WebForms Evaluation
问题描述
您好，
我正在评估ASP.NET
到目前为止，我没有留下任何印象。
我明白微软想要开发他们的开发环境
很容易初学者，但他们似乎也希望专业的开发人员能够使用这种垃圾。
-------------- -------------------------------------------------- ---
DataGrid& UserControls
----------------------------------------- --------------------------
优点
--- -
- 节省我不得不花1分钟打字简单代码（即：循环和
方法）
- 显然可以节省我担心格式化（是的，对吧）
缺点
----
- 停止我使用OO编程约定进行html渲染
- 更新版本的asp.net中的更改风险
- 需要时间来学习我们何时拥有合适的技能（即：我们知道
html并且可以编写代码）
- 这种声明/过度封装的方法总是会导致
处于混乱的变通方法中
- 非常低效的分页实现 - 无法在
生产服务器中使用
- 需要担心的大量额外文件（用户控件，数据集）
- ASPX页面在调用之前不能编译，因此需要更长的时间来调试
我是唯一一个会避开这些功能的人吗？
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
推荐答案
re：
我是唯一一个会避开这些功能的人吗？
No.
看来你是我们现在的常驻巨魔。
; - ）
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Espa？ol
Ven，y hablemos de ASP.NET ...
======================
" John Rivers" <音响***** @ btinternet.com>在留言中写道
news：11 ********************** @ g43g2000cwa.googlegr psps.com ...你好，
我正在评估ASP.NET
到目前为止，我没有留下深刻的印象。
在我看来，基本的评估是使用HTML服务器控件，数据控件，用户控件等内容的PRO和CON都以同样的方式分解：很多缺点很少有专业人士。
我了解微软希望为初学者提供轻松的开发环境，但他们似乎也希望专业开发人员能够使用这种垃圾。
------- -------------------------------------------------- ----------
DataGrid& UserControls
--------------------------------------------- ----------------------
优点
----
- 救我不得不花1分钟打字简单的代码（即：循环和
方法）
- 显然可以让我免于担心格式（是的，对吧）
Cons
----
- 阻止我使用面向对象的渲染的OO编程约定
- 更新版本的asp.net中的更改风险
- 需要时间来了解我们何时拥有已经适合的技能（即：我们知道
HTML并且可以编写代码）
- 这种声明性/过度封装的方法总是会导致混乱的解决方法
- 非常低效的分页实现 - 无法在
生产服务器中使用
- 需要担心的大量额外文件（用户控件，数据集）
- ASPX页面在调用之前不能编译，因此需要更长的时间来调试
我是唯一一个会避开这些功能的人吗？
John Rive rs
Am I the only one who will be avoiding these "features"?
No.
It appears you''re our current resident troll.
;-)
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Espa?ol
Ven, y hablemos de ASP.NET...
======================
"John Rivers" <fi*****@btinternet.com> wrote in message
news:11**********************@g43g2000cwa.googlegr oups.com... 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 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.
你可能会得到一些争论的答案，但你的陈述中有一些事实
。在asp.net中进行了几年的密集编程之后，我发现如果你从一个html原型启动一个新的页面
而不是添加runat它会更有效率=服务器"如所须。并且带有数据绑定项目的转发器
比数据网格更灵活。
Eliyahu
You will probably get a number of arguing responses, but there is some truth
in your statement. After a few years of intensive programming in asp.net, I
found it much more efficient if you start a new page from an html prototype
and than add "runat=server" as needed. And a repeater with databound items
gives you much more flexibility than a datagrid.
Eliyahu
我的想法
My thoughts
- 阻止我使用OO编程约定进行html渲染
如何阻止它，你可以控制HTML
如果您不喜欢网页控件html，请使用html控件
如果您不喜欢DataGrids html，请使用转发器/数据列表
地狱，建立一个for循环，它可以完成
- 更新版本的asp.net改变的风险
更改是记录良好。
您可以同时运行所有版本的.net进行测试
此外，如果它没有改变，那么它就不会变得更好
- 花时间学习我们什么时候已经有合适的技能（即：我们知道
html并且可以编写代码）
你还需要知道ASP.NET中的Html
C. odes不断发展，所以你必须这么多b $ b - 这种声明/过度封装的方法总会导致凌乱的解决方法
凌乱的解决方法=编码错误或设计
听起来像开发人员的问题，而不是工具
- 非常低效的分页实现 - 无法在
生产服务器中使用
这是因为你不知道如何，或者它不会工作
如果你不喜欢内置的自定义分页分页
即它是可选的，你仍然可以使用传统的分页方法
- 许多额外的文件需要担心（usercontrols，数据集）
DataSet不是文件，它是一个对象
Usercontrols是可重用的，所以成为一个单独的文件是有意义的
- ASPX页面不要'编译，直到调用所以需要更长的时间来调试
这是第一次调用它，它必须在一段时间内编译
" John Rivers" <音响***** @ btinternet.com>在留言中写道
news：11 ********************** @ g43g2000cwa.googlegr psps.com ...你好，
我正在评估ASP.NET
到目前为止，我没有留下深刻的印象。
在我看来，基本的评估是使用HTML服务器控件，数据控件，用户控件等内容的PRO和CON都以同样的方式分解：很多缺点很少有专业人士。
我了解微软希望为初学者提供轻松的开发环境，但他们似乎也希望专业开发人员能够使用这种垃圾。
------- -------------------------------------------------- ----------
DataGrid& UserControls
--------------------------------------------- ----------------------
优点
----
- 救我不得不花1分钟打字简单的代码（即：循环和
方法）
- 显然可以让我免于担心格式（是的，对吧）
Cons
----
- 阻止我使用面向对象的渲染的OO编程约定
- 更新版本的asp.net中的更改风险
- 需要时间来了解我们何时拥有已经适合的技能（即：我们知道
HTML并且可以编写代码）
- 这种声明性/过度封装的方法总是会导致混乱的解决方法
- 非常低效的分页实现 - 无法在
生产服务器中使用
- 需要担心的大量额外文件（用户控件，数据集）
- ASPX页面在调用之前不能编译，因此需要更长的时间来调试
我是唯一一个会避开这些功能的人吗？
John Rive rs
- stops me from using OO programming conventions for html rendering
How on earth does it stop that, You can control the HTML
If you don''t like the web control html, use html controls
If you don''t like the DataGrids html, user a repeater/datalist
Hell, build a for loop, it can be done
- risk of change in newer versions of asp.net
Changes are well documented.
You can run all versions of .net simultaneously for testing
Besides, if it weren''t changing, then it wouldn''t be getting better
- takes time to learn when we have suitable skills already (ie: we know
html and can write code)
you still need to know Html in ASP.NET
Codes evolving, so must you
- this sort of declarative / over-encapsulated approach always results
in messy workarounds
Messy workarounds = bad coding or design
Sounds like its the developer thats the problem, not the tool
- very inefficient pagination implementation - couldn''t use in
production server
Is that cause you don''t know how, or it wouldn''t work
Custom paging is available if you don''t like the built in paging
i.e. its optional, you can still use traditional paging methods
- lots of extra files to worry about (usercontrols, datasets)
A DataSet is not a file, its an object
Usercontrols are reusable, so it makes sense to be a seperate file
- ASPX pages don''t compile until called so takes longer to debug
Thats only the first time its called, it has to be compiled some time
"John Rivers" <fi*****@btinternet.com> wrote in message
news:11**********************@g43g2000cwa.googlegr oups.com... 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
这篇关于ASP.NET WebForms评估的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
