Contents tagged with Web Form
-
ASP.NET Web Forms and IdentityServer3
-
Centralizing SqlDataSource Events
Introduction:
-
Page Instrumentation in ASP.NET 4.5
Introduction:
-
Invalid Html Response and JS Errors when you open your Application in Visual Studio 2013
-
Using Response.Redirect Effectively
Introduction:
-
Localizing Default Error Messages in ASP.NET MVC and WebForm
Introduction:
-
Using Classic ASP, PHP and WebForm Pages in ASP.NET MVC Views
Introduction:
-
Persisting Session Between Different Browser Instances
Introduction:
By default inproc session's identifier cookie is saved in browser memory. This cookie is known as non persistent cookie identifier. This simply means that if the user closes his browser then the cookie is immediately removed. On the other hand cookies which stored on the user’s hard drive and can be reused for later visits are called persistent cookies. Persistent cookies are less used than nonpersistent cookies because of security. Simply because nonpersistent cookies makes session hijacking attacks more difficult and more limited. If you are using shared computer then there are lot of chances that your persistent session will be used by other shared members. However this is not always the case, lot of users desired that their session will remain persisted even they open two instances of same browser or when they close and open a new browser. So in this article i will provide a very simple way to persist your session even the browser is closed.
Description:
Let's create a simple ASP.NET Web Application. In this article i will use Web Form but it also works in MVC. Open Default.aspx.cs and add the following code in Page_Load. -
Globally Handling Request Validation In ASP.NET MVC
Introduction:
-
Server Controls in ASP.NET MVC without ViewState
Introduction :
ASP.NET Web Forms provides a development environment just like GUI or windows application and try to hide statelessness nature of HTTP protocol. For accomplishing this target, Web Forms uses ViewState (a hidden field) to remove the gap between HTTP statelessness and GUI applications. But the problem with this technique is that ViewState size which grows quickly and also go back and forth with every request, as a result it will degrade application performance. In this article i will try to use existing ASP.NET server controls without ViewState.