blocks|key|1557867|text|首先，性能、可伸缩性和一个框架为web应用程序的无状态世界提供了更好的基础。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1557868|Wikipedia's+ASP.Net+page+has+a+section对差异的看法。|offset|length|1557869|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/ASP.NET#ASP.NET_compared_with_classic_ASP^0|0|0|12|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Performance, scalability, and a framework that provides a much better foundation for the stateless world of web applications, for a start.

<a href="https://en.wikipedia.org/wiki/ASP.NET#ASP.NET_compared_with_classic_ASP" rel="nofollow noreferrer">Wikipedia's ASP.Net page has a section</a> on the differences.

blocks|key|1557964|text|对于简单的网站，我实际上更喜欢ASP而不是ASP.NET，特别是如果你很了解超文本标记语言。然而，使用ASP将业务逻辑与视图分开是很困难的；您编写的代码很可能很难阅读和维护。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1557965|不过，PHP比ASP更好--在基本层面上也有些类似。如果你对自包含的web开发堆栈感兴趣(但学习曲线要长得多)，你可以随时去Rails或Django。|1557966|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

For simple sites, I actually prefer ASP vs. ASP.NET, especially if you know HTML well. However with ASP, separating business logic from view is hard; the code you write will likely be challenging to read + maintain.

PHP is better than ASP though - and somewhat similar at the basic level. And you could always go to Rails or Django, if you're interested in self-contained web development stack (but a lot longer learning curve).

blocks|key|1558029|text|ASP.NET的一个优点是，您可以选择完全像使用经典的.NET一样编写站点代码，同时还可以访问丰富的ASP框架。您可以保留现有功能，并根据需要添加新的ASP.NET功能。它们很好地融合在一起。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1558030|不幸的是，引用的article的作者并不精通ASP.NET背后的技术，这从他的评论中可以看出(甚至可能不是典型的ASP)。他的大部分观点要么是无效的，要么是完全错误的。|offset|length|1558031|entityMap|0|LINK|mutability|MUTABLE|url|http://www.packtpub.com/article/Classic-ASP^0|0|8|7|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

One advantage to ASP.NET is that you have the option of coding your site exactly as you did with classic ASP, along with access to the richness of the .NET framework. You can keep existing functionality and add new ASP.NET functionality were needed. They mix well.

Unfortunately the author of the referenced <a href="http://www.packtpub.com/article/Classic-ASP" rel="nofollow noreferrer">article</a> isn't very well versed in the technology behind ASP.NET as evident by his remarks (and maybe not even classic ASP). Most of his points are invalid or simply wrong.

blocks|key|1558118|text|你错过了很多东西！ASP.NET的生产力、健壮性和可维护性比老式的ASP所想的要高出几个数量级。服务器端控件，第三方控件，母版页，窗体身份验证，窗体验证，一个OO模型比鼓励适当的应用程序分区，易于部署，内置调试和跟踪，状态管理。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1558119|您甚至可以选择WebForms或MVC。毫不夸张地说，如果你不彻底调查你所遗漏的东西，你就是疯了。|1558120|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You're missing more than a few things! ASP.NET is orders of magnitudes more productive, robust, and maintainable than old-school ASP ever thought about being. Server side controls, third-party controls, master pages, forms authentication, forms validation, an OO model than encourages appropriate application partitioning, easy deployment, built-in debugging and tracing, state management.

You even have the choice of WebForms or MVC. It's not an understatement to say that you are simply out of your mind if you don't thoroughly investigate what you're missing.

blocks|key|1773355|text|如果你喜欢ASP，并且想要迁移到ASP.NET，那就跳过Webforms，学习MVC。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1773356|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you like ASP, and want to move to ASP.NET, skip Webforms and learn MVC.

blocks|key|1773458|text|如果你做的都是简单的小网页，那就做任何事吧。或者更好地学习PHP。你将得到的大多数回复都是来自web应用程序的开发人员，因此asp.net在功能和可维护性方面都超越了经典的asp。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1773459|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If all you make is simple little web pages, then do whatever. Or better yet learn PHP. Most of the response you are going to get are from people who make web applications, and for that asp.net blows the pants off of classic asp in power and maintainability though.

blocks|key|1558272|text|我只有一个词“调试”--你永远不想使用它，但你总是这样做。在.Net中，如果你使用的是Visual+Studio，那么与尝试在ASP上调试代码相比，你就拥有了一个非常棒的调试器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1558273|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I have one word "debugging" - you never want to have to use it but you always do. In .Net if you're using Visual Studio you have a fantastic debugger when compared to trying to debug code on ASP.

blocks|key|1558390|text|如果你回顾你的旧代码，并说，“我在想什么！这是垃圾，我现在写的代码好多了！”那么你已经发展成为一个程序员了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1558391|如果这些站点是相当临时的(例如，你快速构建它，它被用于特定的目的和时间，然后它被有效地关闭)，那么以对你来说最舒适的方式关闭这些站点是完全可以接受的。|1558392|如果你有一长串的错误，修复和改进，你现在需要(或想要)返回到你的旧网站，或者你的“小网站”正在变得越来越大，越来越复杂，这给你带来了巨大的悲痛，那么你需要后退一步，重新评估你是如何构建和支持这些网站的。|1558393|我非常同意ASP.NET是一个非常成熟和有效的编程环境。然而，就像任何工具一样，你需要知道(或学习)正确使用它的方式，因为它不会在一夜之间自动把你变成一个“超级程序员”。|1558394|打破僵局的一种方法是与你的老板达成一致，同意你创建的下一个“网站”是用ASP.NET开发的。向他解释说，这将比你目前交付网站的方式花费更长的时间，因为你必须“摸索”ASP.NET，但好处是x，y和(练习留给读者！)|1558395|就我个人而言，我还处于过渡阶段(我是从v1开始使用ASP.NET的！)因为我有一个相当健壮的经典ASP框架，我已经开发好了，而且用起来很舒服。但是，我在战略上使用了ASP.NET，并发现它非常强大，而且您最终编写的代码必须更少，因为.net框架中内置了如此多的内容，只要您能在文档中找到它。|1558396|我还建议你不要使用VB.NET，也不要咬紧牙关使用C#。语言的改变是很小的，但是你减少了像以前一样写你的网站的机会。它有助于改掉坏习惯，给你一个学习新技术的机会。|1558397|祝好运!|1558398|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

If you look back at your old code and say, "What was I thinking! This is rubbish, I write code much better now!" then you have developed as a programmer.

If the sites are fairly temporary (i.e. you build it quickly, it gets used for a specific purpose and amount of time and then it is effectively closed) then banging out these sites in the most comfortable way for you is perfectly acceptable.

If you have a long list of bugs, fixes and improvements that you now need (or would like) to backport to your old sites, or your "small sites" are getting bigger and more complidated and this is causing you significant grief then you need to take a step back and re-evaluate how you structure and support these sites.

I would very much agree that ASP.NET is a very much more mature and effective programming environment. However, like any tool, you need to know (or learn) the right way to use it as it's not going to automatically turn you into a "super programmer" overnight.

A way to break the ice is to agree with your boss that the next "site" you create is developed in ASP.NET. Explain to him that it will take quite a lot longer than how you currently deliver sites because you have to "get your head around" ASP.NET, but the benefits are x,y and (exercise left to the reader!)

Personally, I'm still in the transition phase (and I started using ASP.NET from v1!) as I have a fairly robust Classic ASP framework I'm developed and comfortable with. However, I have used ASP.NET strategically and have found it VERY powerful and your do end up writing must less code, as so much is built into the .net framework, as long as you can find it in documentation.

I also recommend that you DONT use VB.NET and your bite the bullet to use C#. The change of language is quite minor, but you reduce the chances of writing your sites exactly the same was as you used to. It helps break the bad habits annd gives you a chance to learn new techniques.

Good Luck!

blocks|key|1773670|text|为了专注于具体的问题(“Classic与.Net的好处”)，我只能想到.Net不会想到的Classic做的两件事：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1773671|1)包括。它们并不像你在ASP.Net中期望的那样工作。当然，ASP.Net提供了更好的方法来完成同样的事情，但它仍然有一些损失，并且会使将旧站点迁移到.Net成为一件痛苦的事情。|1773672|2)+ASP.Net不会位于应用程序的根文件夹之上。在我所在的地方，我们有一个相当复杂的内部网，大部分仍然是传统的ASP，随着事物的更新或新事物的添加，这里和那里都有少量的.Net应用程序。如果能够将通用代码的一个副本放在文件夹层次结构中相当高的位置，并且仍然将每个单独的应用程序隔离到它自己的VD，那将是一件很好的事情。但是，这就是源代码控制的目的，所以这没什么大不了的。|1773673|对我来说，从经典的ASP和ASP.Net到目前为止最大的优势是集成开发环境。能够右击函数调用并选择"Go+to+Definition“而不是去寻找函数实际实现的文件，这真是太好了。大大节省了时间。调用函数时的智能感知支持和类型安全也是一个福音。|1773674|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

To focus on the specific question ("benefits of Classic vs .Net"), there are only two things I can think of Classic does that .Net won't:

1) Includes. They just don't work like you expect in ASP.Net. Of course, ASP.Net provides much better ways of accomplishing the same thing, but it's still a bit of a loss and can make migrating an old site to .Net a pain.

2) ASP.Net won't go above the root folder for the application. Where I'm at we have a rather complex intranet that's still mostly classic ASP, with a smattering of .Net apps here and there as things are updated or new stuff added. It would be nice to be able to keep one copy of common code up fairly high in the folder hierarchy but still have each individual app isolated to it's own VD. But then, that's what source control is for, so it's not a big deal.

For me, the biggest advantage moving from Classic ASP and ASP.Net so far is the IDE. It's so nice to be able to right click on a function call and choose "Go to Definition" rather than having to dig around to find the file where the function is actually implemented. Huge time-saver. And intellisense support and type safety when calling functions is a boon as well.

blocks|key|1558522|text|这里的每个人都提出了正确的观点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1558523|我是一个典型的.NET开发人员，直到3年前我切换到ASP2.0。|1558524|我不能回到过去(即使我仍然需要修复一些经典的ASP站点)。|1558525|我很怀念记录集对象，数据中继器在快速显示数据方面很棒，但是数据集，虽然提供了很棒的功能，但当涉及到‘大’站点的性能时，它是非常糟糕的。公平地说，我一直在用经典的ASP中的数组来间接地处理数据集。我唯一一次使用数据集是为了我的电子商务网站篮子。我确实很想rs.movenext等等..。|1558526|FlySwat犯了我见过的许多开发人员犯下的最大错误之一。|1558527|是的，业务逻辑，面向对象等等…….NET带来的好处非常好(我不是100%25同意它的可伸缩性，但它的可扩展性绝对更好)，但是当您使用ASP.NET时，您仍然需要创建一个网站。忘记使用术语“应用程序”的胡言乱语吧。我遇到过许多伟大的.NET开发人员，他们构建了n层的面向对象站点，但他们并不真正理解构建web站点的独特性；例如状态，或者他们过度依赖Javascript的恼人的问题。大多数这些开发人员创建的MS类型的站点通常不符合W3C，不是跨浏览器友好的，并且永远不会优雅地降级。不，即使后台应用程序只与IE兼容，这也是不可接受的。|1558528|.NET也倾向于让简单的网站“变胖”。在许多方面，.NET是让WinForm开发人员开始构建网站(或者他们喜欢的web应用程序)的一种方式。问题是，这带来了一群开发人员，他们拥有不必担心国家、标准等的奢侈。|1558529|我仍然坚持认为，任何.NET站点都可以用传统的ASP构建，并且对最终用户来说运行速度更快(页面响应时间)。|1558530|...BUT虽然我对经典的.NET有着美好的回忆，但我可以在图像、加密、压缩、简单的web服务集成、适当的OO、像样的n层、可扩展性、etc...is等方面使用.NET。即使是简单地向web.config添加一行代码，告诉它在用户不接受cookie的情况下将sessionID写入查询字符串(这在传统的ASP中是一件痛苦的事情)这样愚蠢的事情也是很好的。|1558531|转到.NET，你不会后悔的，但一定要给自己一些时间(特别是如果你不了解OO+(继承、抽象、多态性和封装)。不要在传统的兼容模式下开始构建.NET站点，这只是一种做.NET的廉价方式，你最终仍然会使用经典的ASP实践。如果VBScript是你的主要开发语言，跳跃不会像MS或其他人让你相信的那样容易。|1558532|对我来说最重要的是，从我的经典ASP时代开始，我已经完成了基本的网站应用程序(;-))设计，这一点永远不应该在不同的语言之间改变。|1558533|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|14|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|15|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|16|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|17|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|W|$]]

Everyone here has made valid points.

I was a classic ASP developer until 3 yrs ago when I switched to .NET 2.0.

I couldn't go back (even though I do still have to fix a handful of classic ASP sites).

I do miss having a recordset object, data repeaters are great for displaying data quickly, but datasets, whilst offering wonderful functionality, are dame awful when it comes to performance on 'big' sites. In fairness I've been doing datasets in a roundabout way with Arrays in classic ASP. The only time I use datasets is for my e-commerce site baskets. I do miss rs.movenext, etc...

FlySwat has made one of the biggest mistakes that I see a lot of developers make.

Yes business logic, OO etc... that .NET brings is great (scalability I wouldn’t 100% agree with, but definitely more extensible), but when using ASP.NET you are still creating a WEB SITE. Forget this nonsense of using the terminology ‘application’. I have meet many great .NET developers who build n-tier, OO sites, but they have no real understanding of the uniqueness of building a web site; such as state, or the bloody annoying problem that they over rely on Javascript. Most of these developers build MS type sites which don't normally meet W3C, aren’t cross browser friendly and never gracefully degrade. And no it is not acceptable even for back office applications to be only compatible with IE.

.NET also tends to 'fatten' simple sites. .NET in many ways was a way of getting WinForm developers to start building web sites (or as they prefer, web apps.). The problem was that this brought with it a bunch of developers who had the luxuries not having to worry about state, standards, etc...

I still maintain that any .NET site can be built in classic ASP and run faster (page response times) for the end user....

...BUT though I have fond memories of classic ASP, what I can do with .NET in terms of imaging, encryption, compression, easy web service integration, proper OO, decent n-tier, extensibility, etc...is what gives .NET the advantage. Even silly things like simply adding one line of code to the web.config to tell it to write the sessionID to the querystring if the user doesn’t accept cookies (this was a pain in classic ASP) is great.

Move to .NET, you won’t regret it, but do give yourself sometime (particularly if you don’t know about OO (inheritance, abstraction, polymorphism and encapsulation). Don’t start building .NET sites in classic compatibility mode, it’s just a cheap way of doing .NET and you’ll still end up using classic ASP practises. If VBScript was your main development language, the jump is no were near as easy as MS or others would have you believe.

Most importantly for me is that I have carried across, from my classic ASP days, fundamental web site application (;-)) design and this should never change between languages.

blocks|key|1558613|text|我同意这里的每个人，除了一个人说跳过webforms，直接转到MVC。这是没有帮助的。Webforms对于数据库驱动的应用程序非常有用，这些应用程序做了大量的表格显示等。我在一些非常大的webforms应用程序上工作过，它工作得很好。MVC非常适合交互性更强的“Web2.0”类型的应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1558614|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I agree with everyone here except the one who said skip webforms and go straight to MVC. This is not helpful. Webforms is very useful for database-driven applications which do lots of table displays, etc. I have worked on some very large webforms applications and it works fine. MVC is good for more interactive "Web 2.0" type applications.

blocks|key|1558619|text|5+Reasons+You+Should+Take+a+Closer+Look+at+ASP.NET+MVC|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1558620|entityMap|0|LINK|mutability|MUTABLE|url|http://weblogs.asp.net/dwahlin/archive/2009/04/06/5-reasons-you-should-take-a-closer-look-at-asp-net-mvc.aspx^0|0|1I|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<h2><a href="http://weblogs.asp.net/dwahlin/archive/2009/04/06/5-reasons-you-should-take-a-closer-look-at-asp-net-mvc.aspx" rel="nofollow noreferrer">5 Reasons You Should Take a Closer Look at ASP.NET MVC</a></h2>

blocks|key|1558678|text|对我来说，我不得不说Classic+ASP开发起来很快，使用/上手都很简单，并不是太复杂，而且对大多数要求它的事情都很有能力。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1558679|以JScript/Javascript为主要语言的ASP代码非常非常有趣。VBScript是对脑力的浪费，我认为这就是Classic+ASP坏名声的原因。此外，它被认为很慢，但所有关于速度和用户数的文章都是基于10%2B上一年的服务器。我们在两台服务器上运行一个每天有60,000个用户的站点，CPU几乎不闪烁。现代服务器为您提供了更多的功能。|1558680|随着近年来Javascript的使用、设计和最佳实践的巨大飞跃，ASP+JScript编码器可以得到很多好东西，让生活变得更容易。我已经将Mootools移植到了服务器端，通过它，我们得到了大量的帮助、类模型、优秀的事件模型等等。ASP很有趣。更新:+Mootools现在有一个可以下载的服务器端版本(http://mootools.net/download)。|offset|length|1558681|ASP.net是超级强大的，但在学习曲线上有一个很大的坡度，当它有一个合适的时候，可以让你的整个网站瘫痪，对我来说最糟糕的是，似乎真的可以在房子里到处走动，完成最简单的事情。|1558682|我现在很享受使用这两个工具的乐趣，使用哪一个最适合这个差距。我有一个伟大的小CMS缓存和缩略图构建在.net中，我的ASP脚本使用。两全其美。|1558683|entityMap|0|LINK|mutability|MUTABLE|url|http://mootools.net/download^0|0|0|47|S|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$F|W|G|X|1|Y]]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

For me I'd have to say Classic ASP is quick to develop in, simple to use/pick up, not overly complicated and very capable of most things asked of it.

ASP with JScript/Javascript as the main language is really, really good fun to code with. VBScript is a waste of brain power and I think its that which gives Classic ASP its bad name. Plus its considered slow but all the articles about speed and number of users are based on 10+ year old servers. We run a site getting 60,000 users a day on two servers and the CPU barely flickers. Modern servers give you a lot more power to play with.

With the huge leaps forward in Javascript usage, designs and best practises in recent years the ASP JScript coder can get alot of goodies to make life even easier. I've ported Mootools to server-side and with that we get an load of wonderful helps, class model, excellent event model and so much more. ASP is great fun. UPDATE: Mootools now have a server-side build that you can download (<a href="http://mootools.net/download" rel="nofollow noreferrer">http://mootools.net/download</a>).

ASP.net is SUPER powerful but has a big ramp on the learning curve to do well, can bring your whole site down when it has one of its fits and worst for me can seem to really go around the houses to get the most simplest of things done.

I'm having alot of fun using both at the minute, using which ever one best fits the gap. I've a great little CMS Cacher and Thumbnailer build in .net which my ASP scripts use. Best of both worlds.

blocks|key|1558755|text|如果你在这一点上使用了经典的asp+(没有你的首席技术官的授权)，那么你需要去看一个心理医生。或者你是个受虐狂。或者作为撒旦教徒，在这种情况下，你会喜欢它，因为你会在地狱里！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1558756|严肃地说。对于web应用程序，使用WebForms。|1558757|对于轻量级、快速和肮脏的网站，请使用ASP.NET+MVC。|1558758|ASP的好处是你可以使用VB.NET，C#，Eiffel，Boo或PHP作为你的语言！对于PHP，请查看Phalanger...|1558759|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

If you use classic asp at this point (without a mandate from your CTO) then you need to see a shrink. or you are a masochist. Or as satanist, in which case, you'd like it cuz you'd be in hell! :p 

On a serious note... for web applications use WebForms. 

For light, quick and dirty websites, use ASP.NET MVC. 

Good thing about ASP is that you can use VB.NET, C#, Eiffel, Boo or PHP for your language! For PHP check out Phalanger...

blocks|key|1558812|text|因为我的报酬是创建解决方案而不是编写代码，所以我更喜欢ASP.NET而不是经典的ASP。虽然经典的ASP对于非常小、简单的站点仍然是实用的，但在编写更复杂的站点时，ASP.NET背后仍然有很大的力量。此外，即使使用ASP.NET，您仍然可以使用记事本自己编写.aspx文件，包括嵌入式vb或c#代码。Visual+Studio只提供了许多附加功能，从而消除了自己编写更多代码的需要。而且，正如我所说的，我不会因为写代码而得到报酬……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1558813|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Since I'm paid to create solutions and not to write code, I just prefer ASP.NET over classic ASP. While classic ASP is still practical for very small, simple sites, there's still a lot of power behind ASP.NET when writing a bit more complex sites. Besides, even with ASP.NET you could still just use Notepad to write the .aspx files yourself, including embedded vb or c# code. Visual Studio just provides a lot of additional functionality that takes away the need to write more code yourself.
And, as I said, I don't get paid for writing code...

blocks|key|1558869|text|我总是使用经典的ASP，它工作得很漂亮。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1558870|我尝试了几年的ASP.net，但对于大多数网站开发来说，它太复杂了。我的客户也不喜欢它，因为他们不能理解它。他们也喜欢知道他们不会被锁定在一个开发者身上。|1558871|ASP.NET不断变化，需要巨大的/持续的学习曲线才能保持最新。微软将主要语言转换为C#，这使得转换变得更加困难。|1558872|使用.net时，我的工作效率降到了极点，因为我总是在寻找如何做每件事的教程或示例。|1558873|Visual+Studio简直就是一只小猪。|1558874|PHP有一个丑陋的语法和太多不同的框架，这使得开发人员无法学习。在我看来，这只适用于有专职员工的内部网使用。|1558875|传统的ASP已经被锁定，并且像几年前一样完美地工作在今天。只需几个库文件，代码编写就像馅饼一样简单，互联网上的示例也是无限的。|1558876|vbscript写得很正确，但大多数人都做不到，它是干净、易读、高效的代码。我把客户端的事情留给了像jQuery这样的库，并且发现我的工作效率提高了许多倍。|1558877|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

I always use Classic ASP, it works beautifully. 

I tried ASP.net for a couple of years but it was too complex for most website development. My customers didn't like it either because they couldn't understand it. They also like knowing they are not locked into one developer.

ASP.NET keeps changing and requires enormous/constant learning curve to keep current. MS switched primary language to C# which made the transition just that much harder.

My productivity slowed to a crawl with .net because I was forever out looking for tutorials or examples of how to do everything. 

Visual Studio is pig sloooooow.

PHP has an ugly syntax and too many different frameworks which makes it impossible to learn for developer purposes. Good only for intranet use with dedicated staff, in my opinion.

Classic ASP is locked down and works perfectly today just as it did years ago. With a few library files, code writing is easy as pie and examples are unlimited on the internet.

Written correctly, which most folks don't, vbscript is clean readable, efficient code. I leave the client side stuff for libraries like jQuery and find I am many times more productive.

Having worked with Classic ASP for about 2 years now by creating a few 100 simple web forms I can't see a good reason for switching to .net; however, I'm not that versed in .net so I'm sure I could be missing a few things.

Some points that I often hear around work can be found here: <a href="http://www.packtpub.com/article/Classic-ASP" rel="noreferrer"><a href="http://www.packtpub.com/article/Classic-ASP" rel="noreferrer">http://www.packtpub.com/article/Classic-ASP</a></a> (not that I share all of these thoughts, but it's a good jumping off point)

I'm very interested to hear what others have to say on this matter.

Are there benefits to Classic ASP over ASP.net

集成开发环境

Visual Studio

身份验证

数据库

服务器

调试器

Django

jQuery

使用Classic ASP2年来，通过创建100个简单的web表单，我看不出有什么好的理由切换到.net；然而，我对.net不是很精通，所以我确信我可能会错过一些东西。我在工作中经常听到的一些观点可以在这里找到： (并不是我分享了所有这些想法，但这是一个很好的起点)我很有兴趣听听其他人对这件事的看法。

问与ASP.net相比，传统ASP有哪些优势
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问与ASP.net相比，传统ASP有哪些优势EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问与ASP.net相比，传统ASP有哪些优势
EN