>It seems that the value of Expires should not be set. This is really confusing. I thought by passing an empty date that this was doing the same thing. As when using WWC, we simply send a blank to that value which was achieving the same thing. So, basically, I do it like this:
>
>

>        ' Add a cookie
>        ' expC1 Cookie
>        ' expC2 Value
>        ' expC3 Path
>        ' expC4 Expiration
>        Public Function AddCookie(ByVal tcCookie As String, ByVal tcValue As String, _
>         ByVal tcPath As String, ByVal tdExpiration As Date) As Boolean
>            Dim lcPath As String = tcPath
>            Dim lcValue As String = tcValue
>            Dim loCookie As New System.Web.HttpCookie(tcCookie)
>
>            ' If empty we take the default path
>            If lcPath.Length = 0 Then
>                lcPath = "/"
>            End If
>
>            ' This will determine if there is a need to encrypt the cookie
>            ' Everything is based on oApp.lEncryption
>            lcValue = oApp.EncryptUrl(lcValue, False)
>
>            loCookie.Value = lcValue
>
>            ' If the expiration date is empty, we should not pass it in order for the cookie to expire
>            ' when the browser session ends
>            If Not oApp.EmptyDate(tdExpiration) Then
>                loCookie.Expires = tdExpiration
>            End If
>
>            loCookie.Path = tcPath
>            oApp.oCookie.Add(loCookie)
>        End Function
>

>
>If someone has some more information to share on the topic, don't hesitate to let me know.

(read your reply)
Found this in documentation:
"Setting the Expires property to MinValue makes this a session Cookie, which is its default value."
Cetin