|
|
Release History
| Version |
Date |
Release notes |
| 1.2.41 |
June 17, 2008 |
Changes
- Skip setget/addremove is gone and replaced by more efficient control
- Ask user what app to run if more than one exe is profiled
|
| 1.2.35 |
June 12, 2008 |
New features
- Focus on making it easier to profile full .NET
applications:
o Profiling
now build a full recursive copy of the application’s folders
o A
“Run Application”-button can start a profiled full .NET app
- Handle re-signing of signed assemblies
(registered version only)
- Finer profiling-control via attributes
SkipInstrumentation and HideAtRuntime
- Profiling is faster (3-4 times) and
runtime-module smaller (5-10 times)
- Viewer has a subtle navigation history indicator to help your browsing
- Various minor improvements and a forum on our website
Changes
- Output-dir is no longer “App\profiled”, but neighbor-directory “App (Profiled)”
- The
new EQATECProfilerRuntime.dll module is signed, so any references should use
this new one
- Registry-settings stored under local user, not
local machine (better approach on Vista)
|
| 1.1 |
May 14, 2008 |
- Support for generics
- Automatic check for new available versions
- Changed runtime-API from "EQATEC.Profiler.EQATECProfilerRuntime" to "EQATEC.Profiler.Runtime"
- Fixed bug: could produce invalid MSIL-code if a switch-statement caused a direct return
- Improved the following steps:
- Signed assemblies are still not handled, but are at least detected and skipped now
- Runtime-check ensures that deployed assemblies and runtime-module belong together
- Profiling an already profiled assembly is now an error, not just a warning
- Non-assemblies (config-files etc) are copied to profiled-folder, too
|
| 1.0 |
April 24, 2008 |
Initial release |
|