The SessionIdLoggingContext type exposes the following members.

Constructors

  NameDescription
Public methodSessionIdLoggingContext
Initializes a new instance of the SessionIdLoggingContext class

Methods

  NameDescription
Public methodDispose
Releases all resources used by the SessionIdLoggingContext
Public methodEquals
Determines whether the specified Object is equal to the current Object.
(Inherited from Object.)
Protected methodFinalize
Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection.
(Inherited from Object.)
Public methodGetHashCode
Serves as a hash function for a particular type.
(Inherited from Object.)
Public methodGetType
Gets the Type of the current instance.
(Inherited from Object.)
Protected methodMemberwiseClone
Creates a shallow copy of the current Object.
(Inherited from Object.)
Public methodToString
Returns a string that represents the current object.
(Inherited from Object.)

Extension Methods

  NameDescription
Public Extension MethodAs<(Of <<'(T>)>>) (Defined by TypeHelperExtensionMethods.)
Public Extension MethodIsBetween
Apply a "between" constraint to the named property Note: throws an exception outside of a QueryOver expression
(Defined by RestrictionExtensions.)
Public Extension MethodIsIn(array<Object>[]()[][])Overloaded.
Apply an "in" constraint to the named property Note: throws an exception outside of a QueryOver expression
(Defined by RestrictionExtensions.)
Public Extension MethodIsIn(ICollection)Overloaded.
Apply an "in" constraint to the named property Note: throws an exception outside of a QueryOver expression
(Defined by RestrictionExtensions.)
Public Extension MethodIsProxy (Defined by NHibernateProxyHelper.)
Public Extension MethodToTypeParameters (Defined by ReflectHelper.)

Properties

  NameDescription
Public propertyStatic memberSessionId
We always set the result to use a thread static variable, on the face of it, it looks like it is not a valid choice, since ASP.Net and WCF may decide to switch threads on us. But, since SessionIdLoggingContext is only used inside NH calls, and since NH calls are never async, this isn't an issue for us. In addition to that, attempting to match to the current context has proven to be performance hit.

See Also