Release History

3.4.4

August 25, 2010

Release 3.4

Change: Renamed "Personal" edition to "Standard" edition
Change: Introduced license-dependent limit on instrumented assemblies, e.g. max 10 DLLs in the free edition (note: for all you users with an existing license there is still no limit)
Improvement: User now has the option to deploy only .NETCF assemblies rather than all files in the entire folder structure
Fix: During .NETCF file deployment the profiler could hang if no files could be copied to the device at all
Fix: "Select all" assemblies now don't select those type of files that are by default de-selected (like resource-files etc)
Fix: Profiled apps running under .NET 3.5 without SP1 could get a "WaitOne" runtime-error
Fix: Help-links to online forums were wrong

3.3.80

June 9, 2010

Update

For .NETCF apps the data-connection could timeout before it was established.

3.3.71

June 1, 2010

Update

License-check could fail if firewall/proxy required authentication

3.3.63

May 27, 2010

Update

If output-dir had been changed from $(AppDir) for a .NETCF app the profiler would still deploy+run the original files from the original app-dir, not the instrumented ones in the output-dir. Result: no data connection, no reports, and no log.
Upgraded project-files could cause launch of wrong Casinni-webserver version for Silverlight apps
Now exclude *.asmmeta.dll and *.resources.dll from profiling by default

3.3.43

May 10, 2010

Update

.NET CF executables could not be started if there were full .NET assemblies
Take snapshot/Reset counters were sometimes disabled when they shouldn't be
Connection errors to .NET CF device now correctly reported
Icon for eqbak-files changed to indicate that they should not be deleted

3.3.33

May 4, 2010

Update

Calling the API's runtime-methods could crash if app was not being profiled
Allow free platform-choice (arm, x86 etc) for emulators, too; the built-in hint from the device manager was not always correct
Always log "App x starting" to the log-file unless logging is completely turned off, so it no longer is empty by default
Double-clicking .eqbak-files would cause an error-message

3.3.24

Apr 26, 2010

Update

Fixed application-type detection flaw (full/netcf/silverlight) in scenarios with several types of assemblies

3.3.19

Apr 22, 2010

Update

Fixed .NET CF deployment problem for 64-bit machines, too

3.3.14

Apr 22, 2010

Update

Fixed .NET CF deployment problem for 32-bit machines (fix for 64-bit will follow)

3.3.13

Apr 21, 2010

Update

The 3.3.6 profiler-installation was missing a component, so it would not start at all if Visual Studio was either missing or older than VS2008
Improved handling of mixed .NET and Silverlight assemblies

3.3.6

Apr 21, 2010

Release 3.3

New license terms: now free for commercial and company use!
New license terms: professional/corporate license now needed for .NET CF apps!
Deploy and run .NET CF apps simply by pressing "Run app"
Slightly improved Silverlight webpage detection on x64 systems
Slightly simplified and improved troubleshooting-options
Comes with two demo-apps, both full .NET and CF
No longer clears entire output-folder if it's different from $(AppDir)
Cannot profile remotely anymore; profiled app now connects to the profiler

3.2.38

Mar 26, 2010

Update

Proper handling of custom attributes that are arrays
Two-level namespace/class info now visible in Silverlight demo-mode

3.2.28

Mar 18, 2010

Update

Dynamically-loaded assemblies failed at runtime if nothing else was profiled
No more (harmless) thread/socket-errors in profiler.log at app shutdown

3.2.23

Mar 16, 2010

Update

Thousand-separator could be printed as "un-printable" (a square glyph)
Right-click on method-box can now copy only method-name, too, to clipboard

3.2.18

Mar 12, 2010

Update

Runtime-module is now always signed, as removing the strong-name could cause unresolved references at runtime
Use thin space as thousand-separator instead of comma
Also accept drag-drop of exe/dll files from app instead of just folders

3.2.8

Mar 4, 2010

Update

Fix: IIS-hosted Silverlight webpages had incorrect root-url when started
Improvement: Now handle all various releases of .NET 4.0 (VS2010 SP2 etc)

3.2.4

Mar 3, 2010

Update

Fix: Could fail to locate Silverlight testpage.html pages
Fix: Certain RootUrls could abort Silverlight webpage scanning
Fix: Remove any existing runtime-module reference to avoid instrumented assemblies with duplicate signed/unsigned references (very rare)
Change: Improved detection of default browser

3.2.1

Mar 1, 2010

Release 3.2

A few internal improvements and global announcement of Silverlight profiler.

3.1.65

Feb 26, 2010

Update

Improved Silverlight webpage-detection algorithm and logging; see the FAQ.

3.1.59

Feb 23, 2010

Update

Fix: Could hang on some 64-bit machines when pressing the Run-tab or "Run app"-button.

3.1.47

Feb 19, 2010

Update

Fix: Profiled app could crash with a timer-exception on some WinCE-platforms

3.1.39

Feb 12, 2010

Update

Fix: Improved strategy for locating Silverlight hosting webpages to run
Fix: Profiled files were removed when re-profiled if backup (eqbak) was missing
New: Added "profiler options" with verbose build/run messages for troubleshooting

3.1.33

Feb 9, 2010

Release 3.1

Profile Silverlight applications. Only available with professional/corporate license.
Now works directly on input-files instead of copying everything to another folder.
Minor improvements, like right-click to copy method-name to clipboard etc.

3.0.68

Nov 25, 2009

Update

.NET 4.0 Beta 1 assemblies are now accepted
Runtime-module now also unsigned if all assemblies are unsigned
"New version available"-box will only appear once per new version
Better diagnostics for failing runtime-module

3.0.46

Nov 11, 2009

Release 3.0

• Compare profiling reports

• Profiled apps now run faster
• Support for .NET 4.0 applications
• Better timing of recursive methods
• Export reports as plain text to file (csv)
• Full method signature is now shown in report
• New license terms, introducing paid editions

2.0.89

Feb 11, 2009

Update

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

Release 2.0

• 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

• 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

Update

• 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

Update

• 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

Release 1.2

• Focus on making it easier to profile full .NET applications:
• Profiling now build a full recursive copy of the application’s folders
• 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
• 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

Release 1.1

• 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

Release 1.0