Release History

Version Date Release notes
2.0.89
Feb 11
2009
Minor fix:
Signed assemblies were not re-signed when running the command-line profiler
Certain machines (hardware-dependent) would occasionally give "0" as timing result
2.0.34
Dec 16
2008
New major release:

Major new features:
  • Much easier to use, especially for full .NET apps
  • Profiler/viewer unified into one application
  • Take profiling-snapshots "live" for a running app
  • Report-folder is now fixed and you decide where it is

Lots of other features and changes, too:
  • Save/load settings in named config-files, or just have it handled automatically
  • EQATECProfilerCmd now take a dir or config-file as argument
  • Specify paths using environment-variables, including $(AppDir)
  • Report-files renamed to profiled-exename-timestamp.eqlog
  • Full drag/drop-support for report/config-files
  • Pass command-args to profiled app
  • Window title now displays report-name, if any
  • Profiler show list of all saved reports
  • Profiler-diagnostics saved to logfile, profiler.log
  • Run .Net CF apps directly, too
  • Comes with pre-compiled Bubbles-demo
  • "Most recently used"-dropdowns for apps, executables, and reports
  • Keyboard-shortcuts everywhere (except for call-graph)
  • Navigate easy backwards/forward in call-graph
  • Timing for full Windows .NET apps now have 1 millisec precision (was 16ms)
  • Small averages now shown with one decimal
  • Auto-snapshot for .NET Services and ASP NET apps
  • Prefix those pesky recursive methods with a "<", as in "<433 ms"
  • Resize parts of window
  • Simplified UI and workflow
  • Fixed bug: Running a profiled app did not correctly set its working directory
  • Fixed bug: F# tail.call was not handled properly; it is ignored for now
  • and lots of other minor improvements

 1.2.60




July 7, 2008



Fix

  • Minor fix: if profiling was unsuccessful, but you ran the profiled app anyway, a nullpointer-exception would be thrown. The app now fails with a more informative message telling you to go back and fix the profiling errors.
 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