13 September 2007

Power Toys for .NET Compact Framework 3.5 CTP (September 2007)

The Power Toys for .NET Compact Framework 3.5 CTP provides a early preview of several tools for evaluating performance, obtaining diagnostic information, configuring and working with the .NET Compact Framework.

Tools included in this package:

Remote Performance Monitor and GC Heap Viewer – Provides real time counter data (ranging from Garbage Collector activity to type loading info) on a running NETCF application. The GC Heap Viewer feature allows you to capture the managed heap at any moment your app is running to view live references, and allows you to compare multiple snapshots to find memory leak issues.

NETCF CLR Profiler – CLR Profiler is an instrumenting allocation profiler for NETCF applications. It provides detailed allocation visualizations, allocation callstacks visualizations and useful for diagnosing memory management issues.

App Configuration Tool (NetCFcfg.exe) - On-device tool for specifying what version of the NETCF runtime an application will run against, displaying installed versions of NETCF and displaying info about DLLs in the GAC.

NETCF ServiceModel Metadata Tool – The .NET Compact Framework ServiceModel Metadata Tool (netcfsvcutil.exe) allows you to generate a Windows Communication Foundation (WCF) client proxy to help developers consume WCF services on device. Like svcutil.exe, which is the desktop version of the utility, netcfsvcutil.exe is a command-line tool that generates service model code from metadata documents and generates metadata documents from service model code.

Remote Logging Configuration Tool – The Logging Configuration Tool enables users to easily configure logging options on a NETCF device including: loader, interop, network, error and finalizer logs.

NETCF Network Log Viewer – A utility for viewing NETCF network log data.

Known Issues: These tools are a pre-release to the community for early feedback. Currently known issues are listed here for your reference:
  • CLRProfiler: failure to get heap dump at around 160000 live objects
  • CLRProfiler: error interpretting the profiler log data: Index is invalid
  • CLRProfiler: Error parsing data in profdev.raw file when app call stack is 4000 calls deep
  • CLRProfiler: “Unhandled exception, Cannot access a disposed object” sometimes occurs on second or third click of “Show Heap Now”
  • CLRProfiler: Error loading profiling log. The results may be inaccurate after a completed app run
  • GC Heap Dump doesnt work with emulators
  • CLRProfiler: “Exception, value too large or too small for an unsigned int” when opening heap view window via “Show Heap Now” for the second time
  • CLRProfiler: Unhandled exception when trying to view individual items in heap dump at around 1600 objects
  • CLRProfiler: Unexpected exception: failure to dump heap when allocations are not profiled (ie. Profile it with allocations is unchecked)
  • CLR Profiler: Sporadic Index out of range error when callstack is deeper than 500 calls
  • Remote Performance Monitor Heap dump: While getting heap dump 'view gc heap' button should be grey
  • CLRProfiler: root node in dumps has a incorrect painting in some cases
  • CLRProfiler: long operations need hour glass or progress bar like when expanding a large cal tree
  • Heap dump: confusing 'cycle' line in ObjectReferences view
  • Killing app in CLR profiler won't kill the app on the attached device
  • CLRProfiler: deleting logs not belonging to this session when running multiple instances of the CLR Profiler
  • CLRProfiler: unable to prune heap dump view if looking at individual instances
  • CLRProfiler: call graph: zoom to node looks wrong (caller should not show 0 callees when it has callees)
  • CLRPRofiler: Goto tree view and then view -> All functions, then try to click on the name tab in the new window, functions should be sorted but are not
  • CLRProfiler: Unable to move nodes when call graph window is expanded to a big monitor
  • NETCF App Config Tool : Should validate if the file entered exists before trying to create the app.config file instead of failing
  • CLRProfiler: module graph looks wrong
  • CLRProfiler: generic types don’t show actual parameter types
  • CLRProfiler: comparing two identical logs gives an error and so does cancelling a comparison

Bookmark and Share ITStuff.ca

No comments:

Post a Comment