Culture What's the difference between Codebehind="My cs" and src="My cs"? Some times it is useful to cache the output of a website even for a minute, which will result in a better performance. Net provides a cache object for eg: cache["States"] = ds States; What do you mean by authentication and authorization? NET Framework SDK, open the file containing the code you want to debug, and set your breakpoints. (If "aspnet_wp.exe" doesn't appear in the list then check the "Show system processes" box.) Click the "Attach" button to attach to "aspnet_wp.exe" and begin debugging. The controls can bubble up their event handlers, allowing the main Data Grid event handler to take care of its constituents. NET function executed on Mouse Over over a certain button. It's the Attributes property, the Add function of that property. Caching Output Caching: Caches the dynamic output generated by a request. Go back to Dbg Clr, choose "Debug Processes" from the Tools menu, and select "aspnet_wp.exe" from the list of processes. When you have a complex control, like Data Grid, writing an event processing routine for each object (cell, button, row and so on) is quite tedious. Add("on Mouse Over","some Client Code();") What data type does the Range Validator control support? In the context of a web application, caching retains the pages or data across HTTP requests and reuses them without the expense of recreating them. NET has 3 kinds of caching, strategies Output, Caching Fragment and Caching Data. Caching is a technique widely used in computing to increase performance by keeping frequently accessed or expensive data in memory.
A more complex example would be that you disposed of a class that maybe you use to access the database. But then, somewhere else, you tried to call a method of that class that used those objects that no longer exists.
If I update session state then should I lock it, too?
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.
This is most common in classes where you are using class-wide instantiated objects.
If you create and drop your objects within each method, this isn’t going to be a problem, and you are actually following a better guideline by creating at the last necessary moment, and destroying at the first possible moment, not to mention avoiding possible exceptions like Invalid Reference Exception.
What does Asp Compat="true" mean and when should I use it?