Performance on the Data Tier
Tip 1-Return Multiple Resultsets
Tip 2-Paged Data Access
Tip 3-Connection Pooling
Tip 4-ASP.NET Cache API
Tip 5-Per-Request Caching
Tip 6-Background Processing
Tip 7-Page Output Caching and Proxy Servers
Tip 8-Run IIS 6.0 (If Only for Kernel Caching)
Tip 9-Use Gzip Compression
Tip 10-Server Control View State
Conclusion
Check this out http://msdn.microsoft.com/msdnmag/issues/05/01/ASPNETPerformance/
We often need collection in our programming. To implement collection, we have two choices: fixed-length collection which is familiarly "array" and dynamic length collection. One of the popular dynamic collections is ArrayList. ArrayList (actually Queue, Stact, other collection also) accepts object type, so you could add any type object in it. This is both advantages and disadvantage of them. (In this case, we will take ArrayList as example).
Disadvantage? Yeah, it is not type-safety. Check this out!
Suppose we are going to have a collection of integer using ArrayList:
ArrayList arr = new ArrayList();
arr.Add(1);
arr.Add(2);
arr.Add("3");
arr.Add(4);
foreach (int a in arr)
{
Console.WriteLine(a);
}
Notice that when I code arr.Add("3"), there was just fine. No compile time error. But when I run it.
Yeah, InvalidCastException. Runtime error. Why? This is because when we enumerate there were some invalid type occurred. We actually expect to add a collection of integer, but eventhough I add a string, the ArrayList accept it without any complain.
.NET team aware that it would be better to have the compile time error, rather than runtime error. So, .NET 2.0 introduced us Generic.
The goal of Generics is:
- Type safety
- No Boxing and UnBoxing, because it takes some resources to do that.
In this sample, I will not show you too funky feature, I will just introduce a generic version of ArrayList, which is List<>. Here we go J
Look! I define my List<> just to accept integer. When I add integer, it just work fine, but when I add others type (in this case integer), the compiler will complain. The compile time error. Compiler will tell, "wrong type, bro! Fix it first".
Other generic collection are also available:
Type | Generic Type |
ArrayList | List<> |
Queue | Queue<> |
Stack | Stack<> |
Hashtable | Dictionary<> |
SortedList | SortedList<> |
ListDictionary | Dictionary<> |
HybridDictionary | Dictionary<> |
OrderedDictionary | Dictionary<> |
SortedDictionary | SortedDictionary<> |
NameValueCollection | Dictionary<> |
DictionaryEntry | NameValuePair<> |
StringCollection | List<String> |
StringDictionary | Dictionary<String> |
N/A | LinkedList<> |
Simple? Nothing funky? Yeah, simple but useful, right?
Yeah... We IT people should care our health to
.
Sitting in front of a computer for a whole day could affect our health. Somewhat like sore eyes, backache, neck problem, etc
The following are some QAs with Dr. Jerry Sanders, D.C.
http://www.sqlservercentral.com/columnists/mcoles/3023.asp
Check this out, hope it helps.
Earlier, ASP.NET Ajax team release the new release of AjaxControlToolkit. I myself had tried it, and there were few issues that I met.
· The FilteredTextBox didn’t allow Del Key and arrow
· VSWebSite.Interop become a problem when doing deployment
Now, the newer version of AjaxControlToolkit has released and fixed those problems. You can download it here [J] http://www.codeplex.com/AtlasControlToolkit/Release/ProjectReleases.aspx?ReleaseId=4923