Comments on: Typed session data in ASP.NET made easier still

By: ashis

ashis — Sun, 29 Jun 2008 09:01:15 +0000

Thank it is very easy to understand and workable.

By: Damien Guard

Damien Guard — Sat, 04 Aug 2007 04:05:49 +0000

There is nothing actually stopping you from creating more than one of these classes as long as each uses a different dictionary key in the get property.

Defaults can be handled by specifying them in the MySession class.

The additional overhead of unused variables could well be an issue if you have a large number of sessions that only use a subset of the session variables.

[)amien

By: Philippe Leybaert

Philippe Leybaert — Sat, 04 Aug 2007 01:28:20 +0000

Your solution is indeed simpler, but it has some important limitations:

All fields are stored in the session, even if you don't use them (meaning it is not suitable if you have a lot of session variables).

There is no way to specify defaults that will be returned when there's nothing in the session.

All session variables have to be defined in the same class.

But, indeed, in certain cases your solution is very nice.

By: Damien Guard

Damien Guard — Fri, 03 Aug 2007 23:22:28 +0000

While it is true you can't have something like:

There is nothing stopping you doing:

SqlDataSource1.SelectParameters.Add("CustomerID", MySession.Current.CustomerID);

In the code-behind.

[)amien

By: Rik Hemsley

Rik Hemsley — Fri, 03 Aug 2007 23:06:19 +0000

Nice idea, though won't work with bound controls which use session data as parameters to their data source.