Microsoft Windows SDK Blog : Tools

Using SecAnnotate to Analyze Your Assemblies for Transparency Violations

wsdkblog@microsoft.com — Fri, 20 Nov 2009 17:52:36 GMT

SecAnnotate can be used to analyze your assemblies, especially APTCA assemblies in order to find transparency violations without needing code coverage from a test case. The static analysis provided by SecAnnotate is valuable in ensuring that your assembly is fully correct from a transparency perspective. You can get the tool now in beta form here, and read an in-depth article on the .NET Security Blog about how this tool might be used for a simple APTCA library.

Karin Meier-Magruder
Program Manager

Win SDK Hidden Gems: Function Discovery Browser (fdbrowser.exe)

wsdkblog@microsoft.com — Mon, 12 Oct 2009 19:49:58 GMT

The Function Discovery API, introduced in Vista, serves as an abstraction layer between applications and devices. This API allows applications to discover devices by function rather than lower level details such as bus or connection type.

The Function Discovery Browser is a utility that displays information about devices in your local machine and connected via the network.

Its primary purpose is to assist driver and hardware developers to verify that programs accessing the Function Discovery API and hardware registering its attributes with the Function Discovery API are doing so correctly.

Layered categories are the namespaces of the abstract device types programmers would want to access.

Provider categories are namespaces of device and driver registrations.

For more information:

Using the Function Discovery Browser.

Function Discovery Overview.

The Function Discovery Browser may be found in the Windows SDK for Windows 7 default install location of "C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin\fdbrowser.exe"

Curtis Smith
Developer
Windows C++ Team

Send your thoughts to the Windows SDK Feedback alias. Tell us how you use the SDK and what we can do to improve your development experience.

The MSDN Windows SDK Developer Center is the place to find resources and links to Windows SDK products, release notes, technical articles, and more.

New Tools in Windows SDK for Windows 7

wsdkblog@microsoft.com — Tue, 14 Jul 2009 03:06:00 GMT

The upcoming release of the Windows SDK for Windows 7 and .NET Framework 3.5 SP1 contains many new tools, some of which are brand new, some which are being reintroduced into the SDK and some of which are being made available via the SDK for the first time. These tools will be found under %ProgramFiles%\Microsoft SDKs\Windows\v7.0\bin unless otherwise noted below. Look for upcoming blog posts to describe a few of these in more detail.

File Name

(Tool Name)

Description

AccEvent.exe

(Accessible Event Watcher)

Validates that the user interface (UI) elements of an application raise proper Active Accessibility events when the UI changes.

AppVerif.exe

(Application Verifier)

Finds subtle programming errors that can be extremely difficult to identify with normal application testing.

Note: when selected this program installs in its own directory under %ProgramFiles%

DeviceSimulatorForWindowsSideShow.msi

(Device Simulator for Windows SideShow)

Tests gadgets for Windows SideShow device without need for physical hardware.

Note: This replaces WindowsSideShowVirtualDevice.exe

FileFormatVerifier.exe

(File Format Verifier Tool)

Checks properties, IFilters, and other settings to ensure a file format will register correctly with Windows 7.

FTQuery.exe

(FTQuery Tool)

Verifies and tests the query functionality of the Windows Search Service.

FiltDump.exe

(IFilter Dump)

Loads an IFilter interface implementation for a specified document and prints the output produced by the filter DLL.

FiltReg.exe

(IFilter Registy)

Inspects IFilter installation information in the registry.

IFiltTst.exe

(IFilter Test Tool)

Runs several tests to validate an IFilter interface implementation.

Inspect.exe

(Inspect Objects Tool)

Examines the IAccessible property values of the user interface (UI) items of an application and navigates to other objects.

PKTExtract.exe

(Public Key Token Extractor Tool)

Extracts the publicKeyToken attribute from a certificate file. The output is the publicKeyToken, which is a unique 16-character (8-byte) identifier of the public key present in the certificate, in a format that can easily be pasted into an assembly identity statement.

SDMC.Exe

(SDMC Tool)

SDMC is used by Windows Troubleshooting Pack Designer to compile and validate Windows Troubleshooting Packs.

Note: This tool is found under the TSPDesigner subfolder

TSPDesigner.exe

(Windows Troubleshooting Pack Designer)

Assists users in creating Windows Troubleshooting Packs.

Note: This tool is found under the TSPDesigner subfolder

UICC.exe

(Ribbon Markup Compiler)

Generates a binary version of the Ribbon markup, an ID definition header file that exposes markup elements to the Ribbon host application, and a resource file that is used to link the binary markup to the host application at build time.

UISpy.exe

(UI Spy)

Enables developers and testers to view and interact with the user interface (UI) elements of an application. By viewing the application's UI hierarchical structure, property values, and raised events, developers and testers can verify that the UI they are creating is programmatically accessible to assistive technology devices such as screen readers.

VirtualLightSensor.exe

(Virtual Light Sensor Tool)

Tests gadgets designed for light sensor devices without the need for physical hardware.

VSSTrace.exe

(VSSTrace Tool)

A command line tool that collects tracing information for the Volume Shadow Copy Service infrastructure.

WinDbg.exe

(Debugging Tools for Windows)

Assists in debugging drivers, applications, and services. Can also be used to debug Windows itself.

Note: when selected this program installs in its own directory under %ProgramFiles%

WSTraceDump.exe

(Web Services Trace Dump Tool)

Assists with the analysis of web services trace dumps.

WSUtil.exe

(Web Services Compiler Tool)

Supports service model and serialization of data types. It processes WSDL, XML schema and policy documents. It generates C header and source files. This tool is similar to wsdl compiler tool for managed code with target to native code instead of managed code.

wpt-x86.msi

wpt-x64.msi

wpt-ia64.msi

(Windows Performance Toolkit)

A suite of tools to help capture and analyze traces.

Note: Formerly called xperf_x86.msi, xperf_x64.msi and xperf_ia64.msi

Lisa Rugen

Program Manager for Tools

Windows SDK Team

WinSDK Files That Shipped with Visual Studio 2008: Tools

wsdkblog@microsoft.com — Mon, 02 Mar 2009 19:24:00 GMT

Did you ever wonder what Windows SDK tools, headers, libraries, and reference assemblies are included in the different Visual Studio 2008 SKUs? These Windows SDK components are embedded in all Visual Studio 2008 SKUs. If you are looking for a particular file, you may not need to install a separate Windows SDK to get the content you need.

This table shows which tools shipped in each Visual Studio 2008 SKU. This could save you valuable time when deciding which Visual Studio 2008 SKU is right for the project you are working on. If you are looking for one specific tool to build your application, check here to find which VS SKUs it shipped in.

A future post will list the Windows headers and libraries that shipped in the Visual Studio 2008 SKUs, and another post will list the reference assemblies and Intellisense that shipped in Visual Studio 2008 SKUs.

Click here to open a list of the .NET Framework and Windows Tools in Visual Studio 2008

· “VS STD” includes all Visual Studio Retail (non-Express) products (Pro, VSTS, etc.).

· All files install by default to [ProgramFiles]\Microsoft SDKs\Windows\v6.0A on an X86 computer, or to [ProgramFiles]Microsoft SDKs\Windows\v6.0A\X64 on an X64 computer

Windows SDK Hidden Gems Part 3: TcpAnalyzer.exe and Consume.exe

wsdkblog@microsoft.com — Fri, 04 Jul 2008 01:47:00 GMT

I’ve been writing about some of the useful but sometimes overlooked tools in the Windows Software Development Kit for Server 2008 and .NET Framework 3.5. For this installment, let’s have look at couple of tools that are related in that they are both used for testing. Check out my other ‘hidden gems’ posts, Part 1: Windows Installer Verbose Log Analyzer and Part 2: XAMLPad.

TcpAnalyzer.exe

Your new application works great most of the time, but it inexplicably pauses for long periods of time. You suspect that it might be the connection to the backend server. TcpAnalyzer.exe is the tool to use to figure out what’s going on.

The tool displays a constantly updating list of all network connections in and out of your machine.

It allows you to zero in on a particular connection and log performance information for that connection.

It gives you the information needed to pin down network related delays or unexpected high traffic that might be slowing the network connection.

Consume.exe

This command line tool can consume system resources for a specified amount of time and is useful for reproducing errors that might be caused by resource starvation.

The resources it can consume include physical memory, page file space, disk space, kernel pool, and CPU time.

As an example, start Windows Task Manager (Start->Run->taskmgr.exe) and select the Performance tab. Next, open the Windows SDK CMD window (Start->All Programs->Windows SDK v6.1->CMD Shell) and enter the following “consume.exe -cpu-time -time 15”. You’ll see the CPU Usage History chart(s) climb to maximum for 15 seconds.

For other options use “consume.exe /?”

In closing…

These are just two of the many tools included in the Windows Software Development Kit for Server 2008 and .NET Framework 3.5. A summary of the tools included with the Windows SDK can be found at C:\Program Files\Microsoft SDKs\Windows\v6.1\Bin\StartTools.htm, which can be also be launched from a shortcut key on the Start Menu.

I will keep hunting for gems and report them here.

Cheers
Curtis

The MSDN Windows SDK Developer Center is the place to find resources and links to Windows SDK products, release notes, technical articles, and more.

Integrating Windows SDK and VS with new SDK Configuration tool

wsdkblog@microsoft.com — Sat, 01 Mar 2008 07:29:00 GMT

This article describes the use of the Windows SDK Configuration tool, which is included in the Windows SDK for Windows Server 2008 and .NET Framework 3.5 and works with Visual Studio 2005 and Visual Studio 2008, including Visual Studio 2008 Express SKUs.

A serious bug has been discovered with the Windows SDK Configuration Tool. This bug is not apparent as the tool appears to work correctly. Please read the blog post WinSDK bug notification: SDK Config Tool appears to work but fails, to learn more about the issue and find workaround steps.

What is the Windows SDK Configuration tool for?

The Windows SDK for Windows Server 2008 and .NET Framework 3.5, released in February, 2008, includes a new tool to help you develop more easily with Visual Studio. You can use this tool to set which version of Windows SDK headers, libraries and tools you want to build with in Visual Studio.

The Visual Studio 2008 editions are seamlessly integrated with the Windows SDK. VS2008 editions include the same Vista RTM headers and libraries that shipped in the Microsoft Windows Software Development Kit Update for Windows Vista released in March, 2007. (The SDK tools in VS2008 are more recent.) You can use these integrated Windows Vista headers and libraries right out of the box with Visual Studio 2008. If you want to use the content in another Windows SDK, the SDK Configuration Tool will allow you to do just that, by setting which SDK is the ‘current’ SDK to build with.

Updating the Windows SDK Content in Visual C++2008

You can build Win32 applications right out of the box with the Vista RTM SDK components that are embedded in Visual Studio 2008. It’s also easy to switch to the more recent components that ship with the Windows SDK for Windows Server 2008 and .NET Framework 3.5 by installing this SDK on your computer. If you install the SDK after you installed VS, you are ready to develop with the headers, libraries and tools in the SDK for Windows Server 2008. If you installed the Windows Server 2008 SDK before you install Visual Studio, you will need to use the SDK Configuration Tool to set the directories.

Windows SDK headers, libraries and tools

After installing the Windows SDK for Windows Server 2008 and Visual Studio 2008 (any SKU), you’ll have two sets of SDK resources installed by default to C:\Program Files\Microsoft SDKs\Windows\:

· \v6.0A contains the SDK resources installed by Visual Studio 2008

· \v6.1 contains the SDK resources installed by the Windows SDK for Windows Server 2008

Visual Studio 2008 will point to v6.0A headers, libraries and tools, which installed with VS by default. Use the SDK Configuration Tool to update the Visual C++ directories to point to the v6.1 headers, libraries and tools that shipped with the Windows SDK for Server 2008.

How does the SDK Configuration Tool work?

The tool works by altering the Visual Studio 2008 directories through a registry key setting. (The tool works differently with Visual Studio 2005. This will be covered in a future post.)

· On an X86 computer: HKLM\SOFTWARE\Microsoft\Microsoft SDKs\Windows

· On an X64 or IA64 computer: HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Windows

The settings “CurrentVersion” and "CurrentInstallFolder" refer to the version and location of the registered Windows SDK headers, libraries and tools. These settings get updated during Windows SDK installation or when the Windows SDK Configuration Tool is used to choose which Windows SDK content users want to use with Visual Studio 2008.

SubKey	Window SDK Version
V6.0	Windows SDK for Windows Vista and Windows SDK for Windows Vista Update
V6.0A	Windows SDK Visual Studio Components
V6.1	Windows SDK for Windows Server 2008

Visual Studio 2008 looks at this key to determine how to set the following directories:

· Visual Studio Library Directory sets the paths to use when searching for library files while building a VC++ project. It corresponds to environment variable LIB.

· The Visual Studio Include Directory sets the paths to use when searching for include files while building a VC++ project. It corresponds to environment variable INCLUDE.

· The Visual Studio Executables Directory sets the path to use when searching for executable files while building a VC++ project. It corresponds to environment variable PATH.

The VC++ 2008 Library, Include and Tool path are set upon install to the Windows SDK content that ships embedded with Visual Studio 2008. If you want to change these paths you can do so manually through Visual Studio, or use the SDK Configuration Tool to set these directories.

The SDK Configuration Tool has a GUI interface that works with the Visual Studio Retail (non-Express) SKUs, and a command line interface that works with either the VS Retail or Express SKUs. (See Using Visual C++ 2008 Express with the Windows SDK for more information on working with Visual Studio Express.)

How to use the SDK Configuration Tool in GUI mode

To launch the SDK Configuration Tool GUI interface, go to Start, All Programs, Microsoft Windows SDK v6.1, Visual Studio Registration, Windows SDK Configuration Tool.

Use the drop box to pick which version of SDK content you want to integrate with Visual Studio, and click Make Current.

How to use the SDK Configuration Tool at the command line

The SDK Configuration Tool can be used with either the GUI or command line interfaces with Visual Studio 2005 Retail or Visual Studio 2008. The tool can only be used at the command line for Visual Studio 2008 Express SKUs. (See Using Visual C++ 2008 Express with the Windows SDK.)

1. Launch the Windows SDK Command Window (Start, All Programs, Microsoft Windows SDK v6.1, Command Window)

2. CD to \Program Files\Microsoft\Windows\v6.1\Setup>

3. Type: WindowsSdkVer.exe -version:v6.1

This will set the Windows SDK for Windows Server 2008 (v 6.1) as the “current” SDK for Visual Studio to use for headers, libraries and tools.

How to validate that Visual Studio Directories were successfully updated

Open the Visual Studio command window and check the PATH to see if the v6.1 directory has been added:

1. Start, All Programs, Visual C++ Express Edition 9.0, Visual Studio Tools, Visual Studio 2008 Command Prompt

2. At the prompt, type: PATH

How to Switch back to the SDK content that shipped ‘in the box’ with Visual Studio 2008

To restore the default directories, use the SDK Configuration Tool at the command line to make the v6.0A directories ‘current.’

1. Launch the Windows SDK Command Window (Start, All Programs, Microsoft Windows SDK v6.1, Command Window)

2. CD to \Program Files\Microsoft\Windows\v6.1\Setup>

3. Type: WindowsSdkVer.exe -version:v6.0A

Troubleshooting:

After Visual Studio Repair, environment variables are reset. If Visual Studio is Repaired (through Add/Remove Programs), the environment variables will point back to the default VS content. You will need to use the SDK Configuration tool if you want to point to the content in the Windows Server 2008 SDK.

After Windows SDK Repair, environment variables are reset. If the Windows SDK is ‘Repaired’ (through Add/Remove Programs), the environment variables will point to Windows SDK content. You will need to use the SDK Configuration tool if you want to point to the content that shipped with Visual Studio 2008.

Please send feedback on this tool.

The MSDN Windows SDK Developer Center is the place to find resources and links to Windows SDK products, release notes, technical articles, and more.

Speech Content in the Windows SDK

wsdkblog@microsoft.com — Wed, 27 Feb 2008 21:23:00 GMT

Charles Oppermann on the Speech team wrote a post on the new Speech-related content that ships in the recently released Windows SDK for Windows Server 2008 and .NET Framework 3.5. The content in this new Windows SDK completely replaces the older SAPI 5.1 SDK and supports development on Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008.

Where is UISpy.exe?

wsdkblog@microsoft.com — Tue, 19 Feb 2008 01:29:00 GMT

The UI Spy tool did not ship in the Windows SDK for Windows Server 2008 and .NET Framework 3.5, released February, 2008. We’re working to get this great tool back into the next SDK release. If you need UISpy, you can find it in the earlier Windows SDK for Vista Update. If you don’t want the entire SDK on your computer, you can download just the .NET Framework Tools from the Windows SDK for Vista Update.

Update: UISpy.exe has been reintroduced into the Windows SDK for Windows 7 and .NET Framework 3.5 SP1.

Caution: if you have Visual Studio 2008 installed, installing Windows SDK side by side on the same computer will affect your Visual Studio 2008 installation. Different versions of SDKs are designed to work side by side but a partial install of SDK may cause problems. Here’s why:

After installing the Windows SDK you will have one set of SDK resources for each SDK installed, located under \Program Files\Microsoft SDKs\Windows:

· \Program Files\Microsoft SDKs\Windows\v6.1\ – resources installed by Windows SDK for Windows Server 2008 and .NET Framework 3.5

· \Program Files\Microsoft SDKs\Windows\v6.0A\ – resources installed by Visual Studio 2008

· \Program Files\Microsoft SDKs\Windows\v6.0\ – resources installed by Windows SDK for Vista Update (the \Bin directory here will have the tool set that includes UISpy.exe)

The Visual Studio 2008 IDE and some environment variables used by MSBuild are directed to the location of the last installed version of SDK to find Windows headers and libraries, and tools. This happens because the last installed SDK updates the "CurrentInstallFolder" value under the following registry keys to point to the last installed SDK location:

On an X86 machine:

· HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows

· HKEY_CURRENT_USER\Software\Microsoft\Microsoft SDKs\Windows

On an X64 or IA64 machine:

· HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows

· HKEY_CURRENT_USER\Software\Microsoft\Microsoft SDKs\Windows

· HKEY_LOCAL_MACHINE \SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Windows

· HKEY_CURRENT_USER \SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Windows

If you wish to change the version of SDK resources that Visual Studio uses, you will need to update this registry key to point to the location of the SDK resources installed by Visual Studio (v6.0a). This can be done using the ‘SDK Configuration Tool’. More details about ‘SDK Configuration Tool’ can be found here and here. Advanced users with sufficient experience can update this registry key using regedit. Please review http://support.microsoft.com/kb/256986 before making any changes to your registry.

What is UISpy? The UI Spy tool enables developers and testers to view and interact with the user interface (UI) elements of an application. By viewing the application's UI hierarchical structure, property values, and raised events, developers and testers can verify that the UI they are creating is programmatically accessible to assistive technology devices such as screen readers.

Sumit Kumar

Tools Program Manager

Windows SDK Team

Windows SDK Hidden Gems: Part 1

wsdkblog@microsoft.com — Sat, 26 Jan 2008 23:51:00 GMT

Windows Installer Verbose Log Analyzer (WiLogUtl.exe)

I, like many before me, have downloaded the Windows SDK, installed it, and moved on to more pressing problems. Other than digging into header files, I had rarely looked at what else might be included. As the builder of the SDK, I now have a vested interest in what is delivered with the SDK, and I thought I'd share some of the interesting jewels I've found.

Installed by default to “C:\Program Files\Microsoft SDKs\Windows\[version number]\Bin\WiLogUtl.exe”, the Windows Installer Verbose Log Analyzer is a tool to assist in identifying most critical installer errors, and offer possible solutions to those errors. This tool is available in the standalone Windows SDKs and in the Windows SDK components that ship in Visual Studio 2008.

Upon launching the tool, the user is presented with a history of past logs viewed and a preview of the latest log.

Installer log files are usually stored in the user’s temp folder. A quick way to find installer logs is to press the ellipsis (…) button, type %temp% in the file name entry, then press enter. The preview is invaluable for identifying log files when you have a directory full of MSI[random char].LOG files.

After loading the log file, just press Analyze. You will be presented with a dialog that breaks out errors, possible solutions, client and server side details, and allows you to view particulars about the install such as states, properties, and policies. There is also an html view of the log available that color codes all lines into various categories, making the file much easier to read.

The detailed log file view allows you to cycle through individual errors without slogging through an entire installer file. Additional windows display the machine states at the time of the install, view machine and user policies, or look at the properties the MSI is using. Properties are the equivalent of variables in programming.

Additionally, there is an option to view a color coded version of the log in your browser. There are also options to get more information about a particular error, and a brief walkthrough on how to read an installer log file.

You can also run the tool in quiet mode from a command line. This article on MSDN details the command line options to do so.

In coming months, I will be presenting more of these hidden gems. Hopefully, I can find one that will make your life easier one day.

Cheers,

Curtis

Windows SDK Builder

SDK Workaround: Guidgen.exe fails to execute, use UUIDgen.exe

wsdkblog@microsoft.com — Tue, 18 Sep 2007 19:15:00 GMT

This workaround applies to:

· The prerelease Windows SDK for Windows Server 2008 and .Net Framework 3.5 (RC0), September, 2007

· The prerelease Windows SDK for Windows Server 2008 and .Net Framework 3.5 (IDS04), July, 2007

Guidgen.exe fails with the following error:

System.ComponentModel.Win32Exception: The application has failed to start because its side-by-side configuration is incorrect.

Workaround: use the tool Uuidgen.exe to generate GUIDs from the command prompt. Run the following command:

%ProgramFiles%\Microsoft SDKs\Windows\v6.1\bin\Uuidgen.exe

For help with this tool, type: uuidgen.gen /?

FxCop wins Chairman's Award for Engineering Excellence

wsdkblog@microsoft.com — Sat, 28 Jul 2007 00:06:00 GMT

Microsoft’s prestigious Engineering Excellence Chairman's Award was awarded to Mike Fanning, Krzysztof Cwalina, and Brad Abrams for the design of FxCop, which ships in the Windows SDK, as a standalone tool and in Visual Studio 2005 and later.

The Chairman’s Award is given for contributions that Bill Gates considers extremely important and has been given only twice in Microsoft’s history (until this year, the only other winner of the Chairman's award was Dr. Watson). Krzysztof and Brad have more information about the award and the development of FxCop on their blogs.

FxCop is a code analysis tool that checks .NET managed code assemblies for conformance to the Microsoft .NET Framework Design Guidelines. FxCop includes both GUI and command line versions. It uses reflection, MSIL parsing, and callgraph analysis to inspect assemblies for many defects.

Send the Windows SDK Team Your Thoughts

wsdkblog@microsoft.com — Thu, 26 Jul 2007 20:35:00 GMT

Do you have feedback for the Windows SDK? We want to hear from you. Email your feedback to us. The Windows SDK provides all of the necessary headers, libraries, and tools needed to build Windows applications that make use of the Win32 API set and the .NET Framework, and includes samples to illustrate the technologies for those platforms. What do you like? What do you dislike? What should we change next time?