ASP.NET MVC 4：从衰落到转型与成长

需积分: 9 200 浏览量更新于2024-07-21 收藏 9.83MB PDF 举报

"Apress.ASP.NET.MVC.4.Recipes"是一本针对ASP.NET MVC 4的实用指南，它在探讨现代Web应用程序开发的重要性和转型过程中，着重讲解了ASP.NET MVC框架的崛起与优势。随着ASP.NET Web Forms的逐渐衰退，MVC框架的增长势头强劲，特别是在顶级流行网站中的应用量增长超过110%。本书涵盖了从入门到高级的主题，包括设置开发环境、Visual Studio 2012的概述、利用内置模板、应用架构设计、异步编程、测试驱动开发、Web Forms向MVC的迁移、使用jQuery、Knockout.js和Web API创建现代用户界面，以及移动、社交和云计算技术的应用。第1章"现代Web应用程序的需求"讨论了为什么需要转向更为现代和灵活的Web开发方式，以适应不断变化的技术趋势。第二章深入解析ASP.NET MVC，介绍了其核心概念和设计理念，对于初次接触或希望提升技能的开发者来说是不可或缺的基础内容。第三章指导读者如何配置和准备开发环境，确保能够顺利进行MVC项目的开发。第四章专门介绍Visual Studio 2012，一个强大的集成开发环境，用于构建、调试和部署ASP.NET MVC应用。第五章关注预置模板的高效使用，帮助开发者快速搭建项目骨架，并优化开发流程。第六章阐述了如何设计和组织应用架构，以实现模块化和可扩展性。第七章详细探讨解决方案设计，强调代码结构和版本管理的重要性。第八章深入研究异步编程，这是现代Web开发中的关键技能，能提升用户体验和性能。第九章引入测试驱动开发（TDD），确保代码质量和稳定性。第十章则着重于Web Forms与MVC的迁移策略，帮助开发者平稳过渡到更受欢迎的MVC框架。第十一章展示了如何利用前端库如jQuery、Knockout.js以及Web API来打造动态且响应式的用户界面，提高交互体验。最后一章关注移动、社交和云技术，使读者了解如何将这些前沿技术融入到ASP.NET MVC应用中，以实现全面的Web服务和兼容性。 "Apress.ASP.NET.MVC.4.Recipes"是一本实战性强，内容丰富的教材，不仅适合初学者系统学习ASP.NET MVC，也适合有一定经验的开发者在技术演进中寻求进阶指导。通过阅读本书，开发者将能更好地应对现代Web开发挑战，跟上技术的步伐。

CHAPTER 1 ■ THE NEED FOR MODERN WEB APPLICATIONS

9. On the Service Accounts screen, in most cases, you can accept the default settings. This

will create a service account NT Service\MSSQLServer with an Automatic Startup type for

the SQL Server Database engine service. The SQL Server Browser service is disabled by

default. It is recommended that you keep this setting for security reasons.

10. On the Database Engine Configuration page, it is recommended that you use the default

setting of Windows Authentication Mode, which is more secure than Mixed Mode. You

should also add yourself to the SQL Server administrators account by clicking the Add

Current User button. On the Data Directories, adjust the settings as appropriate for your

machine. Click Next to continue.

11. On the Error Reporting screen, click Next.

12. At this point, installation will proceed. It will take between 5 and 20 minutes for the

installation to complete, depending on the speed of your computer.

13. On the Complete screen, click the Close button.

Installing the Sample Database

The following steps explain how to install the sample database.

1. Download the sample database backup file from the Downloads tab on the Apress web site

(www.apress.com/9781430247739).

2. The database backup file is available under the Shared folder. Unzip the file to a location

on your local hard disk.

3. Open SQL Server Management Studio. This is a tool that should have been installed with

the SQL Server 2012 installation.

4. When prompted to connect to a server, your local machine should be selected by default

and Windows Authentication should be selected. Click OK to connect.

5. In the Microsoft SQL Server Management Studio application, right-click the Databases

node in the Object Explorer and select Restore Database.

6. Under Source in the Restore Database window, select Device, and then click the

Ellipse button.

7. In the Select Backup Devices window, select File as the Backup Media Type, and then click

the Add button.

8. Browse to the location where you unzipped the database backup file, and then select

Ch7SharedDatabase.bak and then click OK.

9. Click OK in the Select Backup Devices window.

10. In the Restore Database window, the database name should be set to Ch7SharedDatabase

and the last full backup should be checked in the Backup Sets To Restore list. Click the OK

button to begin the restore process.

11. When completed, a message should state that the database was restored successfully.

Click the OK button to dismiss the message.

12. Confirm that the database exists and is accessible by expanding the Databases node in the

Microsoft SQL Server Management Studio Object Explorer.

Chapter 2

Understanding ASP.NET MVC

2-1. Understanding the Microsoft Web Development Ecosystem

Problem

You are new to the Microsoft platform and need to know how to get started. You are confused by the myriad of product

offerings. You don’t know if you should be using WebMatrix, LightSwitch, ASP.NET MVC, ASP.NET Web Forms,

ASP.NET Web Pages, Napa, or Silverlight. You would like to understand all these tools and determine which tool

you should learn more about.

Solution

The ever-growing selection of developer products from Microsoft has grown substantially over the past few years.

The current list of products has become confusing, even for experienced Microsoft developers. To clear up this

confusion, it is helpful to have a general understanding of the platforms, which include servers, productivity suites,

programming frameworks, and languages. Once you understand the platforms and the types of applications that you

can create on them, you can then explore the development tools to get an understanding of how each is applied to

the ecosystem.

How It Works

The Microsoft web development ecosystem works by leveraging the building blocks on the Windows operating

system. These building blocks include the Windows APIs (Win32), Component Object Model (COM), Object Linking

and Embedding (OLE), Component Services (COM+), and the Microsoft .NET Framework.

Built from these foundational layers is Microsoft’s Web Server Internet Information Services (IIS). IIS 7, which

was a complete rewrite of past versions of the web server, provides a flexible extensibility model that divides its

functionality into a collection of loosely-coupled modules.

This architecture allows any component to be replaced by a custom version if needed and allows additional

functionality to be created by both Microsoft and third-party independent software vendors. IIS 7 ships with more

than 40 modules, which include authentication, response compression, configuration, and application frameworks

such as ASP.NET. They also provide backward compatibility with older versions of IIS, which allows older application

frameworks such as Classic ASP.

In addition to application frameworks developed by Microsoft, IIS supports many third-party and open-source

web platforms, including PHP, CGI, Perl, Node.js, Ruby on Rails, and Java development technologies such as J2EE.

Chapter 2 ■ Understanding asp.net MVC

Microsoft Development Platforms and Frameworks

This section introduces each of the major platforms and frameworks that have been developed by Microsoft and run

on IIS.

Classic ASP

Active Server Pages (ASP) was a Microsoft web development framework released in 1998 as part of the Windows NT 4.0

Option Pack. It was extremely successful, and even though it has been superseded by ASP.NET, it continues to

power hundreds of thousands of web sites. It can still be installed all versions of Windows Server, including Windows

Server 2012.

ASP was also implemented on Unix and Linux systems by ChiliSoft (later acquired by Sun and now part of

Oracle).

Classic ASP’s popularity was driven by the fact that it was very simple and easy to learn. It allowed developers to

use either VBScript or JavaScript as the programming language.

The main issue with it is was that it mixed together business logic with presentation and often led to applications

that became impossible to maintain. It was also very difficult to debug. Many teams attempted to remedy ASP’s

shortcomings by putting the business logic into COM components written in C++ or VB. This practice was later

officially recommended by Microsoft in what was called Windows DNA.

Ultimately, the rise of Java technologies and the growing complexity of business requirements led to the

development of Microsoft .NET and ASP.NET, which replaced Classic ASP.

Although Classic ASP is still officially supported on the Windows Server platform, I would not recommend using

it for new projects.

ASP.NET Web Forms

ASP.NET Web Forms, which was first released in 2002, is now in its seventh version. It has been the primary web

development technology used on the Microsoft platform for more than ten years. Web Forms abstracts the web and

uses a programming model that is very similar to programming Windows Forms. It follows a model where a developer

would design a screen by dragging controls such as text boxes and drop-down lists to the design surface, and then

double-clicking the control to create an event handler on a code-behind page. For example, double-clicking on a

button would create an OnClick event handler where you would put your code to be executed when the button

was clicked.

The main benefits of Web Forms is that it was easy to learn for VB programmers looking to move away from fat,

client programming and start building web applications. It also saved developers time with features such as form

validation controls and web site security.

The drawbacks are that is was designed for the web of 2002, when it was acceptable for every UI manipulation to

result in a post back to the server. They remedied this with some success in 2008 with the release of ASP.NET Ajax, but

developers who attempt to create rich user interfaces may find themselves fighting the framework.

Web Forms may still be ideal for teams that need to rapidly put together a small application that does not need

a highly sophisticated user interface. However, as technologies such as SharePoint and LightSwitch become more

sophisticated, and tools like business process management systems become more prevalent, the need for developers

to hand-develop these types of systems are diminishing.

ASP.NET MVC

ASP.NET MVC was first released in March 2009. It shares a common infrastructure with ASP.NET Web Forms, but

breaks away from the server control, drag-and-drop paradigm of the web forms world and provides a more natural

model for creating Ajax-driven, rich end-user experiences.

A detailed comparison between ASP.NET Web Forms and ASP.NET MVC is provided in Recipe 2-5.

Chapter 2 ■ Understanding asp.net MVC

ASP.NET MVC is well suited for most web applications, and perhaps the paradigm of choice for all new

development. ASP.NET MVC requires that the developer invest time into understanding the Model View Controller

(MVC) pattern. Compared to some of Microsoft’s other frameworks, ASP.NET MVC may not be as easy for

inexperienced developers to learn.

ASP.NET Web Pages

ASP.NET Web Pages is a simple web development framework that provides a mechanism for creating custom web

applications with the WebMatrix IDE. It shares some underpinnings with ASP.NET MVC, including page routing and

the Razor view engine. While it is possible to create sophisticated applications using ASP.NET web pages, it is less

suitable for enterprise scale than ASP.NET MVC.

It may be ideal for experienced developers looking to create a simple application. For example, let’s say that you

need to create a web site for your softball team and would like to expose a database of batting averages. The simplicity

of WebMatrix allows you to do this faster than if you did the same application using MVC in Visual Studio. ASP.NET

Web Pages is less ideal for a team of developers working on a large project.

For enterprise developers, ASP.NET Web Pages and Web Matrix can be a great prototyping tool. Its rapid

application development environment allows you to quickly put together a demo and deploy it to a staging

server where it can be demonstrated to end users. The project can later be ported into Visual Studio and the full

MVC Framework, where you can apply enterprise development best practices and generate unit tests and other

recommended artifacts.

LightSwitch

LightSwitch is a RAD (rapid application development) tool that simplifies the creation of data entry–centric

applications. The initial release of LightSwitch used Silverlight to create the end-user experience. It exploited

Silverlight’s rich data-binding capabilities to create data-driven applications with minimal or no coding. LightSwitch

applications can be run either as a browser Silverlight application or as an out-of-browser application that runs on the

desktop. The latest version supports project output in HTML5 as well as Silverlight.

LightSwitch is a good solution for very simple applications. It has several major limitations, such as the inability

to support forms that need to update data from multiple database tables, which prevent it from being used for

anything other than trivial “peak and poke” applications.

Silverlight

Silverlight is a rich Internet application (RIA) tool that competes with the Adobe Flash plug-in. It is used primarily for

creating rich media streaming experiences by web sites such as Netflix.

Even though Microsoft has pledged to continue supporting Silverlight until 2021, Microsoft’s RIA strategy has

shifted to HTML5. Silverlight still has some advantages over HTML, such as the ability to run on legacy enterprise

desktops that have standardized on browsers such as Internet Explorer 7, which does not support HTML5 and has

poor JavaScript performance. It also is superior to HTML5 in that it can deliver richer streaming experiences with

an extensible codec framework and support for 3D graphics. Silverlight can run outside the browser and be granted

permission to access the local file system.

I recommend that architects and tech leads avoid using Silverlight for new applications. If possible, they

should either opt for an Ajax/HTML5 application or consider using a native Windows technology such as Windows

Presentation Foundation (WPF). If Silverlight is used, I recommend an “islands of richness” model over a full-

browser-window Silverlight application. An example of “islands of richness” is a Silverlight-based media player that

allows playback of Digital Rights Management (DRM)–protected content. In a full-browser Silverlight application, the

entire user experience is created in Silverlight.

剩余618页未读，继续阅读

ninght301

粉丝: 0
资源: 1

ASP.NET MVC 4：从衰落到转型与成长

Apress.Pro.ASP.NET.MVC.2.Framework

Apress.ASP.NET.MVC.4.Recipes.Feb.2013

Apress.Pro.ASP.NET.MVC.3.Framework

关于springboot的英文文献

帮我找一下可以写再javaweb毕设里的英文参考文献

spring boot项目英文文献

列举几个SpringBoot相关的技术文献,以文献引用的格式展示

javascript相关外文文献

springboot的参考文献

springboot框架外文参考文献列表

最新资源