Before installing Gibraltar, you need to have .NET 2.0 SP1 or later installed.
If .NET 2.0 is installed without SP1 or SP2 installation will proceed but the application
will fail to start.
Uninstall any previous version of Gibraltar before installing a new version.
On computers with Visual Studio installed the installation will pause for a while
at 99% while it updates the help content. Please do not interrupt this process
which, depending on the speed of your computer and how many other products have
integrated with Visual Studio Help, may take from one to ten minutes.
This release of Gibraltar includes both a new Analyst and Agent. You are encouraged
to upgrade to the newest Agent at your earliest convenience. These versions
are backwards compatible with previous versions of Gibraltar (meaning they can open
and work with data produced by those versions) however there were minor updates
that will cause a compatibility warning if you attempt to use a version of Gibraltar
Analyst prior to build 2.00.0445 to read data recorded by this newer version of
the Gibraltar Agent. Accordingly, we recommend upgrading both Analyst and
Agent to the latest version.
New Features in Gibraltar 2.0.1
This specific release is an update to Gibraltar 2.0.1 to fix issues reported in
the initial release (build 2.00.0445). No new features were introduced in
this build. The following is a summary of the new features in Gibraltar 2.0.1.
Gibraltar Agent for ASP.NET
While the Gibraltar Agent has always worked for any .NET 2.0 application, we've
added a specific agent for ASP.NET that provides additional health and performance
monitoring, right out of the box. This feature is integrated with the Configuration
Wizard for easy installation without any code changes. Read More about Using Gibraltar with ASP.NET
Configuration without configuration files
You can now perform all Gibraltar Agent configuration without using an application
configuration file. Instead, you can specify every configuration option through
your code. This is particularly useful for monitoring unit tests and for creating
single file applications where the Agent is being merged into your application and
it's not viable to have configuration in a separate file. Of course, you
can still do all configuration with application configuration files just like before.
Read More about doing Agent Configuration through Code
Improved Email Options
It's now much easier to configure email to route through a mail server on an
alternate port and/or using SSL. This can be done through the configuration
wizard or through the API making it easy to use Google Apps or other restricted
email gateways to submit session data. Read More about Emailing Packages.
Reduced Agent Memory Utilization
We've found ways to reduce the memory usage of the Gibraltar Agent when using
the Live Viewer and in other cases to further ensure that Gibraltar won't interfere
with your production environment. You can read more about what we did on the
Gibraltar Blog, Rock Solid.
- Fixed: Packager Dialog Selection Criteria had a grammatical error in the description
of the first option.
- Fixed: Individual timestamps that vary in time zone offset from the first
timestamp recorded by the agent are assigned an inaccurate time zone offset when
- Fixed: Log Message Count is off by one because End Session messages are not
- Fixed: Repository session summary views did not show sessions that were recorded
with a future date and time (typically in a different time zone)
- Fixed: Unable to view session details (log messages, metrics, etc.) for sessions
recorded in time zones with a positive UTC offset when Analyst is running in a time
zone with a positive UTC offset.
- Fixed: Saving a package as a new file using Save As appears to work but does
not actually create a new package file. Subsequent attempts to open sessions
from the package fail.