Loupe - Log - Monitor - Resolve
Loupe / User's Guide / Loupe Desktop / Session Viewer / Loupe Desktop - Session Viewer - Session Details
In This Topic
    Loupe Desktop - Session Viewer - Session Details
    In This Topic

    The Session Details tab of the session viewer contains:

    This information is particularly useful when comparing a session that experienced a problem with others that didn't - often the difference is caused by an attribute of the processing environment that is different, such as a dependent assembly or process architecture.

    Session Details

    Session Details

    Session Properties

    Many properties are captured for each session.  Of particular interest are:

    Process Architecture

    While .NET generally handles architectural differences automatically there are situations when problems can arise.  For backwards compatibility reasons, newer 64 bit architectures (IA64 and Amd64) still support running processes as 32-bit applications (X86).  The session details includes the .NET Architecture and computer architecture so you can determine what the native architecture of the operating system was and what the effective architecture of the process was.  Architecture also shows up in the assembly list, indicating whether a particular assembly was targeted at just one architecture or was compiled as MSIL which can be used in any architecture.


    Often, an application is developed and tested exclusively on a single culture (like United States English, which has the unique name "en-US") and then encounters unexpected errors when run on an alternate culture.  There are multiple cultures that come into play:

    While some of these cultures can conceptually change during the execution of a process, the initial culture is captured and reflected in the session details.


    A list of all of the threads that logged any message.  Other threads may have existed in the .NET process that didn't log any messages and therefore weren't recorded.  For each thread, the following information is captured:


    Every assembly that was loaded into the process is listed.  For each assembly that was loaded, the following information is captured:


    If an application recorded information from multiple users (including the process user) then the Users panel is displayed with the list of the details available for each user.  If an application provides extended Application User information this will be displayed here, making it easy to test exactly what was provided by the application at runtime.

    See Also