Loupe 3.5.4 is backwards compatible with 3.0 and has the same constraints as 3.0 when working with older versions:
You can mix older and newer agents on the same computer, however they will be unaware of each other and will not coordinate when sending to hub, packaging, or auto send consent. When upgrading any unsent sessions recorded by a 2.x agent will not be transferred by the newer agent.
We've added overloads for Log.Error, Log.Critical, and Log.Write (and a few related methods) to support attributing the log message based on where the logged exception was thrown instead of where it was logged. This is the same behavior that Log.RecordException uses but allows you to fully control the log message. These overloads are designed for logging within higher-level exception handlers where it isn't meaningful where it was caught as much as where the error happened in the first place.
Now the application will remember your window settings, filter settings, and other user options when you use Live View for each application. This way when you're debugging an application and place one application's live view in one area and another somewhere else it'll remember exactly where you placed each one.
From customer feedback and support cases we've incorporated the standard MessageAlert event handler we've previously recommended developers add into the core of the Agent. It will now automatically set SendSessions = true and the send delay to 5 minutes whenever there are error or critical messages logged and server auto send is enabled.
The effect of this behavior change is that if you are using auto send and do not want to receive data from sessions while they run you will need to either set the new "autoSendOnError" configuration option to false or subscribe to the MessageAlert event and set SendSession = false at runtime.
For users of the free Loupe Desktop we've added an optional registration screen so people can opt into our mailing list for Loupe and receive notification of updated versions. This is only displayed to users that aren't connected to a Loupe Server (since Loupe Server users have already had the chance to opt in or out of receiving notifications).
The Log4Net Agent has been updated to use version 1.2.11 of Log4Net. This works with the Log4Net NuGet package version 2.0.0 which is the current version. Since the signing key was changed between Log4Net 1.2.10 and 1.2.11 this change was necessary to allow forwards compatibility with the version published to NuGet. If you are still using an older version of Log4Net we recommend you directly compile the Log4Net appender from source code which is published in the installed SDK.
For more information, see Third Party Integration - Using Log4Net with Loupe.
Since this is an update release you should read Getting Started - What's New - Version 3.5 for a more complete picture of the new capabilities since version 3.0.