blocks|key|1460331|text|我会选择ASP.MVC而不是经典的ASP.NET。传统ASP的问题在于对它的支持程度。使用MVC，您可以了解web+get/post和状态管理，同时获得使用您最喜欢的OO语言的优势。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1460332|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'd pick ASP.NET MVC over classic ASP. The problem with classic ASP is the support level for it. With MVC, you learn both about web get/post and state management, while at the same time getting the advantage of using your favorite OO language.

blocks|key|1675853|text|我想说的是，不要先学习经典的ASP，然后学习ASP.NET，因为经典的ASP已经死了。或者说应该是。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1675854|为什么不学习ASP.NET+(MVC和WebForms)，同时也要涉足PHP。查看PHP将帮助开发人员了解在较低的抽象级别工作是什么感觉。|1675855|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|$]]

I would say don't learn classic ASP and then ASP.NET. Classic ASP is dead. Or should be.

Why not learn ASP.NET (MVC and WebForms) while also dabbling in PHP. Looking at PHP would help a developer get a sense of what its like working at a lower abstraction level.

blocks|key|1460521|text|我要说的是，大多数新的web开发人员在最初学习HTTP时会更好，特别是不要用经典的ASP或ASP.NET把事情搞混。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1460522|一旦他们掌握了基础知识，我建议直接转向ASP.NET和一种编译/面向对象的编码语言。|1460523|虽然传统的ASP更加紧凑和专注(需要掌握的对象较少)，但不幸的是，使用它编写的大多数代码都是用VB-Script编写的。|1460524|我所见过的最糟糕的代码是用VB-script编写的经典ASP网站。虽然用VB-Script编写可维护和清晰的代码可能是可能的，但该语言本身似乎几乎鼓励完全相反的做法。|1460525|此外，听起来HTTP对于您的环境来说是一个更好的选择，因为它对开发人员“隐藏”了更少的ASP.NET。对于某些类型的应用程序，它是比ASP.NET+Web+Forms更好的选择。|1460526|总而言之:跳过经典的ASP，避免它可能带来的所有坏习惯和问题。|1460527|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

I'd say most new web developers would be better off initially learning about HTTP specifically without muddying things with either classic ASP or ASP.NET.

Once they have the fundamentals, then I'd suggest moving straight to ASP.NET and a compiled/object oriented coding language. 

While classic ASP is more compact and focused (smaller group of objects to grasp), most code written using it is unfortunately in VB-Script.

Some of the most atrocious code I've ever seen was classic ASP web sites in VB-script. While it is probably possible to write maintainable and clear code in VB-Script, the language itself seems to almost encourage the complete opposite.

Also, it sounds like ASP.NET MVC would be a better choice for your environment as it "hides" less about HTTP from the developer. For certain types of application it is a better choice then ASP.NET Web Forms.

In summary: skip the classic ASP and avoid all of the bad habits and problems that it can introduce.

blocks|key|1460385|text|从经典ASP开始不会有什么坏处，但我不认为这是值得的，因为只要花一点努力，你就可以理解Webforms是从你那里抽象出来的。如果你想两全其美，就从ASP.NET+MVC开始吧。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1460386|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|$]]

It wouldn't hurt to start with Classic ASP, but I don't think it would be worth it since with a little effort you can understand what Webforms is abstracting away from you. If you want the best of both worlds, start with ASP.NET MVC.

blocks|key|1460891|text|这相当于说这样的话：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1460892|“在学习C%2B%2B之前，您必须先学习pascal！”|1460893|您正在比较两种不同的语言和平台。|1460894|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

It's the equivalent argument of saying something like:

"You must learn pascal before you learn C++!"

You're comparing 2 different languages &amp; platforms.

blocks|key|1676033|text|我同意其他人的观点，学习HTTP请求/响应模型是关键。我还注意到许多.NET开发人员不理解HTTP模型。我是用ASP学习的，但.NET+WebForms让开发人员很容易不需要知道。所以我同意HTTP是一个既能做.NET又能学习HTTP模型的好方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1676034|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 others here that learning the HTTP request/response model is the key. I have also noticed that many .NET developers don't understand the HTTP model. I learned it using ASP, but .NET WebForms makes it easy for developers to not need to know it. So I agree that ASP.NET MVC would a great way to do both .NET and learn the HTTP model.

blocks|key|1676305|text|开始使用ASP几乎没有什么价值。如果你当时是一名ASP程序员，那么你可以欣赏ASP.NET中的一些概念。IIS7和Visual+Studio的更新版本对ASP并不是很友好，这意味着作为一个新的程序员学习它确实比它的价值更麻烦。首先，我说的是最新的内容，因为这是每个人都在做的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1676306|此外，面向解决方案的语言应该是次要的。在一天结束的时候，你需要交付一些能让客户满意的东西。|1676307|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|$]]

There is very little value in starting out with ASP. If you were an ASP programmer back in the day then you can appreciate some of the concepts that have carried on into ASP.NET. The fact that IIS 7 and newer versions of Visual Studio are not really that ASP friendly means that learning it as a new programmer is really more hassle than its worth. Start with what's current is what I say because its what everyone's doing. 

Also, be solution oriented - language should be secondary. At the end of the day you need to deliver something that works which makes the customer happy.

blocks|key|1460411|text|两种语言都有各自的advantages.Though，我同意“Haacked”和“John+Sheehan”的回答。每个人都会有自己的观点。所以最好开始学习你感兴趣的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1460412|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|$]]

Both languages have their individual advantages.Though, I agree with reply by 'Haacked' and 'John Sheehan' both. Every one will have their individual opinions. So better start learning in which you are interested.

blocks|key|1461306|text|我认为，你需要考虑的远不止国家管理，而是首先考虑实施经典学习asp的其他影响。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1461307|而不是学习经典的ASP，相反，确保您的开发人员将“状态管理”作为其培训过程的一部分。所有好的培训材料都将包括状态管理部分。|1461308|您可能会冒着在经典的ASP范例中思考并试图将默认设计模式应用于ASP.net的风险。而不是充分利用ASP.net的平台和技术。|1461309|话虽如此，我已经在ASP.net上开发了很多年了。我目前正在维护企业级的经典ASP系统。了解这些系统背后的框架是如何在ASP.net之前开发的，这是非常有价值的，并改进了我的ASP.net。|1461310|学习另一种语言总是有价值的:最近我用objective-C开发了一个iPhone应用程序，它让我更好地理解了MVC模式(XCode中的默认模式)-所以从长远来看，这将提高我的ASP.net。|1461311|尽管查看企业系统将是有价值的，但我不认为仅仅为了状态管理等目的而涉足经典的ASP+(即小的一次性页面)是值得的，而且可能会产生有害的影响。相反，要花时间“好好”学习ASP.net+(即包括状态管理)。|1461312|注：我发现不把这变成一场经典的ASP+/+ASP.net辩论是很棘手的。取而代之的是集中精力学习。|1461313|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

I think you need to be thinking far further than state management and instead be thinking of the other implications of imposing learning classic asp first. 

Rather than learning classic ASP, instead ensure your developers have "state management" as part of their training process. All good training material will include a state management section.

You may run the risk of thinking in the classic ASP paradigm and attempting to apply a defunt design pattern to ASP.net. Instead of making best use of ASP.net's platform and technology.

Having said that I have been developing in ASP.net for a number of years. I am currently maintaining enterprise grade classic ASP systems. Having the knowledge of how the frameworks behind these systems were developed pre-ASP.net is very valuable and HAS improved my ASP.net. 

Learning an alternative language is always valuable: Recently I developed an iPhone app in objective-C, it has given me a better understanding of the MVC pattern (the defualt paradigm in XCode) - so will improve my ASP.net in the long run.

Although looking at enterprise systems will be valuable, I do not think just dabbling in classic ASP (i.e. small one-off pages) for the purpose of state management etc is worthwhile and may have detrimental effects. Instead invest time in learning ASP.net "well" (i.e. include state management).

n.b. I have found it tricky not to turn this into a classic ASP / ASP.net debate. Instead tried to concentrate on the learning.

blocks|key|1675730|text|你并不是真的学习ASP.NET，你会学一门语言，比如C#或VB.NET。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1675731|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|$]]

You don't really learn ASP.NET, you'll learn a language such as C# or VB.NET. But yes .NET > !.NET

blocks|key|1461016|text|为什么你要学习经典的ASP呢？它已经死了；没有新的工作在里面做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1461017|如果你想学习一种像web一样工作的编程模型(+Asp.net+webforms做不到的，它是对windows窗体的漏洞百出的模仿)，有像ASP.Net+MVC这样的现代模型。|1461018|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|$]]

Why you should learn classic ASP at all? It is dead; no new work is done in it. 

If you want to learn a programming model that works the way that the web works (Which Asp.net webforms does not, it is a leaky imitation of windows forms), there are modern models like ASP.Net MVC.

blocks|key|1461239|text|首先通过编写静态页面来学习基础知识，并了解基本的HTTP请求/响应模型。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1461240|然后，转到使用服务器端技术。如果你的脑海中还没有充斥着Asp.Net+webforms模型，我建议你使用Asp.Net+Mvc，但是要理解其中的权衡。最有可能的是，你迟早要处理webforms，因为大多数.Net+brownfield+webapps都在使用该平台。|1461241|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|$]]

Learn the fundamentals first by writing static pages and understand the basic HTTP request/response model. 
Then, move on to using server side technology. I'd recommend with Asp.Net Mvc if your head is not already filled with Asp.Net webforms model, however understand the tradeoff. Most likely you will have to deal with webforms sooner or later as majority .Net brownfield webapps are using that platform.

blocks|key|1676192|text|我建议直接使用ASP.Net。ASP是一项如此古老的技术，他们将不得不学习太多关于常见地方的工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1676193|我也会直接选择ASP.Net而不是MVC，因为MVC到底有多有价值还没有定论(至少对我来说)。它使开发人员失去了很多控制权。|1676194|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|$]]

I would recommend just going with ASP.Net. ASP is so old a technology that they will have to learn so many work arounds to things that are common place.

I would also go with straight ASP.Net over MVC as the jury is still out (for me anyway) on how valuable MVC really is. It takes a lot of control away from the developer.

My colleague here argues that new programmers must learn ASP first, before they learn ASP.Net. 

I seem to agree with him as most new programmers who start with ASP.Net do not understand web get, post and state management :(

Which is best to learn web programming Classic ASP or ASP.Net?

Should new programmers learn ASP first or ASP.Net?

Visual Studio

服务器

我的同事认为，在学习ASP.Net之前，新程序员必须先学习ASP。我似乎同意他的观点，因为大多数从ASP.Net开始的新程序员都不了解web get、post和状态管理：哪一个是最好的学习网页编程经典的ASP和ASP.Net？

问新程序员应该先学习ASP还是ASP.Net？
EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问新程序员应该先学习ASP还是ASP.Net？EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问新程序员应该先学习ASP还是ASP.Net？
EN