1.Can Session state be shared between Classic ASP applications and ASP.NET applications?
2.Can I run ASP.NET on Apache?
3.Do I have to use a single programming language for all the Web pages in my app?
Ans: No. Each page can be written in a different programming
language if you want, even in the same application.
If you are creating source code files and putting them in the \App_Code folder
to be compiled at run time, all the code in must be in the same language.
However, you can create subfolders in the \App_Code folder and use subfolders
to store components written in different programming languages.
Ref : http://www.aspnetfaq.com/default.aspx?FaqId=265&CategoryId=39
4. # List the various stages of Page-Load lifecycle.
5. What is DLL Hell?
DLL hell is the problem that occurs when an installation of a newer application might break or
hinder other applications as newer DLLs are copied into the system and the older applications do
not support or are not compatible with them. .NET overcomes this problem by supporting multiple
versions of an assembly at any given time. This is also called side-by-side component versioning.
6. Explain the differences between server-side and client-side code?
7. Different types of Directives.
* @ Page directive
* @ Import directive
* @ Implements directive
* @ Register directive
* @ Assembly directive
* @ OutputCache directive
* @ Reference directive
8. Describe the difference between inline and code behind.
Inline code is written along side the HTML in a page. There is no separate distinction between design code and logic code. Code-behind is code written in a separate file and referenced by the .aspx page.
9. What is the difference between Server.Transfer and Response.Redirect?
* Response.Redirect: This tells the browser that the requested page can be found at a new location. The browser then initiates another request to the new page loading its contents in the browser. This results in two requests by the browser.
* Server.Transfer: It transfers execution from the first page to the second page on the server. As far as the browser client is concerned, it made one request and the initial page is the one responding with content. The benefit of this approach is one less round trip to the server from the client browser. Also, any posted form variables and query string parameters are available to the second page as well.