Application Architecture Guide 2.0 (The Book)


 Documentation App Arch Guide 2.0 – pdf

Part I, Fundamentals
Part II, Design
Part III, Layers
Part IV, Archetypes

patterns & practices: Application Architecture Guide 2.0 (The Book) – Home

All Microsoft SDKs in one place!


With over 50 Software Development Kits hosted on various Microsoft web sites, you might have trouble finding the right one for your development needs. Look no further! Now you can go to one page and find links to Microsoft Software Development Kits (SDKs), which provide documentation, code samples, tools, headers, libraries, and other files that developers can use to create software applications and libraries.

IIS URL Rewriting and ASP.NET routing

With the release of URL-rewrite module for IIS 7.0 and the inclusion of ASP.NET routing into the .NET Framework 3.5 SP1, there have been a lot of questions from ASP.NET developers about how these two features relate to each other and when to use each.

Differences between URL Rewriting and ASP.NET Routing

Based on the above explanation you can see that the main conceptual differences between URL rewriting and ASP.NET routing are the following:

  1. URL rewriting is used to manipulate URL paths before the request is handled by the Web server. The URL-rewriting module does not know anything about what handler will eventually process the rewritten URL. In addition, the actual request handler might not know that the URL has been rewritten.
  2. ASP.NET routing is used to dispatch a request to a handler based on the requested URL path. As opposed to URL rewriting, the routing component knows about handlers and selects the handler that should generate a response for the requested URL. You can think of ASP.NET routing as an advanced handler-mapping mechanism.

In addition to these conceptual differences, there are the following functional differences between IIS URL rewriting and ASP.NET routing:

  1. The IIS URL-rewrite module can be used with any type of Web application, which includes ASP.NET, PHP, ASP, and static files. ASP.NET routing can be used only with .NET Framework-based Web applications.
  2. The IIS URL-rewrite module works the same way regardless of whether integrated or classic IIS pipeline mode is used for the application pool. For ASP.NET routing, it is preferable to use integrated pipeline mode. ASP.NET routing can work in classic mode, but in that case the application URLs must include file extensions or the application must be configured to use "*" handler mapping in IIS.
  3. The URL-rewrite module can make rewriting decisions based on domain names, HTTP headers, and server variables. By default, ASP.NET routing works only with URL paths and with the HTTP-Method header.
  4. In addition to rewriting, the URL-rewrite module can perform HTTP redirection, issue custom status codes, and abort requests. ASP.NET routing does not perform those tasks.
  5. The URL-rewrite module is not extensible in its current version. ASP.NET routing is fully extensible and customizable.

Which Option Should You Use? Read more @ IIS URL Rewriting and ASP.NET routing : Using URL Rewrite Module : Installing and Configuring IIS 7.0 : The Official Microsoft IIS Site

IIS UR Rewriting

ASP.NET Routing

XAML guidelines


XAML Guidelines Draft  HTML, PDF, XPS and DOCX.


Introduction. 1

Why XAML guidelines?. 1

Come on, get to the guidelines. Please!. 1

Overall Project Organization. 2

Naming conventions. 3

Scenario 1: Naming elements within a scene. 3

Scenario 2: Naming elements within a template. 4

Organizing resources. 5

Scenario 1: Organizing logical resources within a scene. 5

Scenario 2: Organizing resources in a resource dictionary. 6

Using static versus dynamic resources (in non-themed projects). 8

Using static versus dynamic resources (in themed or skinned projects). 8

Using the xmlns prefix. 8

Using implicit styles versus explicit styles. 9

Wrapping control templates in styles. 9

Templating inside Expression Blend. 10

Referencing file-based resources (dictionaries, images, fonts, etc.). 10

Declaring individual XAML elements. 10

Converters. 11

Commands. 11

Theming (or more commonly skinning). 12

Conclusion. 13

Thanks. 13

Jaime Rodriguez : XAML guidelines part 3