Recommended in this week's ASP. NET technical article [04/22-04/28]

 

Summary

I almost forgot about this weekend ...... There are 7 articles in this issueArticle:

1. JavaScript document comment format
2. Support for JavaScript smart sensing in Visual Studio orcas
3. Break down configuration files in ASP. NET
4. Move viewstate from client to server
5. Miscellaneous concepts in. Net: Part 1
6. Select mock object framework
7. Web applications using AjaxProgramLayered

 

[1]The format for JavaScript Doc comments(Format of JavaScript document comment)

XML-Format documents are an infrastructure of Visual Studio's smart sensing function. In the next-generation Visual Studio Orcas, the smart perception of JavaScript also relies on some XML annotation documents in specific formats.

This article briefly introduces the rules for using such annotations in Javascript. For example, the annotation rules for parameters are as follows:

 
<Param Name= "Parametername"
 

Maybenull= "True | false" Optional= "True | false"
 

 
Type= "Parametertype" Parameterarray= "True | false"
 

 
Integer= "True | false" Domelement= "True | false"
 

 
Elementtype= "Arrayelementtype" Elementinteger= "True | false"
 

 
Elementdomelement= "True | false" Elementmaybenull= "True | false"
 

Locid= "Descriptionid">Description</Param>
 

The comment rules for return values are as follows:

<Returns
 

 
Type= "Valuetype" Integer= "True | false" Domelement= "True | false"
 

 
Maybenull= "True | false" Elementtype= "Arrayelementtype"
 

 
Elementinteger= "True | false" Elementdomelement= "True | false"
 

 
Elementmaybenull= "True | false"
 

Locid= "Descriptionid">Description</Param>
 

 

[2]Javascript intelliisense in Visual Studio "orcas"(Support for JavaScript intelligent sensing in Visual Studio orcas)

Scott carries forward his consistent "introduction, summarization, and induction" style in this article, and provides a series of information about the support for JavaScript smart sensing in Visual Studio orcas. Taking into account the various depressing aspects of Javascript development, Visual Studio orcas deserves the expectation of many client developers. During this period, many friends in the garden have introduced this and we can see that everyone is very concerned about this.

The following is an example of how to perceive the ASP. NET Ajax client framework.

 

[3]Factoring Configuration(The configuration file is decomposed in ASP. NET)

Nikhil mentioned a small trick to break down configuration files in ASP. NET, showing the uniqueness of ASP. NET designers. For example, in Web. config:

 
...
 

<System. Web>
 

 
...
 

 
<Profile Configsource= "Profile. config" />
 

 
...
 

 
</System. Web>
 

 
...
 

Then, in the profile. config file specified above, you can define the profile-related content:

 
<Profile>
 

 
<Properties>
 

<Add Name= "Name" Type= "String" />
 

 
<Add Name= "Age" Type= "Int32" />
 

 
</Properties>
 

 
</Profile>
 

 

[4]Move the viewstate off the client and cache it on the server(Move viewstate from client to server)

With the release of Enterprise Library 3.0, we can save the viewstate data originally placed in the client's hidden field on the server-not to mention it as an "improvement", but it is always regarded as another method. As for how to apply the data in a project, you need to analyze the specific problems. The following two images show the page size information of viewstate placed on the client and server.

 

[5]Miscellaneous concepts of. Net-Part 1(Miscellaneous concepts in. Net: Part 1)

Although it is not so related to ASP. NET, this article is indeed very interesting. This section describes application domain and CLR host. Developers on any. NET platform should understand this, although you may not use:

1. What are application domains?
2. Application domains and CLR hosts-loading default Domains
3. Unmanaged portion of CLR hosts
4. Managed portion of CLR hosts
5. Creating application domains and Executing User code
6. Code access security and application domains

 

[6]Choosing a mock object framework(Select the mock object Framework)

In unit testing, mock objects have always received much attention. Roy osherove, author of this article, is selecting a mock object framework for his new book. Although it is a piece of comments, it also briefly summarizes the features of several common mock objects on the market. If you are interested, take a look.

1. Nunit. mocks
2. Nmock
3. Nmock2
4. Easymock
5. Rhino mocks
6. Typemock

 

[7]Ajax enabled Layered Web Application(Layer using Ajax Web applications)

Based on the current trend of Ajax, the author provides a 4-Layer Web application architecture that he thinks is better than Ajax. The article is too long, but it still has some reference value.