Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Diagnostics   (RSS)

.NET Compact Framework v3.5 Power Toys Released!

I've been meaning to post this for the last week...  The .NET Compact Framework v3.5 Power Toys have officially been released.  You can download the Power Toys from here . See the .NET Compact Framework Team weblog for details on the included
Posted by DavidKlineMS | 1 Comments
Filed under:

CoreCon API: Brought to you by the Visual Studio for Devices team

The Visual Studio for Devices team has been posting a very interesting and informative series on the CoreCon API.  I highly encourage anyone interested in writing remote tools to read the series.  In fact, I recommend everyone interested in
Posted by DavidKlineMS | 1 Comments
Filed under:

Steven Pratschner on the CLR Profiler for the .NET Compact Framework

I love tools.  Debuggers , analyzers, performance monitors, profilers, everything.  In version 1 of the .NET Compact Framework, the only available tools where the Visual Studio debugger and the performance counter data file (also known as the
Posted by DavidKlineMS | 1 Comments
Filed under:

.NET Compact Framework v3.5 Power Toys CTP

The .NET Compact Framework team made an exciting CTP available this week.  The .NET Compact Framework v3.5 Power Toys September 2007 CTP release contains some old friends (ex: Remote Performance Monitor) and ads some great new ones (Service Model

Using the .NET Compact Framework Remote Performance Monitor to Configure Diagnostic Options

Diagnostic, performance and debugging tools are very cool. The more tools available, the easier it tends to be to find and fix application issues. With Visual Studio 2005, several handy tools were added. I use the Remote Registry Editor and Remote File

The Error Log: A New Diagnostic in .NET Compact Framework v2 Service Pack 1

The recent release of Service Pack 1 for the .NET Compact Framework version 2 has added some very useful diagnostic tools. You may have already read about the .NET Compact Framework Remote Performance Monitor , and have hopefully used it to analyze the

Using the Interop Log to Diagnose P/Invoke Call Issues

Sometimes, determining why an unmanaged function call (P/Invoke) has failed can be challenging. Fortunately, version 2 of the .NET Compact Framework has a new diagnostic log for this data -- the Interop Log. In June 2005, Steven Pratschner wrote a great

Diagnosing MissingMethodExceptions and TypeLoadExceptions using the Loader Log

Have you ever encountered a MissingMethodException or TypeLoadException when starting a .NET Compact Framework application? If you are running version 2 of the .NET Compact Framework, the Loader Log can help identify the source of the exception. For detailed
 
Page view tracker