Memory management is the main concern for any application whether application is window based or web based. In .Net, CLR has garbage collector that executes as a part of our program and responsible for reclaiming the memory of no longer used objects. Garbage collector free the memory for objects that are no longer referenced and keeps the memory for future allocations.
.NET Framework provides two methods Finalize and Dispose for releasing unmanaged resources like files, database connections, COM etc. This article helps you to understand the difference between Finalize and Dispose method.
Now let’s have a look how Web server and IIS do things internally. Before we move ahead, you have to know about two main concepts
1. Worker Process
2. Application Pool
- Check for the
IsPostBackproperty to determine whether this is the first time the page is being processed.
- Create or recreate dynamic controls.
1. Controls Values and View state Values can access from Page_PreLoad event of Page Life Cycle.
2. Session value can be access from beginning of Page_PreInit event of Page Life Cycle.
Order to call Page Life Cycle Event :-
WCF is a combined feature of Web Service, Remoting, MSMQ and COM+. Its provide a single platform for all .Net Communication.
WCF - Window Communication Foundation( code name is INDIGO) . It is used for network-distributed services syetem.
Bitwise operators treat their operands as a sequence of 32 bits (zeroes and ones), rather than as decimal, hexadecimal, or octal
Using Ajax.BeginForm in your MVC View gives you an easy way of doing a partial postback via an AJAX call. In its simplest form, our view would look something like this: