ASP.NET 4与Visual Studio 2010 Web开发新特性概览

需积分: 3 183 浏览量更新于2024-07-29 收藏 1.14MB PDF 举报

ASP.NET 4与Visual Studio 2010 Web Development Overview 在本指南中，我们将深入探讨ASP.NET 4和Visual Studio 2010联合带来的众多新特性和改进，这些特性为Web开发人员提供了更强大的工具和性能优化。以下是部分内容的详细解读： 1. **核心服务**（Core Services）: ASP.NET 4引入了新的服务，如依赖注入和通用中间件，使得应用程序的结构更加模块化和可维护。这些服务简化了开发者的工作流程，提高了代码的可重用性。 2. **Web.config文件重构**（Web.config File Refactoring）: 新版的配置文件允许更灵活、简洁的配置管理，减少了冗余代码，提升了部署效率。通过XML Schema Validation和命名空间管理，开发者可以更轻松地管理和扩展应用程序设置。 3. **可扩展的输出缓存**（Extensible Output Caching）: ASP.NET 4引入了对输出缓存的增强，使得开发者可以根据应用需求动态调整缓存策略，提高网站性能。 4. **自动启动Web应用程序**（Auto-Start Web Applications）: 通过新的启动机制，应用程序可以在服务器启动时自动初始化，避免了不必要的延迟，提升用户体验。 5. **页面永久重定向**（Permanently Redirecting a Page）: 改进后的重定向功能使得开发者能够更精确地控制页面重定向，提升了URL管理的灵活性。 6. **会话状态管理**（Shrinking Session State）: 新版本提供了对会话状态大小的控制，有助于优化内存使用和性能，特别是对于高并发环境。 7. **URL范围扩展**（Expanding the Range of Allowable URLs）: 更宽泛的URL支持使得开发者能处理更复杂的路径，提高网站的兼容性和易用性。 8. **请求验证扩展**（Extensible Request Validation）: 开发者可以根据需要自定义请求验证规则，确保输入数据的安全性。 9. **对象缓存和扩展性**（Object Caching and Object Caching Extensibility）: 对象缓存功能得到了增强，允许开发者更好地管理和定制缓存策略，提高响应速度。 10. **HTML、URL和HTTP头编码扩展**（Extensible HTML, URL, and HTTP Header Encoding）: 更高级的编码选项支持多语言和国际化需求，提升用户体验。 11. **单工作进程下的应用程序性能监控**（Performance Monitoring for Individual Applications in a Single Worker Process）: 开发者可以更深入地了解应用程序在服务器中的运行情况，进行有针对性的性能优化。 12. **多目标编译**（Multi-Targeting）: Visual Studio 2010支持跨平台和跨版本的开发，方便开发者构建兼容多种环境的应用。 13. **Ajax技术的集成**（Ajax）: ASP.NET 4与jQuery的集成使得异步数据通信更加简便，提升了Web应用的交互性和响应速度。 14. **内容分发网络支持**（Content Delivery Network Support）: 集成了CDN的支持，帮助开发者将静态内容分发到全球各地，加快用户的加载速度。 15. **Script Manager中的明确脚本**（Script Manager Explicit Scripts）: 提供了更好的脚本管理，使开发者能更精准地控制脚本的加载和执行。 16. **WebForms更新**（WebForms）: 新版WebForms引入了增强的特性，如更灵活的布局、控件增强等，提升了用户界面设计的效率。 17. **元标签设置**（Setting Meta Tags）: 开发者可以通过`.MetaKeywords`和`.MetaDescription`属性轻松设置页面元数据，利于搜索引擎优化。 18. **控件状态启用**（Enabling ViewState for Individual Controls）: 控件级别的 ViewState 可以根据需要启用或禁用，提高性能的同时保留必要的状态信息。 19. **浏览器能力的调整**（Changesto Browser Capabilities）: 新版对浏览器兼容性进行了优化，确保应用能在主流浏览器上正常运行。 20. **ASP.NET 4路由系统**（Routing in ASP.NET 4）: 强大的路由机制使得URL结构更加清晰，易于管理，提升了SEO友好度。 21. **客户端ID设置**（Setting ClientIDs）: 更灵活的客户端ID生成方式，有助于避免ID冲突，提高前端代码的可维护性。 22. **表格行选择持久化**（Persisting Row Selection in Data）: 在数据绑定控件中，用户的选择可以被持久化，改善了用户体验。 ASP.NET 4与Visual Studio 2010的结合为Web开发带来了显著的提升，不仅在性能、安全性、用户体验上有所优化，还为开发者提供了更多的自定义选项和扩展能力。学习和掌握这些新特性和工具，无疑将极大地推动您的Web开发项目向前发展。

ASP.NET 4 and Visual Studio 2010 Web Development Overview 11

//For this example we want the cache entry to be automatically expired

//if the contents on disk change. A HostFileChangeMonitor provides

//this functionality.

policy.ChangeMonitors.Add(new HostFileChangeMonitor(filePaths));

//Fetch the file's contents

fileContents = File.ReadAllText("c:\\data.txt");

//And then store the file's contents in the cache

cache.Set("filecontents", fileContents, policy);

}

MessageBox.Show(fileContents);

}

Extensible HTML, URL, and HTTP Header Encoding

In ASP.NET 4, you can create custom encoding routines for the following common text-encoding tasks:

HTML encoding.

URL encoding.

HTML attribute encoding.

Encoding outbound HTTP headers.

You can create a custom encoder by deriving from the new System.Web.Util.HttpEncoder type and then

configuring ASP.NET to use the custom type in the httpRuntime section of the Web.config file, as shown

in the following example:

After a custom encoder has been configured, ASP.NET automatically calls the custom encoding

implementation whenever public encoding methods of the System.Web.HttpUtility or

System.Web.HttpServerUtility classes are called. This lets one part of a Web development team create a

custom encoder that implements aggressive character encoding, while the rest of the Web development

team continues to use the public ASP.NET encoding APIs. By centrally configuring a custom encoder in

the httpRuntime element, you are guaranteed that all text-encoding calls from the public ASP.NET

encoding APIs are routed through the custom encoder.

ASP.NET 4 and Visual Studio 2010 Web Development Overview 12

Performance Monitoring for Individual Applications in a Single Worker Process

In order to increase the number of Web sites that can be hosted on a single server, many hosters run

multiple ASP.NET applications in a single worker process. However, if multiple applications use a single

shared worker process, it is difficult for server administrators to identify an individual application that is

experiencing problems.

ASP.NET 4 leverages new resource-monitoring functionality introduced by the CLR. To enable this

functionality, you can add the following XML configuration snippet to the aspnet.config configuration

file.

<?xml version="1.0" encoding="UTF-8" ?>

</runtime>

</configuration>

Note The aspnet.config file is in the directory where the .NET Framework is installed. It is not the

Web.config file.

When the appDomainResourceMonitoring feature has been enabled, two new performance counters

are available in the "ASP.NET Applications" performance category: % Managed Processor Time and

Managed Memory Used. Both of these performance counters use the new CLR application-domain

resource management feature to track estimated CPU time and managed memory utilization of

individual ASP.NET applications. As a result, with ASP.NET 4, administrators now have a more granular

view into the resource consumption of individual applications running in a single worker process.

Multi-Targeting

You can create an application that targets a specific version of the .NET Framework. In ASP.NET 4, a new

attribute in the compilation element of the Web.config file lets you target the .NET Framework 4 and

later. If you explicitly target the .NET Framework 4, and if you include optional elements in the

Web.config file such as the entries for system.codedom, these elements must be correct for the .NET

Framework 4. (If you do not explicitly target the .NET Framework 4, the target framework is inferred

from the lack of an entry in the Web.config file.)

The following example shows the use of the targetFramework attribute in the compilation element of

the Web.config file.

ASP.NET 4 and Visual Studio 2010 Web Development Overview 13

Note the following about targeting a specific version of the .NET Framework:

In a .NET Framework 4 application pool, the ASP.NET build system assumes the .NET Framework 4 as

a target if the Web.config file does not include the targetFramework attribute or if the Web.config

file is missing. (You might have to make coding changes to your application to make it run under the

.NET Framework 4.)

If you do include the targetFramework attribute, and if the system.codeDom element is defined in

the Web.config file, this file must contain the correct entries for the .NET Framework 4.

If you are using the aspnet_compiler command to precompile your application (such as in a build

environment), you must use the correct version of the aspnet_compiler command for the target

framework. Use the compiler that shipped with the .NET Framework 2.0

(%WINDIR%\Microsoft.NET\Framework\v2.0.50727) to compile for the .NET Framework 3.5 and

earlier versions. Use the compiler that ships with the .NET Framework 4 to compile applications

created using that framework or using later versions.

At run time, the compiler uses the latest framework assemblies that are installed on the computer

(and therefore in the GAC). If an update is made later to the framework (for example, a hypothetical

version 4.1 is installed), you will be able to use features in the newer version of the framework even

though the targetFramework attribute targets a lower version (such as 4.0). (However, at design

time in Visual Studio 2010 or when you use the aspnet_compiler command, using newer features of

the framework will cause compiler errors).

Ajax

jQuery Included with Web Forms and MVC

The Visual Studio templates for both Web Forms and MVC include the open-source jQuery library. When

you create a new website or project, a Scripts folder containing the following 3 files is created:

jQuery-1.4.1.js – The human-readable, unminified version of the jQuery library.

jQuery-14.1.min.js – The minified version of the jQuery library.

jQuery-1.4.1-vsdoc.js – The Intellisense documentation file for the jQuery library.

Include the unminified version of jQuery while developing an application. Include the minified version of

jQuery for production applications.

For example, the following Web Forms page illustrates how you can use jQuery to change the

background color of ASP.NET TextBox controls to yellow when they have focus.

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="ShowjQuery.aspx.cs"

Inherits="ShowjQuery" %>

剩余65页未读，继续阅读

vincent081

粉丝: 0
资源: 1

ASP.NET 4与Visual Studio 2010 Web开发新特性概览

Visual Studio 2008 Web开发详解及新特性

Visual Studio 2010与ASP.NET 4.0新特性解析

Visual Studio 2012 深入探索与实践

ASP_NET_4_and_Visual_Studio_2010_Web_Development_Overview.pdf

Microsoft - Team Development with Visual Studio.NET and Visual SourceSafe

Introducing Net 4.0 With Visual Studio 2010.pdf

Visual Studio 2010 and .NET 4 Six-in-One part1

[Wrox] ASP.NET 3.5 Enterprise Application Development with Visual Studio 2008

Web Deployment Projects Visual Studio® 2005

Beginning ASP.NET for Visual Studio 2015

最新资源