ASP.NET Difference FAQs-9

1.Difference between .NET Application Development and Traditional Application Development
.NET Application Development
Traditional Application Development
Using .NET Framework, your program will be compiled into an intermediate language representation called MSIL (Microsoft Intermediate Language).
Your program will be compiled into an assembly language code that is very specific to the platform in which you are running your application.
MSIL code will not contain any API calls specific to any platform.
Assembly language code will contain API calls specific to the current application platform.
This MSIL code is then converted into machine code at runtime using CLR (Common Language Runtime).
This assembly language code is then converted into machine code.
Optimization is done at runtime by CLR.
Optimization is done by the compiler itself at compile time.
The compiler used in this process is static meaning that it checks only for syntax and the necessary semantics.
The compiler is not static. It performs both compilation as well as optimization.
Libraries used by your program are linked even before generating MSIL, but it is linked in an un-compiled form. This will be compiled by the compiler and it will be used by the CLR while executing the program.
Libraries used by your program are linked only after generating the machine code.
The program will not directly call APIs of the operating system. Instead CLR will act as a mediator. CLR will call API's of operating system and the result of execution will be returned to program.
Now the program is ready for execution by the operating system. The program will directly call APIs of the operating system.
Automatic memory management and garbage collection is done by CLR.
No automatic memory management or garbage collection.
.NET Framework Class Library provides object oriented libraries.
No object oriented principles are incorporated.

2.Difference between CSS and Themes
Applies to all HTML Controls
Applies to all the server controls
Is applied on the Client Side in the Browser
Is applied on the server rather than in the browser
We can apply multiple style sheets to a single page
But we cannot apply multiple themes to a single page. Only one theme we can apply for a single page.
The CSS supports cascading
But themes does not support cascading
The CSS cannot override the property values defined for a control.
But any property values defined in a theme, the theme property overrides the property values declaratively set on a control, unless we explicitly apply by using the StyleSheetTheme property.
Cannot be Applied through the configuration files
Can be Applied through Configuration Files.
Can be used directly via a reference to the css file location
All theme and Skin files should be placed in a special Asp.net folder called the “App_Themes” in order for the themes to work and behave normally.
Do not require any other resource like Skin files
Each theme should be associated with at least one Skin file.
In case of CSS you can define only style properties
But a theme can define multiple properties of a control not just style properties such as we can specify the graphics property for a control, template layout of a GridView control etc.
3.Difference between Postback and Callback
A Postback occurs when the data (the whole page) on the page is posted from the client to the server..ie the data is posted-back to the server, and thus the
page is refreshed.
A callback is also a special kind of
postback, but it is just a quick round-trip to the server to get a small set of data(normally), and thus the page is not refreshed, unlike with the postback.
With Asp.Net, the ViewState is refreshed when a postback is invoked.
With Asp.Net, the ViewState is not
refreshed when a callback is invoked.
A postback occurs when a request is sent from the client to the server for the same page as the one the user is currently viewing. When a postback occurs, the entire page is refreshed and you can see the typical progression on the progress bar at the bottom of the browser.
A callback, generally used with AJAX,
occurs when a request is sent from the
client to the server for which the page is not refreshed, only a part of it is updated without any flickering occurring on the browser.

4.Difference between Session.Clear() and Session.Abandon()
Session.Clear() just removes all values (content) from the Object. The session with the same key is still alive.It is just like giving value null to this session.
Session.Abandon() destroys the session and the Session_End event is triggered and in the next request, Session_Start will be fired.
Use Session.Clear(), if we want user to remain in the same session and we don not want user to relogin or reset all his session specific data.
So, if we use Session.Abandon(), we wil lose that specific session and we will get a new session key. We could use it for example when the user logs out.


  1. I’d have to check with you here and get more information about ASP .Net Development. Which is not something I usually do! I enjoy reading a post that will make people think. Also, thanks for allowing me to comment!

  2. Warm welcome Martin ! Thank you for your presence and feedback.More updates on ASP.NET Development will come in the future.

  3. I think this is very useful blog.....and thank you for this details....

    1. Thank you for your positive feedback.You can also visit by wordpress blog @ http://globaldownloadlinks.com/ for all technical contents.