New Windows SDK Available to Download


It has been barely 3 months since we shipped the previous Windows SDK prerelease; and here we are today shipping another prerelease version of the Windows SDK.  This SDK coincides with the release of Microsoft® Visual Studio® 2008 Beta2 and Microsoft® .NET Framework 3.5 Beta2.  If you want to be on the cutting edge of .NET Framework 3.5 development, this SDK is for you.  Our SDK even has a catchy new name, the Windows SDK for Windows Server® 2008 and .NET Framework 3.5.


 


Here’s a quick rundown of what’s new in this SDK:


·         The latest set of documentation and samples for .NET Framework 3.5 development. 


·         New and updated tools for .NET Framework 3.5 development


·         A new C++ compiler and associated CRT


·         This SDK will install side-by-side with Microsoft® Visual Studio® 2008 Beta2.


 


As was the case with our previous prerelease SDK, this SDK is compatible with the RTM release of Microsoft® Visual Studio® 2005 SP1 and the Microsoft® Visual Studio® Express Editions, which are available to download, free of charge.


 


As always, we strongly recommend reading the Release Notes for a description of known issues with this SDK.  A few items worth calling out are the following:


·         To take advantage of .NET Framework 3.5 features, such as new samples or tools, you’ll need to install the Microsoft® .NET Framework 3.5 Beta2


·         If you want to use Microsoft® Visual Studio® 2005 with existing SDK C++ samples you can.  If you want to take advantage of and try out the latest C++ command line compiler that ships in this SDK on those same samples, you’ll need to upgrade those sample projects as described in the Release Notes.


·         This release of the SDK is an ISO-only download.  This means that you will need to download the entire ISO and then either burn it to a DVD to use in your local DVD drive, mount it virtually as if it were another drive, or copy the contents locally, in order to run the SDK’s setup.exe.  More details about how to work with the DVD ISO image can be found at the download page for the SDK


 


We encourage you to install this SDK on a test machine and let us know what you think.


 


Barry Butterklee


Windows SDK Release PM


barrybu@microsoft.com


 

Comments (5)

  1. TiKu says:

    I’m missing Spy++ and Dependency Walker. Aren’t they included in Windows SDK anymore or am I just too dumb to find them?

  2. Brian Cost says:

    Hi TiKu,

    I do not believe we have shipped Spy++ in the recent past in the Windows SDK.

    Dependency Walker was removed sometime back. It can be downloaded easily from http://dependencywalker.com

    Thanks,

    Windows SDK

  3. bwknight877 says:

    I believe the SetEnv.cmd batch file is broken in C:Program FilesMicrosoft SDKsWindowsV6.1Bin

    I tried the previous pre-release of the SDK (v6.0A) and had the same issue.

    Many of the paths are set using exclamation points around the path variable names instead of percents.  When you run the command, the PATH environment variable is broken.  

    Here is what I get after running the command:

    Path=C:Program FilesMicrosoft SDKsWindowsV6.1VCBin;C:Program FilesMicrosoft SDKsWindowsV6.1Bin;C:WINDOWSMicrosoft.NETFrameworkv2.0.50727;!Path!

    The !Path! at the end should include the original contents of my path variable.  These exclamation points are all throughout the SetEnv.cmd file, and NONE of those work to expand the system environment variables correctly.

    After installing the SDK on my Windows Server 2003 R2 x86 system, I have had to edit the SetEnv.cmd file to change all of the exclamation points to percent symbols.  After making that change, the SetEnv.cmd file works as it should.  

    What system environment or command processor does this batch with file work in?  It most certainly does not work on any system that I use for development without editing it first.

    This needs to be fixed for the final release of the SDK.

    Thanks,

    – BK

  4. bwknight877 says:

    Our automated build process launches the cmd.exe from the COMSPEC variable, which has no parameters on it.  

    Thanks to a quick reply from a few of the SDK folks, I have a solution:

    You must enable delayed environment variable expansion for the CMD session by using the CMD /V:ON switch, or by issuing a setlocal ENABLEDELAYEDEXPANSION command.

    Also info from running cmd.exe /?

    Delayed environment variable expansion is NOT enabled by default.  You

    can enable or disable delayed environment variable expansion for a

    particular invocation of CMD.EXE with the /V:ON or /V:OFF switch.  You

    can enable or disable completion for all invocations of CMD.EXE on a

    machine and/or user logon session by setting either or both of the

    following REG_DWORD values in the registry using REGEDT32.EXE:

       HKEY_LOCAL_MACHINESoftwareMicrosoftCommand ProcessorDelayedExpansion

           and/or

       HKEY_CURRENT_USERSoftwareMicrosoftCommand ProcessorDelayedExpansion

    to either 0x1 or 0x0.  The user specific setting takes precedence over

    the machine setting.  The command line switches take precedence over the

    registry settings.

    If delayed environment variable expansion is enabled, then the exclamation

    character can be used to substitute the value of an environment variable

    at execution time.

    (I hope this is useful to more people out there)

  5. The LIB-environment variable is missing a back-slash variable in the VC-path. Also curious about the !Lib! thing.

    LIB=C:Program FilesMicrosoft Visual Studio 9.0Lib;C:Program FilesMicrosoft S

    DKsWindowsv6.1Lib;!Lib!