1

How to completely disable ViewState and ControlState

Posted by Sameer on April 21, 2010 in Programming |

Here is a code snippet that will COMPLETELY disable ViewState and ControlState.

Please note, if you want to disable viewstate, you can set “EnableViewState” to false for the page, however you will still see “VIEWSTATE” in the page. The reason for that is because the hidden ViewState HTML field also contains “Control State”, which is used by server controls (either built in controls or custom 3rd party controls) and is not disable-able (for core functionality that their control depends on).

However you can still disable this, with disastrous consequences on postback.

USE THIS only if you have NO POSTBACKS whatsoever and you are living in a happy client side world of javascript and web service calls.

Put this following code inside your ASP.NET page

private class DummyPageStatePersister  :PageStatePersister
{
    public DummyPageStatePersister(Page p) : base(p) { }
    public override void Load() { }
    public override void Save() { }
}

private DummyPageStatePersister _PageStatePersister;
protected override PageStatePersister PageStatePersister
{
    get
    {
        if (_PageStatePersister == null)
            _PageStatePersister = new DummyPageStatePersister(this);
        return _PageStatePersister;
    }
}

Please note this will has disastrous consequences if you attempt to do a postback because you have essentially killed the control state.

7

Flesk Viewstate Optimizer Documentation

Posted by Sameer on March 1, 2010 in .NET articles |

Flesk.ViewStateOptimizer_NET20

I came across this excellent looking tool Flesk ViewState Optimizer but was not able to find any details or documentation on it.  Apparently the tool used to be commercial but now its free!  I was able to dig up some history on it

Flesk.ViewStateOptimizer is a unique technology that overrides sending ViewState object to your client’s browser! This means that your client’s browser will no longer receive those large hidden field values, which thus reducing downloading time. Instead, Flesk.ViewStateOptimizer saves the page’s Viewstate hidden field to a file, on the server side, speeding up processing time, downloading time and data.

Combining Flesk.ViewStateOptimizer and Flesk.Accelerator,
you can benefit from reducing downloading data and downloading time up to 30 times faster! No other components
do the same or give the same results!

Flesk.Accelerator and Flesk.ViewStateOptimizer are now released with versions
targeted for the .NET Framework v2.0

 

How it works?

Flesk.ViewStateOptimizer has several viewstate optimization possibilities that can be set through the web.config file.
From viewstate data compression to saving viewstate on server farms, anything can be possible. This means that Flesk.ViewStateOptimizer can persist values using server side Sessions or files saved on shared locaton accessible by a server farm, or by using common viewstate hidden field value on client side, with the ability to compress data.

There are 2 ways to setup Flesk.ViewStateOptimizer on your web application or .Net project:

  1. In all your codebehind, instead of inheriting your class with
    System.Web.UI.Page, change the inheritance to Flesk.Accelerator.Page.
    If you use script block codebehind, use the following lines:

    <%@ Page  Language="C#" Inherits="Flesk.Accelerator.Page" %>
    
  2. Flesk.ViewStateOptimizer is designed to meet the requirements of customers that are unable to change
    the base class of their pages.
    As such, Flesk.ViewStateOptimizer provides static methods that allows calling the viewstate procedures
    from within any page class.

    If you have access to the source of your base class, just add the following lines to the code:

    													
    protected override void  SavePageStateToPersistenceMedium(object viewStateBag)
    {
       Flesk.Accelerator.Page.SavePageStateToPersistenceMedium(this, viewStateBag);
    }
    
    protected override object LoadPageStateFromPersistenceMedium()
    {
        return Flesk.Accelerator.Page.LoadPageStateFromPersistenceMedium(this);
    }
    

    If you are using precompiled code you’ll have to edit your aspx files. If at all possible, add the following

    snippet to your aspx file:

    protected override PageStatePersister PageStatePersister
    {
      get
      {
        return Flesk.Accelerator.Page.GetPageStatePersister(this);
      }
    }
    

 

Flesk.ViewStateOptimizer can use different storage methods:

  • save to file (saves ViewState into a file, server side)
  • Session (saves ViewState into a Session variable, server side)

  • Default (default ViewState saving method, sends hidden fields to client side)

Other parameters are:

  • depending on the storage method setting, Flesk.ViewStateOptimizer can be set to compress viewstate value,
    so that it can be significantly smaller than the original value
  • the request behaviour of viewstate can be set to be generated on the first request to a page and then
    reused in the following postbacks, or to be generated on each request to a page.
    A common scenario where viewstate set to be generated on each request can be usefull is in Content Management
    frameworks:
    page loads up some controls on postback based on some state stored in hidden input values, handles events
    and as a result of those actions purges the control collection and loads new controls.
    Standard Flesk.ViewStateOptimizer configuration persists the Viewstate using the same GUID as the original
    page.
    If the user then hit’s refresh (F5) in the browser, the data is posted again, the framework loads up it’s
    controls based on the original state but the viewstate value now matches the new controls. This also happens
    with any change to the viewstate between postbacks, when users back up or use refresh in their browsers.

    The solution was to make Flesk.ViewStateOptimizer generate GUID’s each and every time the viewstate is persisted.
    Only then is the viewstate truly unique for each page.

 

Features

V1.0

  • Reduces downloading time of your website or web application, by not sending back the page’s Viewstate
    hidden field.
  • This component is setup individually. It is not shared by all the webserver’s websites, but only by
    your website or webapplication. This means that you can install it in your hosting account without changing
    any webserver’s configuration.
  • Runs on .NET Framework v1.1 and v2.0. No configuration required. Only a few lines on your web.config
    file is all you need to change.
  • Greatly reduces bandwidth traffic from your webserver, reduces Posted data from your client’s browser,
    and speeds up your web application!
    Supported by WebFarms

V1.2

  • Compresses the ViewState value. This means that ViewState is sent and returned to/from client’s browser
    or saved into local file, on server, compressed, thus reducing ViewState’s value length and increasing
    speed even more!
  • This release of the Viewstate Optimizer is designed to meet the requirements of
    customers that are unable to change the base class of their pages.
  • The Flesk.Accelerator.Page class now provides two static methods that allow calling the viewstate

    procedures from within any page class.

  • ViewState files can now be persisted on shared location accessible by all servers in a server farm.

From Archive.Org

Not sure what happened to the company but glad they decided to give their product for free now! (GPL license)

Edit Aug 12, 2010

Web.Config Requirements

To use this, here is what you put in Web.Config between and

  <Flesk.NET>
    <!-- 
		The StorageMethod parameter sets the ViewState's storage type.
		Possible values are :
			
			- File (saves ViewState into a file, server side)
				- StoragePath must specify a write enabled server path ( ~ means site root path)
					If StoragePath is a web path (i.e.: \\MachineName\Dir), when used in webfarms,
					please add the following line under <system.web>
					<identity impersonate="true" userName="domain\username" password="userpass"/>
						
			- Default (default ViewState saving method, sending hidden fields to client side)
			
			- Session (saves ViewState into a Session variable, server side)
			
			- SqlServer (saves the ViewState into a database table)
				- ConnectionString specifies the database connection.
				- TableName specifies the table in the database where the records will be stored.
			
		New Option :
			Compressed="true" or Compressed="false"
			this will compress the ViewState if StorageMethod is Default or File.
			so the ViewState's value will be significantly smaller than the original value.
			Compression method is not suported by StorageMethod="Session"
			
		-->
    <ViewStateOptimizer
			PersistenceHandler="Flesk.Accelerator.SessionViewstatePersister, Flesk.Accelerator"
			StorageMethod="SqlServer"
			StoragePath="~/Files/Logs"
			ConnectionString="Server=...;Database=...;Uid=...;Pwd=...
			TableName="app_ViewState"
			Compressed="false"
			RequestBehavior="EachLoad"
			ViewStateCleanupInterval="01:00:00"
			/>
  </Flesk.NET>

Between and put the following:

    <sectionGroup name="Flesk.NET">
      <section name="ViewStateOptimizer" type="Flesk.Accelerator.Viewstate.ConfigHandler, Flesk.ViewState" />
    </sectionGroup>

Between and you can put

			<!--
			This HttpModule provides automatic cleanup of viewstate files
			on the start of each session, thus requiring
			the SessionStateModule to be installed as well.
		  -->
			<add name="ViewstateCleanupModule" type="Flesk.Accelerator.Viewstate.CleanupModule, Flesk.ViewState"/>
		</httpModules>

0

Recursively extract files

Posted by Sameer on February 11, 2010 in Hosting |

i want to recursively unzip into proper folder
so i have
/home/abdullah/quran1/files.zip

/home/abdullah/quran2/files.zip

/home/abdullah/quranfolder/files.zip

best way to search inside php files for text yoursearchtexthere

find . -name '*.php' -exec grep --with-filename --line-number 'yoursearchtexthere' {} \;

i simply want to unzip all of them at once, here is the shell script to do it in linux:

find -maxdepth 1 -mindepth 1 -type d | while read line; do unzip $line/*.zip -d $line ; done

This way is problematic if any of the folders have spaces in them

this way is better

for dir in */; do ( cd "$dir" && unzip *.zip ); done

Ref: http://unix.derkeiler.com/Newsgroups/comp.unix.misc/2005-03/0006.html

Here is an application of method 1 above, delete all files with 2008 in the name

find -name *2008* | while read line; do rm -f $line ; done

0

Improve SQL Server Plan Execution Speed With Foreign Keys and constraints

Posted by Sameer on January 11, 2010 in SQL |

Its been a while since I have posted, and I thought this was too amazing to NOT share

Apparently, using Check Constraints and adding Foreign Keys not only improves the quality of your database through ensuring referential integrity and data integrity in general, apparently it also helps the Query Analyzer design better plans!

Take a look at this post:

  • 13 Things you should know about statistics and the query optimizer, jump to Point 9.
  • Also, incase you are wondering what he means by “trusted constraint” and “non trusted constraints”, it would be ‘non trusted’ if you allowed existing non-complying data in the table to stay in there. More here on trusted constraints.

1

The Most Useful .NET Utility Classes Developers Tend To Reinvent Rather Than Reuse

Posted by Sameer on August 7, 2009 in Programming |

I think this is a classic post that everyone should read:

The Most Useful .NET Utility Classes Developers Tend To Reinvent Rather Than Reuse

5

Annoying Nulls in SQLParameters

Posted by Sameer on August 7, 2009 in Programming |

If you read Creating SqlParameters Best Practices you will find the fun you have if you have null values:

SqlParameter[] sqlParams = new SqlParameter[] { 
  new SqlParameter("@Required", required), 
  questionCode == null ? new SqlParameter("@Code", DBNull.Value) : new SqlParameter("@Code", questionCode) 
};  

Here is a nice helper function to deal with nulls without having to manually check every time.

        /// <summary>
        /// Return a SqlParameter with DBNull value or value
        /// </summary>
        /// <param name="key"></param>
        /// <param name="value"></param>
        /// <returns></returns>
        public static SqlParameter NullWrapper(string key, object value)
        {
            if (value == null)
                return new SqlParameter(key, DBNull.Value);
            else
                return new SqlParameter(key, value);
        }

Then you can use it as follows

            SqlParameter[] sqlParams = new SqlParameter[] {
                new SqlParameter("@UserID", userId),
                new SqlParameter("@itemNo", itemNo),
                General.NullWrapper("@expiryDate", expiryDate) //no need to check if null any more
            };

0

recursively search a certain file for certain text (linux)

Posted by Sameer on July 1, 2009 in Hosting |

Have you ever tried to do a recursive linux search for a text string inside a particular file? For example
grep -r "mail" *.php
and then it fails because the current folder doesn’t have any php files in it?

This below line will search all files for the text moo

find . -type f -exec grep -i 'moo' {} \; -print

Tags: ,

0

Advanced File Deletion in Linux

Posted by Sameer on June 13, 2009 in Hosting |

Here is a cool way to delete files according to some complex rules without knowing complicated bash commands.

First, create a file as follows that contains your deletion rules.

+ public_html/
+ public_html/*
- access-logs
- etc/
- logs/
- mail/
- .cpanel/
- .cpaddons/
- .spamassassin/
- .ssh/
- public_ftp/
- cpmove.psql/
- tmp/
- cpeasyapache/
- MySQL-install/

Then, run rsync with the source and destination folder being the same
rsync -avz --include-from:rulesFile.txt . . --delete-excluded

You can add –dry-run if you want to see what will be deleted:

rsync -avz --include-from:rulesFile.txt . . --delete-excluded --dry-run

Tags:

1

ASP.NET 4.0 Features

Posted by Sameer on May 27, 2009 in Programming |

Here is a list of new features in ASP.NET 4.0.

Very interesting. Auto start feature, new ways to choose where data is cached, built in option for compression session (via gzip), and more!

0

LINQ to Entities Create Function Import Scalar Value Missing

Posted by Sameer on April 9, 2009 in .NET articles |

LINQ to Entities seems really great. It can save you a lot of time in writing unnecessary db connection code, improve the performance many fold, only connect to the db when required (lazy loading), and easy concurrency handling for you.

However there is a missing feature which I found out the hard way. If you try to do a ‘Create Function Import’ and it returns a scalar, the code will not be automatically generated, due to ‘lack of time’ from the MS Team:

MSDN Forums – See the post by Noam.

So basically, you are handicapped! Either write the code yourself or just do it the old fashioned way

Copyright © 2007-2014 SharpDeveloper now AgileChai All rights reserved.
This site is using the Desk Mess Mirrored theme, v2.0.2, from BuyNowShop.com.