ASP.NET真的像他们声称的一样好吗？ （不，这不是巨魔，请阅读） [英] Is ASP.NET really as good as they claim? (No, this isn't a troll, please read)

问题描述

你好，


这不是一个巨魔，这是一个真正的问题。请正确阅读

以了解原因。

多年来我一直在使用Vusual Basic和Classic ASP，并且

现在开始关注ASP.NET了。乍一看，它看起来非常优秀，虽然没有什么是经典ASP无法做到的。

我已经通过一些教程并对如何留下深刻印象很快

你可以在页面上获得数据库信息。


让我担心的是它是否真的像它看起来一样好。好几年之后，MS试图通过向VB引入Web类来说服VB程序员进入编写网站

。乍一看，这些看起来像是一个非常快速简便的网站编码方式。普遍意见

对他们来说，当你试图获得任何真实的东西时，它们很糟糕。你花了很多时间与系统进行斗争

你本来可以手动更快地做到这一点。


同样的事情发生在MS推出时将数据环境转换为VB。

再次，这应该是一个RAD工具，用于快速获取基于数据库的
应用程序。第一印象是非常有利的，但是你很快就发现自己写了更多的代码来对抗系统而不是你想要通过手工完成所有这些操作来做到这一点。 。


还有其他一些例子，但我认为这一点很清楚。那个

似乎是一个很棒的代码编写方式，当你尝试迈出第二步时，可能会成为一个编码噩梦。


那么，ASP.NET是一样的，还是MS终于搞定了？我的第一个

印象是它很棒，可以节省很多时间。麻烦

，我几乎可以感觉自己要回到几年前，当我第一次尝试数据环境时，b $ b。这让我很担心，我是否会开始使用它然后发现它比它的价值更令人烦恼？


人们在ASP.NET中做专业网站仍然认为它很好吗？

也许这是一个错误的地方，任何讨厌它的人都会问，并给了

可能不会在这里阅读，但我仍然希望有一些

再次保证，如果我学习了，那么我的时间将会很好地投资

ASP.NET。鉴于我的代码库已经建立了很多年b / b
，我可以很快地在经典ASP中获得数据库驱动的网站。

我不是除非我知道另一种选择是真正的改善。


正如我在开始时说的那样，这是一个真正的问题，而不是巨魔。

请妥善回复。 TIA

Hello,

This is NOT a troll, it''s a genuine question. Please read right
through to see why.

I have been using Vusual Basic and Classic ASP for some years, and
have now started looking at ASP.NET. At first glance, it looks
excellent, albeit nothing that couldn''t have been done to Classic ASP.
I have been through a few tutorials and was impressed with how quickly
you can get database info onto a page.

What worries me is if it really is as good as it looks. Some years
ago, MS tried to persuade VB programmers to get into writing web sites
by introducing Web Classes to VB. These looked, at first glance, like
a really quick and easy way to code a web site. The universal opinion
on them was that they were awful when you tried to get anything real
done with them. You spent so much time fighting with the system that
you would have been quicker doing it by hand in the first place.

Same thing happened when MS introduced the Data Environment into VB.
Again, this was supposed to be a RAD tool for getting database-based
apps up quickly. The first impressions were very favourable, but you
quickly found yourself writing more code to fight the system than you
would have done by doing it all by hand in the first place.

There are other examples, but I think the point is clear. That which
appears to be a fantastic way to code initially may turn out to be a
coding nightmare when you try and take the second steps.

So, is ASP.NET the same, or have MS finally got it right? My first
impression is that is it great and could save a lot of time. Trouble
is, I can almost feel myself going back a few years to when I first
tried the Data Environment. That''s what worries me, am I going to
start with it and then find it''s more bother than it''s worth?

Do people do professional sites in ASP.NET and still think it''s good?
Maybe this is the wrong place to ask as anyone who hated it and gave
up probably wouldn''t be reading here, but I would still like some
reassurance that my time is going to be invested well if I learn
ASP.NET. Given my extensive code library, built up over a number of
years, I can get db-driven web sites up in Classic ASP quite quickly.
I''m not going to drop that unless I know the alternative is a genuine
improvement.

As I said at the start, this is a genuine question, not a troll.
Please reply appropriately. TIA

推荐答案

ASP.NET真正引入了分离UI和代码的概念。因此，UI

仍然可以由网页设计师完成，它可以以任何你想要的方式显示。然后由编写代码的开发人员提供

功能。


" Alan Silver" <去**** @ alansilver.co.uk>在留言中写道

news：90 ************************** @ posting.google.c om ...

ASP.NET really introduces the concept of separating UI and code. So the UI
can still be done by a web designer and it can look any way you want. The
functionality is then provided by a developer who write the code behind.

"Alan Silver" <go****@alansilver.co.uk> wrote in message
news:90**************************@posting.google.c om...

你好，

这不是一个巨魔，这是一个真正的问题。请正确阅读
以了解原因。
我已经使用Vusual Basic和Classic ASP多年了，现在已经开始关注ASP.NET了。乍一看，它看起来非常好，虽然没有什么是经典ASP无法做到的。
我已经完成了一些教程并且对你能获得多快的印象深刻印象深刻数据库信息到页面上。

让我担心的是它是否真的像它看起来一样好。多年前，MS试图通过向VB引入Web类来说服VB程序员进入编写网站。乍一看，这些看起来像是一种非常快速简便的网站编码方式。对他们的普遍看法是，当你试图用它们做任何真实的事情时，它们很糟糕。你花了很多时间与系统进行斗争，以至于你本来可以更快地手工操作。

当MS将数据环境引入VB时，同样的事情发生了。同样，这应该是一个RAD工具，用于快速获取基于数据库的应用程序。第一印象非常有利，但是你很快发现自己编写了更多的代码来对抗系统而不是你本来可以手工完成这一切。
还有其他一些例子，但我认为这一点很清楚。当你尝试采取第二步时，那似乎是一种极好的编码方式可能会成为一个编码的噩梦。

所以，是ASP.NET同样的，还是MS终于搞定了？我的第一个印象是它很棒，可以节省很多时间。麻烦
是，我几乎感觉自己要回到几年后才第一次尝试数据环境。这让我很担心，我是否会开始使用它然后发现它比它的价值更麻烦？

人们在ASP中做专业网站吗？ .NET仍然认为它很好吗？
也许这是一个错误的地方，因为任何讨厌它并给予
的人可能不会在这里阅读，但我仍然会喜欢
保证，如果我学习ASP.NET，我的投入时间会很长。鉴于我的代码库已经建立了很多年，我可以很快地在经典ASP中使用数据库驱动的网站。
我不会放弃它，除非我知道替代方案是真正的改进。

正如我在开始时所说，这是一个真正的问题，而不是巨魔。
请适当回复。 TIA

Hello,

This is NOT a troll, it''s a genuine question. Please read right
through to see why.

I have been using Vusual Basic and Classic ASP for some years, and
have now started looking at ASP.NET. At first glance, it looks
excellent, albeit nothing that couldn''t have been done to Classic ASP.
I have been through a few tutorials and was impressed with how quickly
you can get database info onto a page.

What worries me is if it really is as good as it looks. Some years
ago, MS tried to persuade VB programmers to get into writing web sites
by introducing Web Classes to VB. These looked, at first glance, like
a really quick and easy way to code a web site. The universal opinion
on them was that they were awful when you tried to get anything real
done with them. You spent so much time fighting with the system that
you would have been quicker doing it by hand in the first place.

Same thing happened when MS introduced the Data Environment into VB.
Again, this was supposed to be a RAD tool for getting database-based
apps up quickly. The first impressions were very favourable, but you
quickly found yourself writing more code to fight the system than you
would have done by doing it all by hand in the first place.

There are other examples, but I think the point is clear. That which
appears to be a fantastic way to code initially may turn out to be a
coding nightmare when you try and take the second steps.

So, is ASP.NET the same, or have MS finally got it right? My first
impression is that is it great and could save a lot of time. Trouble
is, I can almost feel myself going back a few years to when I first
tried the Data Environment. That''s what worries me, am I going to
start with it and then find it''s more bother than it''s worth?

Do people do professional sites in ASP.NET and still think it''s good?
Maybe this is the wrong place to ask as anyone who hated it and gave
up probably wouldn''t be reading here, but I would still like some
reassurance that my time is going to be invested well if I learn
ASP.NET. Given my extensive code library, built up over a number of
years, I can get db-driven web sites up in Classic ASP quite quickly.
I''m not going to drop that unless I know the alternative is a genuine
improvement.

As I said at the start, this is a genuine question, not a troll.
Please reply appropriately. TIA

我在这里不同意......我对ASP.Net的看法是它可以让你写出

真正的N级和OO代码......但是你需要遵守纪律和警惕

。我不确定你的意思，但我猜你是

引用代码隐藏之类的东西。就我而言，代码隐藏

并不会促进N-Tier，相反它会阻碍它。人们认为，如果他们使用代码隐藏，他们正在开发一个N层系统，因为

表示层似乎与业务层分离。只有

的问题是分离只是物理的，不合逻辑的...使用像

VS.Net这样的工具代码隐藏/ ASPX文件强耦合，意味着没有真正的

分离存在。除此之外，代码隐藏应该是

表示逻辑层的位置而不是业务层...大多数人认为

代码隐藏是业务层，但当然它不可能因为它被绑定到某个特定的页面。


幸运的是他们在ASP.Net 2.0中得到了正确的介绍皮肤，

主题和部分课程。但回到这一点，使用ASP.Net

1.X它可以实现这一点，只是没有它可能那么简单或者

应该看起来（举一个很好的例子，看看社区服务器论坛，它们不会使用代码隐藏或代码内联，而是依靠蒙皮

机制来帮助推广这一方面N-Tier）。


我也可以指向数据集，我认为从OO

立场和N-Tier立场来看都很糟糕（虽然他们肯定有他们的b
/地方/优势）。但是再一次，.Net框架提供了非常强大的b $ b替代品（在这种情况下有一堆）。


是的，ASP.Net很严重，现在已经存在了足够长的时间（〜5年），以及b / b
。不会有另一个版本的经典ASP所以

你将不得不在某些时候转向JSP或ASP.Net。然而，

的学习曲线是有意识的，如果你想构建严肃的系统，那么你需要知道他们在做什么并且不会采取的人简单的

出路（有很多）。


Karl


-

MY ASP.Net教程
http：//www.openmymind。 net /

" Marina" <所以***** @ nospam.com>在消息中写道

news：％2 *************** @ TK2MSFTNGP09.phx.gbl ...

i can''t agree here...my opinion of ASP.Net is that it enables you to write
true N-Tier and OO code...but that you need to be disciplined and vigilant
about it. I''m not sure what you mean by this, but I''m guessing you are
refering to things like codebehind. As far as I''m concerned, codebehind
doesn''t promote N-Tier, instead it hinders it. People think that if they
use codebehind they are developing an N-Tier system, because the
presentation layer is seemingly separated from the business layer. Only
problem is the separation is merely physical, not logical...using tools like
VS.Net the codebehind/ASPX files are strongly-coupled, meaning no true
separation exists. Added to this, codebehind should be the location of the
presentation logic layer NOT the business layer...most people think
codebehind IS the business layer, but of course it can''t be since it''s tied
to a specific page.

Luckily they got it right in ASP.Net 2.0 with the introduction of skins,
themes and partial classes. But getting back to the point, using ASP.Net
1.X it''s possible to achieve this, just not as simple as it might be or
should seem (for a good example, check out the communityserverforums which
don''t use codebehind nor code-inline, but instead rely on a skinning
mechanism to help promote that side of N-Tier).

I can also point to datasets, which I think are horrible from both an OO
standpoint and an N-Tier standpoint (though they certainly have their
place/advantage). But yet again, the .Net framework provides very capable
alternatives (there are a bunch in this case).

Yes, ASP.Net is serious and has been around for long enough now (~5years) to
say so with authority. There won''t be another version of classic ASP so
you''re going to have to move to either JSP or ASP.Net at some point. The
learning curve however is viscious and if you want to build serious systems,
you''ll need people who know what they are doing and won''t just take the easy
way out (which there are a lot of).

Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
"Marina" <so*****@nospam.com> wrote in message
news:%2***************@TK2MSFTNGP09.phx.gbl...

ASP.NET真正介绍了分离UI和代码的概念。因此，
UI仍然可以由网页设计师完成，它可以以任何你想要的方式显示。然后由编写代码的开发人员提供
功能。

Alan Silver <去**** @ alansilver.co.uk>在消息中写道
新闻：90 ************************** @ posting.google.c om ...

ASP.NET really introduces the concept of separating UI and code. So the UI can still be done by a web designer and it can look any way you want. The
functionality is then provided by a developer who write the code behind.

"Alan Silver" <go****@alansilver.co.uk> wrote in message
news:90**************************@posting.google.c om...

你好，

这不是一个巨魔，这是一个真正的问题。请正确阅读
以了解原因。
我已经使用Vusual Basic和Classic ASP多年了，现在已经开始关注ASP.NET了。乍一看，它看起来非常好，虽然没有什么是经典ASP无法做到的。
我已经完成了一些教程并且对你能获得多快的印象深刻印象深刻数据库信息到页面上。

让我担心的是它是否真的像它看起来一样好。多年前，MS试图通过向VB引入Web类来说服VB程序员进入编写网站。乍一看，这些看起来像是一种非常快速简便的网站编码方式。对他们的普遍看法是，当你试图用它们做任何真实的事情时，它们很糟糕。你花了很多时间与系统进行斗争，以至于你本来可以更快地手工操作。

当MS将数据环境引入VB时，同样的事情发生了。同样，这应该是一个RAD工具，用于快速获取基于数据库的应用程序。第一印象非常有利，但是你很快发现自己编写了更多的代码来对抗系统而不是你本来可以手工完成这一切。
还有其他一些例子，但我认为这一点很清楚。当你尝试采取第二步时，那似乎是一种极好的编码方式可能会成为一个编码的噩梦。

所以，是ASP.NET同样的，还是MS终于搞定了？我的第一个印象是它很棒，可以节省很多时间。麻烦
是，我几乎感觉自己要回到几年后才第一次尝试数据环境。这让我很担心，我是否会开始使用它然后发现它比它的价值更麻烦？

人们在ASP中做专业网站吗？ .NET仍然认为它很好吗？
也许这是一个错误的地方，因为任何讨厌它并给予
的人可能不会在这里阅读，但我仍然会喜欢
保证，如果我学习ASP.NET，我的投入时间会很长。鉴于我的代码库已经建立了很多年，我可以很快地在经典ASP中使用数据库驱动的网站。
我不会放弃它，除非我知道替代方案是真正的改进。

正如我在开始时所说，这是一个真正的问题，而不是巨魔。
请适当回复。 TIA

Hello,

This is NOT a troll, it''s a genuine question. Please read right
through to see why.

I have been using Vusual Basic and Classic ASP for some years, and
have now started looking at ASP.NET. At first glance, it looks
excellent, albeit nothing that couldn''t have been done to Classic ASP.
I have been through a few tutorials and was impressed with how quickly
you can get database info onto a page.

What worries me is if it really is as good as it looks. Some years
ago, MS tried to persuade VB programmers to get into writing web sites
by introducing Web Classes to VB. These looked, at first glance, like
a really quick and easy way to code a web site. The universal opinion
on them was that they were awful when you tried to get anything real
done with them. You spent so much time fighting with the system that
you would have been quicker doing it by hand in the first place.

Same thing happened when MS introduced the Data Environment into VB.
Again, this was supposed to be a RAD tool for getting database-based
apps up quickly. The first impressions were very favourable, but you
quickly found yourself writing more code to fight the system than you
would have done by doing it all by hand in the first place.

There are other examples, but I think the point is clear. That which
appears to be a fantastic way to code initially may turn out to be a
coding nightmare when you try and take the second steps.

So, is ASP.NET the same, or have MS finally got it right? My first
impression is that is it great and could save a lot of time. Trouble
is, I can almost feel myself going back a few years to when I first
tried the Data Environment. That''s what worries me, am I going to
start with it and then find it''s more bother than it''s worth?

Do people do professional sites in ASP.NET and still think it''s good?
Maybe this is the wrong place to ask as anyone who hated it and gave
up probably wouldn''t be reading here, but I would still like some
reassurance that my time is going to be invested well if I learn
ASP.NET. Given my extensive code library, built up over a number of
years, I can get db-driven web sites up in Classic ASP quite quickly.
I''m not going to drop that unless I know the alternative is a genuine
improvement.

As I said at the start, this is a genuine question, not a troll.
Please reply appropriately. TIA

如果有人将他们的所有代码直接放入代码隐藏中，那么他们就是

之前有点好一点，但这并没有真正推广模块化的b $ b可重用代码。是不是更好的意大利面条代码所有动态HTML

是用一系列Response.Write'来完成的，是不可理解的？

是的，到目前为止，没有比较。


它确实意味着你可以让UI设计师在客户面前工作

页面的一部分，开发人员编写代码后来。我的观点

这里，页面的外观质量将完全取决于谁在做你的用户界面，并且asp.net不会引入

对此的限制。


现在，我没有声称只是因为代码和用户界面分开了你

获得真正的N层代码等。任何人都可以完全以非模块化的方式编写所有代码，1层方式，无论是Web表单还是Windows表单。所有

取决于开发人员的技能和远见。对我来说，这是一个完全独立的话题，而不是这个人的问题。


" Karl Seguin" < karl REMOVE @ REMOVE openmymind REMOVEMETOO。 ANDME net>

在消息新闻中写道：OB ************** @ TK2MSFTNGP14.phx.gbl ...

If someone puts all their code directly into the codebehind, well, then they
are somewhat better off then before, but that doesn''t truly promote modular
reusable code. Is it better then spaghetti code where all the dynamic HTML
is done with a series of Response.Write''s and is impossible to understand?
Yes, by far, no comparison.

And it does mean that you can have a UI designer work on the client facing
part of the page, and the developer write the code later. And my point
here, was that the quality of appearence of the pages is going to be
completely dependent on who is doing your UI, and that asp.net introduces no
limitations on this.

Now, I didn''t claim that just because the code and the UI are separated you
get true N-tier code, etc. Anyone can write all their code in a completely
non-modular way, 1 tier way, be it web forms or windows forms. This all
depends on the skill and forsight of the developer. To me, this is a
completely separate topic, and not what the person asked.

"Karl Seguin" <karl REMOVE @ REMOVE openmymind REMOVEMETOO . ANDME net>
wrote in message news:OB**************@TK2MSFTNGP14.phx.gbl...

我可以在这里不同意......我对ASP.Net的看法是，它可以让你写出真正的N-Tier和OO代码......但是你需要遵守纪律和警惕
关于它。我不确定你的意思，但我猜你是在谈论代码隐藏之类的东西。就我而言，代码隐藏
并不会促进N-Tier，相反它会阻碍它。人们认为，如果他们使用代码隐藏，他们正在开发一个N层系统，因为
表示层似乎与业务层分离。只有
问题是分离只是物理的，而不是逻辑的...使用工具
像VS.Net一样，代码隐藏/ ASPX文件是强耦合的，这意味着不存在真正的分离。除此之外，代码隐藏应该是
的位置，表示逻辑层而不是业务层......大多数人认为
代码隐藏是业务层，但当然它不可能是因为它'
绑定到特定页面。

幸运的是，他们在ASP.Net 2.0中通过引入皮肤，
主题和部分类来正确使用它。但回到这一点，使用ASP.Net
1.X它可以实现这一点，只是没有它可能看起来那样简单或者看起来很好（例如，检查出来）社区服务论坛不使用代码隐藏或代码内联，而是依靠蒙皮机制来帮助推广N-Tier的这一面。

我可以也指向数据集，我认为从OO
立场和N-Tier立场来看都是可怕的（尽管他们肯定有他们的优势/优势）。但是再一次，.Net框架提供了非常强大的替代方案（在这种情况下有很多）。

是的，ASP.Net是认真的，现在已经存在了很长时间（ 〜5年）
以权威说出来。不会有另一个版本的经典ASP所以
你将不得不在某些时候转向JSP或ASP.Net。然而，
学习曲线是有意识的，如果你想构建严肃的
系统，你需要知道他们正在做什么的人，并且不会只是简单地拿出
（其中有很多）。

Karl

-
我的ASP.Net教程
http://www.openmymind.net/

" Marina" <所以***** @ nospam.com>在消息中写道
新闻：％2 *************** @ TK2MSFTNGP09.phx.gbl ...

i can''t agree here...my opinion of ASP.Net is that it enables you to write
true N-Tier and OO code...but that you need to be disciplined and vigilant
about it. I''m not sure what you mean by this, but I''m guessing you are
refering to things like codebehind. As far as I''m concerned, codebehind
doesn''t promote N-Tier, instead it hinders it. People think that if they
use codebehind they are developing an N-Tier system, because the
presentation layer is seemingly separated from the business layer. Only
problem is the separation is merely physical, not logical...using tools like VS.Net the codebehind/ASPX files are strongly-coupled, meaning no true
separation exists. Added to this, codebehind should be the location of the presentation logic layer NOT the business layer...most people think
codebehind IS the business layer, but of course it can''t be since it''s tied to a specific page.

Luckily they got it right in ASP.Net 2.0 with the introduction of skins,
themes and partial classes. But getting back to the point, using ASP.Net
1.X it''s possible to achieve this, just not as simple as it might be or
should seem (for a good example, check out the communityserverforums which
don''t use codebehind nor code-inline, but instead rely on a skinning
mechanism to help promote that side of N-Tier).

I can also point to datasets, which I think are horrible from both an OO
standpoint and an N-Tier standpoint (though they certainly have their
place/advantage). But yet again, the .Net framework provides very capable
alternatives (there are a bunch in this case).

Yes, ASP.Net is serious and has been around for long enough now (~5years) to say so with authority. There won''t be another version of classic ASP so
you''re going to have to move to either JSP or ASP.Net at some point. The
learning curve however is viscious and if you want to build serious systems, you''ll need people who know what they are doing and won''t just take the easy way out (which there are a lot of).

Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
"Marina" <so*****@nospam.com> wrote in message
news:%2***************@TK2MSFTNGP09.phx.gbl...

ASP.NET真正引入了这个概念分离UI和代码。所以

ASP.NET really introduces the concept of separating UI and code. So the

UI

UI

仍然可以由网页设计师完成，它可以任何你想要的方式。
然后由编写代码的开发人员提供该功能。

Alan Silver <去**** @ alansilver.co.uk>在消息中写道
新闻：90 ************************** @ posting.google.c om ...

can still be done by a web designer and it can look any way you want. The functionality is then provided by a developer who write the code behind.

"Alan Silver" <go****@alansilver.co.uk> wrote in message
news:90**************************@posting.google.c om...

你好，

这不是一个巨魔，这是一个真正的问题。请正确阅读
以了解原因。
我已经使用Vusual Basic和Classic ASP多年了，现在已经开始关注ASP.NET了。乍一看，它看起来非常好，虽然没有什么是经典ASP无法做到的。
我已经完成了一些教程并且对你能获得多快的印象深刻印象深刻数据库信息到页面上。

让我担心的是它是否真的像它看起来一样好。多年前，MS试图通过向VB引入Web类来说服VB程序员进入编写网站。乍一看，这些看起来像是一种非常快速简便的网站编码方式。对他们的普遍看法是，当你试图用它们做任何真实的事情时，它们很糟糕。你花了很多时间与系统进行斗争，以至于你本来可以更快地手工操作。

当MS将数据环境引入VB时，同样的事情发生了。同样，这应该是一个RAD工具，用于快速获取基于数据库的应用程序。第一印象非常有利，但是你很快发现自己编写了更多的代码来对抗系统而不是你本来可以手工完成这一切。
还有其他一些例子，但我认为这一点很清楚。当你尝试采取第二步时，那似乎是一种极好的编码方式可能会成为一个编码的噩梦。

所以，是ASP.NET同样的，还是MS终于搞定了？我的第一个印象是它很棒，可以节省很多时间。麻烦
是，我几乎感觉自己要回到几年后才第一次尝试数据环境。这让我很担心，我是否会开始使用它然后发现它比它的价值更麻烦？

人们在ASP中做专业网站吗？ .NET仍然认为它很好吗？
也许这是一个错误的地方，因为任何讨厌它并给予
的人可能不会在这里阅读，但我仍然会喜欢
保证，如果我学习ASP.NET，我的投入时间会很长。鉴于我的代码库已经建立了很多年，我可以很快地在经典ASP中使用数据库驱动的网站。
我不会放弃它，除非我知道替代方案是真正的改进。

正如我在开始时所说，这是一个真正的问题，而不是巨魔。
请适当回复。 TIA

Hello,

This is NOT a troll, it''s a genuine question. Please read right
through to see why.

I have been using Vusual Basic and Classic ASP for some years, and
have now started looking at ASP.NET. At first glance, it looks
excellent, albeit nothing that couldn''t have been done to Classic ASP.
I have been through a few tutorials and was impressed with how quickly
you can get database info onto a page.

What worries me is if it really is as good as it looks. Some years
ago, MS tried to persuade VB programmers to get into writing web sites
by introducing Web Classes to VB. These looked, at first glance, like
a really quick and easy way to code a web site. The universal opinion
on them was that they were awful when you tried to get anything real
done with them. You spent so much time fighting with the system that
you would have been quicker doing it by hand in the first place.

Same thing happened when MS introduced the Data Environment into VB.
Again, this was supposed to be a RAD tool for getting database-based
apps up quickly. The first impressions were very favourable, but you
quickly found yourself writing more code to fight the system than you
would have done by doing it all by hand in the first place.

There are other examples, but I think the point is clear. That which
appears to be a fantastic way to code initially may turn out to be a
coding nightmare when you try and take the second steps.

So, is ASP.NET the same, or have MS finally got it right? My first
impression is that is it great and could save a lot of time. Trouble
is, I can almost feel myself going back a few years to when I first
tried the Data Environment. That''s what worries me, am I going to
start with it and then find it''s more bother than it''s worth?

Do people do professional sites in ASP.NET and still think it''s good?
Maybe this is the wrong place to ask as anyone who hated it and gave
up probably wouldn''t be reading here, but I would still like some
reassurance that my time is going to be invested well if I learn
ASP.NET. Given my extensive code library, built up over a number of
years, I can get db-driven web sites up in Classic ASP quite quickly.
I''m not going to drop that unless I know the alternative is a genuine
improvement.

As I said at the start, this is a genuine question, not a troll.
Please reply appropriately. TIA

这篇关于ASP.NET真的像他们声称的一样好吗？ （不，这不是巨魔，请阅读）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！