Hi,

If I understand your question correctly, this is my view on the topic,
please note my closing paragraph.

SmartClients do not generally need to maintain session state on the server.
However if you absolutely need that functionality one option would be to use
a WebService to communicate back to the server from the smart client and
have your WebService maintain session state, by default WebServices do not
maintain session state, but this can be enabled with the following attribute
on the web method:

[System.Web.Services.WebMethod(EnableSession=true)]

Obviously this would require that the smart client runs in a more trusted
environment and would thus require configuration of client workstations. I
normally address this with a simple msi which is rolled out via active
directory.

On the other hand if all you need is to persist information for the client
then you could use isolated storage

Personally I have never needed to go the route of server side sessions for a
smartclient application and would probably try to find an alternative
design.

Hope this helps