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 [...]]]> 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   ageStatePersister
{
    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.

Other Interesting Posts

• PHP VS. ASP.NET
• Creating SqlParameters Best Practices
• Creating Maintainable Database Queries In C# (with source code)

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

Here is a nice helper function to deal with nulls without having to manually [...]]]> 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
            };

Other Interesting Posts

• PHP VS. ASP.NET
• Creating SqlParameters Best Practices
• Creating Maintainable Database Queries In C# (with source code)

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

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

Other Interesting Posts

• PHP VS. ASP.NET
• Creating SqlParameters Best Practices
• Creating Maintainable Database Queries In C# (with source code)

A quick overview how to do it.
1. Edit your .CSPROJ file and manually add another reference to System.Core
Add a True

This will make the compiler copy it to the BIN folder.

Thats it. You can now use .NET 3.5 features

It’s so easy you won’t believe it

and when you are done

References:
sp_addlinkedserver [...]]]> When using SQL Server Management Studio you might want to copy data from one DB to another (using just a SELECT and INSERT statement)

sp_addlinkedserver @server='192.168.123.456', @provider='SQLNCLI',    @srvproduct='',@provstr='User Id=sa; Password=are-you-crazy-to-use-sa'

insert into [192.168.123.456].MYDB.dbo.tblRecords

select * from MYDB.dbo.tblRecords

sp_dropserver  [192.168.123.456]

References:
sp_addlinkedserver on MSDN

sp_dropserver on MSDN

Other Interesting Posts

• PHP VS. ASP.NET
• Creating SqlParameters Best Practices
• Creating Maintainable Database Queries In C# (with source code)

If you have this script running, chances are your server has been exploited.

Here is the actual dm.cgi script if you want to see it.

If you manually want to simulate a postback, Here is how you would stick together a string manually calling __doPostBack in .NET 1.1
In this case its making a link in a particular linkbutton control inside a datagrid.

__doPostBack in .NET 1.0

How we track flu trends [...]]]> This is quite an astonishing use of Google Trends.  Google realized that when people get sick they (obviously) search for flu related keywords and they managed to find a correlation to actual published flu infection statistics.  Quite amazing and this is definately a unique and interesting application of technology.

How we track flu trends (Google blog)
Here is an explanation of how it works

What other ideas can we apply this to?

Other Interesting Posts

• PHP VS. ASP.NET
• Creating SqlParameters Best Practices
• Creating Maintainable Database Queries In C# (with source code)