Is it necessary to lock application state before accessing it ?
Answer / kumar saurabh
Only if you're performing a multistep update and want the update to be treated as an atomic operation. Here's an example:
Application.Lock ();
Application["ItemsSold"] = (int) Application["ItemsSold"] + 1;
Application["ItemsLeft"] = (int) Application["ItemsLeft"] - 1;
Application.UnLock ();
By locking application state before updating it and unlocking it afterwards, you ensure that another request being processed on another thread doesn't read application state at exactly the wrong time and see an inconsistent view of it.
| Is This Answer Correct ? | 0 Yes | 0 No |
Explain what are the advantages of asp.net mvc framework? : asp.net mvc
Apart from IDE what are the enhancements in asp.net 2.0?
How can we prevent an aspx page get refreshed when any information fetch from the database ?
Can you create an app domain ?
what is command line compiler.what are the steps and how it is related to debugging.
How do you construct HtmlResponseMessage?
What's a bubbled event?
About Garbage Collector?
How To Authenticate Your Web service??
what is DLL Hell and how it is solved in .NET? please explain clearly??
what are the levels of securities need to be considered for the finincial web application?
Features in ASP.NET ?
Visual Basic (800)
C Sharp (3816)
ASP.NET (3180)
VB.NET (461)
COM+ (79)
ADO.NET (717)
IIS (369)
MTS (11)
Crystal Reports (81)
BizTalk (89)
Dot Net (2435)
Exchange Server (362)
SharePoint (720)
WCF (340)
MS Office Microsoft (6963)
LINQ Language-Integrated Query (317)
WPF (371)
TypeScript (144)
Microsoft Related AllOther (311)