Loupe 2.5.2 is a maintenance update to resolve issues found in Loupe 2.5.  For more information on recent enhancements see Getting Started - What's New - Version 2.5.

New Features In This Release

Logging of Assembly Load Failures now Optional (and off by default)

We received significant feedback that the new logging of assembly load failures introduced in 2.5.1 was unduly chatty and confusing because of the large number of assemblies that the .NET framework probes for.  This logging has been disabled by default in 2.5.2 but can be individually enabled by setting the enableAssemblyLoadFailureEvents property in Developer's Guide - Listener Configuration.

Improved Source Code Viewer in Loupe Desktop

We've incorporated an updated source code viewer that allows you to edit and save source code changes as well as copy/paste code directly from the view.  This is only available in the full Loupe Desktop session viewer, not the live viewer.

Local Disk Usage Default Raised

Based on customer feedback we've increased the default maximum amount of local data per application from 50 to 150MB.   

Defects Fixed In This Release

This is the list of issues fixed since the last release version (2.5.1.793)

Agent

• Fixed: Packager class does not return failure information for Send to Server operations.
• Fixed: Loupe Agent for PostSharp doesn't have aspect ordering hints to enable easier composition of aspects.
• Fixed: The Live Viewer message buffer was activated in ASP.NET applications, causing the agent to use more memory than necessary.
• Fixed: Packager utility didn't correctly parse fully qualified paths that started with a drive letter and a colon.
• Fixed: Agent for ASP.NET fails to record web requests that resolve in a blank path.

Loupe Desktop

• Fixed: Long Xml Details cause the log message viewer to be very slow.
• Fixed: The Top Errors by Class / Top Errors by Category summary views in Loupe Desktop are unacceptably show when there are a large number of unique errors.
• Fixed: Gemini Session Lists don't show the real user name from the server for assigned user, instead just showing the key.

Server

• Fixed: Updated session data isn't available if the session was already read by a Loupe Desktop due to a problem with the file cache.
• Fixed: If a request times out while waiting on an internal lock it may cause all subsequent requests to timeout.