This article, in the tips and tricks format, takes a good look at the components in an App-V infrastructure and the role each of them plays and how the interconnection existing in those components builds the existing models available to deploy App-V in our organization.
The reader will benefit from the previous article on FAQ on Virtualization and Microsoft App-V.Read Tips and Tricks on Microsoft Application Virtualization 4.6 in full
Validation is the key to any application that accepts input of any kind, but where should it be implemented—on the client where it is most responsive, in the business logic where it is most central, or in the data layer where it is most secure? ASP.NET MVC provides a simple yet powerful framework for defining validation from a central location that is decoupled from the data layer; validation that makes use of client scripting without being dependent on it; and with all this, keeping the validation DRY.
In this article by Andrew Siemer and Richard Kimber, authors of ASP.NET MVC 2 Cookbook, we will cover:
- Basic input validation
- Data annotations
- Client-side validation with jQuery
- Custom validators
- Remote validation with jQuery
Master pages are a very important part of any large-scale site. They allow you to easily manage the boilerplate code that every page in your site uses. This might encompass features such as navigational items, header and footer layout, basic layout, and so on. In this article by Andrew Siemer and Richard Kimber, authors of ASP.NET MVC 2 Cookbook, we will discuss how to create and use master pages to control application-wide formatting. We will also take a look at how to employ a base page, to control which master page is used. Then we will see how to pass data from the view to the master page. Specifically we will cover:
- How to create a master page
- Determining the master page in the ActionResult
- Controlling which master page is used with a view base class
- Setting the master page from a controller base class
- Passing data to the master page
A slow website with angry managers looking over your shoulder and raging calls from advertisers and clients is every web developer's nightmare.
The following article will take a look at some tips and tricks to improve the performance of your ASP.NET-based website, such as:
- Caching is one of the methods used to improve website performance
- Hotlinking should be avoided
- Reducing space taken by ASP.NET Ids
With the completion of LINQ to NHibernate for NHibernate 3.0, we can easily implement the specification pattern. In this article by Jason Dentler, author of NHibernate 3.0 Cookbook, we will see how to set up and use the specification pattern with the NHibernate repository.Read NHibernate 3.0: Using LINQ Specifications in the data access layer in full
For queries where the criteria are not known in advance, such as a website's advanced product search, ICriteria queries are more appropriate than named HQL queries. This article by Jason Dentler, author of NHibernate 3.0 Cookbook, shows how to use the same DAL infrastructure with ICriteria and QueryOver queries.
In an effort to avoid overwhelming the user, and increase application responsiveness, large result sets are commonly broken into smaller pages of results. This article also shows how we can easily add paging to a QueryOver query object in our DAL.Read NHibernate 3.0: Using ICriteria and Paged Queries in the Data Access Layer in full
In this article by Matt Perdeck, author of ASP.NET Site Performance Secret, we will cover the following:
- Missing indexes
- Clustered index
- Non-clustered index
- Included columns
- Selecting columns to give an index
- Maintaining indexes
- Expensive queries
In many websites, database access is the most expensive part of producing a web page. This article by Matt Perdeck, author of ASP.NET Site Performance Secret, shows how to identify the most common sources of delays and how to resolve them.
This article shows how to pinpoint and prioritize a number of common bottlenecks, so that you can spend your time where it counts the most. These bottlenecks include:
- Missing indexes
- Expensive queries
- Execution plan reuse
Read Pinpointing Bottlenecks for Better Database Access in ASP.Net in full