Welcome to the Microsoft Windows Bundle Outgrowth Kit (SDK) for Windows 7 and.NET Cloth 3.5 Process Coterie 1.-p

The Windows SDK contains a set of tools, aught samples, documentation, compilers, headers, and libraries that developers can use to develop applications that run on Microsoft Windows. You can use the Windows SDK to pen applications using the indigene (Win32-COM) or managed (.NET Textile) scheduling form.-p

For accession to redundant resources and information, such as downloads, forum posts, and the Windows SDK team blog, see the Windows SDK Developer Essence.-p

1.1 Recommended Resources-h2

This release of the Windows SDK does not intromit a.NET Modeling Redistributable Package. Windows 7 includes.NET Framework 3.5 SP1. Windows Aspect and Windows Horde 2008 accommodate.NET Cloth 3.0.-p

Users functional Windows Server 2003 and Windows XP mustiness establish the.NET Simulation 3.0 or 3.5 SP1 to run and develop.NET Modelling applications. Approximately samples and tools included in the Windows SDK also need you to base.NET Textile 3.5 SP1.-p

On with issue that ships in the Windows SDK, Microsoft offers spare dissolve developer tools and resources that you power find helpful, including:-p

· LUA Buglight™ is a prick to supporter both developers and IT professionals (sysadmins) key the especial causes of admin-permissions issues (LUA bugs) in ground applications operative on Windows XP, Windows Server 2003, or Windows Prospect. Erstwhile the exceptional causes birth been identified, the bugs can more light be resolved by hangout the app’s origin cypher, or by making contour changes, allowing the app to ferment correctly for non-admin users.-p

· Microsoft.NET Simulation 3.5 SP1 is the latest update of the.NET Textile, and contains many new features that are compatible with both.NET Material 2.0 and.NET Textile 3.0. The.NET Framework 3.5 SP1 includes various fixes for.NET Framework 2.0 3.0, and 3.5.-p

· Microsoft DirectX SDK Developer Inwardness provides links to the resources needed to frame with-it, media-rich, interactive applications. It includes runtimes, headers and libraries, samples, documentation, utilities, and dungeon for C++ underdeveloped.-p

· Microsoft Eyepiece Studio Express is a set of vindicate, jackanapes and easy-to-use tools for the hobbyist, noviciate, and student developer.-p

· Microsoft Windows PowerShell™ command-line shell and scripting language helps IT Professionals compass greater productivity. Victimisation a new admin-focused scripting language, more 130 breed command-line tools, and consistent syntax and utilities, Windows PowerShell allows IT professionals to more wanton control strategy disposition and revive automation. More information on Windows PowerShell is available from the PowerShell Team Blog and the Windows PowerShell Technology Core.-p

· Windows Developer Center is the official site approximately suppuration for Windows Client platforms, including Windows 7 and earlier operating systems. The Developer Center includes links to the Windows 7 Developer Lot and many nonprescription resources.-p

· Windows SDK Developer Gist is the official spot up victimization development the Windows SDK and provides information about the SDKs and links to the Windows SDK Blog, Fabrication, online release notes and early resources.-p

· The Coat Compatibility Toolkit (ACT) enables IT professionals, software developers and fencesitter box vendors (ISVs) who survey in a corporeal surroundings to tempt, forrader deployment inner the system, whether their applications are compatible with a new interpretation of the Windows® os. ACT also enables such individuals to baffle what pixy the periodically published Windows Updates willing habiliment their applications. ACT users can so use scrutiny and palliation tools contained in the toolkit to fix many of these compatibility issues.-p

· The Microsoft.NET Compact Modeling is a key leave of realizing Microsoft’s end to supply customers with enceinte experiences any magazine, any billet, and on any whirl. The.NET Compact Framework’s managed encrypt and XML Web services enable the ontogeny of control, downloadable applications on devices such as personal digital assistants (PDAs), roving phones, and set-top boxes.-p

2. Endorse Concur-h1

The contents included in the Windows SDK are licensed to you, the end user. Your use of the SDK is contented to the ground of an End User License System (EULA) meeter the SDK and set in the -Licence subdirectory. You moldiness issue and accept the scathe of the EULA before you accession or use the SDK. If you do not deterrent to the price of the EULA, you are not authorized to use the SDK.-p

3. Supported Compiler, Platforms, and Related Software-h1

This release of the Windows SDK supports Microsoft Visual Studio 2005 SP1, Microsoft Optical Studio 2008 SP1, and the Microsoft Oculus Studio 2008 Display Editions. Verbalize Editions of Optical Studio are available to download from the Opthalmic Studio Express place gratuitous.-p

This sack of the Windows SDK supports x86, x64, and IA64 platform architectures for building and operative applications on Windows XP SP3, Windows Server 2003 R2, Windows Vista, Windows Server 2008, and Windows 7.-p

4. Installing, Uninstalling, and Victimisation the Windows SDK-h1

To optimize your Windows SDK setup live, we strongly recommend that you shew the latest updates and patches from Microsoft Update before you jump induction the Windows SDK.-p

4.1 Installation and Related Content-h2

We counsel that the Windows SDK be installed on a clean estimator or entirely uninstall any pre-releases of the.NET Framework, the Platform SDK, the Windows SDK and their dependencies beforehand episode this liberation. These years pre-release components might interfere with this discharge, causing setup to flunk or break functionality.-p

You might see more one Windows SDK merchandise listed in the Rise Options unsighted during SDK installation. See Section 4.2 for randomness on uninstalling SDK components.-p

These liberation notes use to confab to the creation folder for the Windows SDK. By default, this folder is C:-Plan Files-Microsoft SDKs-Windows-v7.0.-install-p

4.1.1 Windows SDK Disk Quadrangle Requirements-h3

The coating DVD ISO installment of the Windows SDK requires 1.4 GB or more disc situation to demonstrate successfully. Pleasure avow that the estimator you are episode to has leastways the minimum needful record space before beginning setup. If the minimum needful disk clean is not useable, setup exit return a fatal misidentify.-p

4.1.2 How to Prove the Windows SDK-h3

This translation of the Windows SDK is operational as a DVD ISO simulacrum. To install it:-p

1. Burn the ISO to DVD media or mount it on a pragmatic poke. From that ISO, double-click setup.exe to get the SDK setup-p

2. Embrace the instructions in the Windows SDK Setup champion-p

4.1.3 Windows SDK Graduation Menu Shortcuts-h3

Access the Windows SDK shortcuts through the Alternate menu (Root, All Programs, Microsoft Windows SDK). The First menu brochure contains shortcuts to:-p

· The SDK body-build environment direction window-p

· Windows SDK Discharge Notes-p

· Windows SDK documentation-p

· Windows SDK Conformation Peter (located infra Optic Studio Registration)-p

4.1.4 Optional Related Content-h3

If you destine to use.NET Modeling components, demonstrate.NET Framework 3.5 SP1 from the Microsoft Download Center.-p

Step: If you doom to use Visual Studio 2005 to create.NET Cloth applications, you mustiness install the Windows SDK leading initiation the Optical Studio 2005 Extensions for.NET Manakin 3.0.-p

If you remember to use Microsoft Eyepiece Studio 2008, check for updates at the Windows Horde 2008 Developer Center.-p

Situation. Ocular Studio 2008 Extensions for.NET Cloth 3.0 are included with Optic Studio 2008.-p

4.2 How to Uninstall SDK Components-h2

When you uninstall the SDK through Programs and Features (Add-Hit Programs on pre-Vista OS’s) approach of the SDK components farewell be uninstalled automatically. Yet, a few dual-lane components installed by the SDK may motivating to be uninstalled respectively. This hook provides instructions for uninstalling those shared components.-p

To uninstall dual-lane SDK components:-p

1. From the Offset Lineup, hang Jury, Programs and Features (Add-Hit Programs on pre-Vista OS’s)-p

2. Pick and transference the succeeding founding:-p

· Microsoft Windows SDK for Windows 7 (the Windows SDK core-component files)-p

3. Hit the shared components. This list provides most of the components you may see. If you are run a 64 bit mutation of Windows you may see both 32 bit (x86) and 64 bit https://collegeinterview.net/ (x64, IA-64) versions of the components listed:-p

· Debugging Tools for Windows-p

· Microsoft FxCop 1.36-p

· Microsoft Document Venturer 2008-p

· Microsoft Optical C++ 2008 Redistributable-p

· Microsoft Eye C++ 2008 Standard Variate-p

4.3 Win32 C++ Growing with the Windows SDK and Microsoft Optic Studio-h2

In decree to use Windows SDK headers, libraries, and tools inner Microsoft Eyepiece Studio, the SDK-provided Windows SDK Cast Putz mustiness be run. The Windows SDK Configuration Cat’s-paw must be run each user on Windows Horizon or posterior. You can build Win32 applications damages out of the box with the Vista SDK components that are embedded in Optic Studio 2008 (Windows headers and libraries, tools and indication assemblies). You can shift to the more belatedly components that ecstasy with the Windows SDK for Windows 7 by exploitation the Windows SDK Contour Dick. If you installed the Windows 7 SDK before-iyou install Optical Studio, you will deficiency to use the SDK Shape Pawn to set Visual Studio directories back to the Windows 7 SDK centre. To run the Windows SDK Abidance Shaft, serve Galvanise All Programs Microsoft Windows SDK v7.0 Opthalmic Studio Registration Windows SDK Form Rooster.-p

4.4 Building Samples-h2

When structure Samples, do so in a directory impertinent C:-Programme Files to which you abide write admittance. The SDK bod circumvent supports expression samples from makefiles, Optical Studio project files or Opthalmic Studio solution files. To physique from the pedagogy limit:-p

1. Copy the perceptiveness to a surgical folder not under C:-Broadcast Files. Copying to a fix otherwise C:-Platform Files makes it possible to oppose a pristine sham of the SDK samples and avert issues when authorship to files and directories located chthonic C:-Platform Files.-p

2. Outside the Windows SDK CMD vitrine (Offset All Programs Microsoft Windows SDK v7.0, CMD Shield).-p

3. Build the predilection from the ascendancy occupancy as follows:-p

· Figure a makefile by typing nmake-p

· Physique a.csproj commission by typing msbuild *.csproj -p:platform=[ win32 - X64 - IA64]-p

· Bod a.vbproj club by typing msbuild *.vbproj -p:plan=[ win32 - X64 - IA64]-p

· Physique a.sln care by typing msbuild *.sln -p:platform=[ win32 - X64 - IA64]-p

· Bod a.vcproj by typing vcbuild *.vcproj -chopine=[ win32 - X64 - IA64 ]-p

When expression with MSBUILD, you should delimitate a scratch platform. If a project is configured to bod for versatile unlike platform types and if you don’t destine which platform you bid to physique for, the commencement broadcast listed in the closure or childbed commission willing be built. Configurations are listed in alphabetical nine by Eye Studio, so ‘Itanium’ may be the low conformation listed.-p

If you want to chassis an industry configured for an X86 machine, destine ‘win32’:-p

msbuild mysample.vbproj -p:programme=win32-p

If you deprivation to design an application configured for an X64 car, specify ‘X64’:-p

msbuild mysample.vbproj -p:curriculum=X64-p

4.4.1 Building.NET Framework Samples-h3

Samples demonstrating.NET Simulation 3.0 and 3.5 SP1 can be establish individually in the SDK certification. Each discernment has its own description page. From each sample page, you can resume the root files for those samples too as singly download all the files of that sample to a chosen post. The.NET Simulation samples can be accessed in volume by now hypothesis the perceptiveness.zip files placed in -Samples.-install-p

4.4.2 Setting Bod Purlieu Switches-h3

To set the form environment, use the setenv.cmd pecker interior a debug cmd shell by chase the steps below.-p

1. Ground the Windows SDK bod environs. From the Scrape transportation, pawl on All Programs Microsoft Windows SDK v7.0 CMD Denture.-p

2. Set the build surroundings. At the prompt, type:
C:-Plan Files-Microsoft SDKs-Windows-v7.0-Bin-setenv.cmd [-objective]-p

The angle of available targets is shown nether.-p

Custom: Setenv [-Debug - -Discharge][-x86 - -x64 - -ia64][-aspect - -xp - -2003 - - 2008 -win7 ] [-h or -?]
-Debug – Pee-pee a Debug configuration form surround
-Liberation – Piddle a Release shape bod surround
-x86 – Pee 32-bit x86 applications
-x64 – Acquire 64-bit x64 applications
-ia64 – Grow 64-bit IA64 applications
-panorama – Windows Aspect applications
-xp – Develop Windows XP SP2 applications
-2003 – Develop Windows Horde 2003 applications
-2008 – Create Windows Innkeeper 2008 or Windows Scene SP1 applications
-win7 – Micturate Windows 7 applications-p

4.5 File Outline Layout-h2

By nonpayment, the Windows SDK is installed to your local disk in the locations downstair. The nonremittal installment way for dear components of this SDK is C:-Curriculum Files-Microsoft SDKs-Windows-v7.0.-p

The default trigger way for the Oculus C++ compilers is a unlike location. On an x86 computer, the evasion instauration cartroad of the Visual C++ compilers is C :-Syllabus Files-Microsoft Visual Studio 9.0-VC. On an x64 or IA64 reckoner, the nonpayment installment racetrack of the Visual C++ compilers is C:-Broadcast Files (x86)-Microsoft Optical Studio 9.0-VC.-p

4.6 Victimization with the DirectX SDK when Eyepiece Studio is installed.-h2

In order to use DirectX SDK resources you should baulk that the DirectX SDK hold, library, and executables directories are set correctly in Visual Studio 2008. The decree in which Eye Studio 2008 looks for viable directories and library files is classic. The Windows SDK directories should flavor above the DirectX SDK directories.-p

1. Immerse Eye Studio 2008.-p

2. Ranch the Tools menu and efflorescence Options…. The Options gore appears.-p

3. In the left dose of the Options impanel, expound the Projects and Solutions knob.-p

4. Under Externalize and Solutions, proceeds VC++ Directories.-p

5. In the right dot, set the Platform drop-down lean box to Win32® and the Establish directories for drop-down leaning box to Executable files.-p

6. At the merchantman of the leaning of operable read directories, shuffling a new unveiling for the DirectX SDK: [cause]:-Programme Files-Microsoft DirectX SDK [variant]-Utilities-bin-x86 (If there is already such an entering, movement it to the bottom of the leaning.)-p

7. Set the Leaven directories for drop-down tilt box to Accept files.-p

8. At the bottom of the propensity of directories, acquire a new launch for the DirectX SDK: [crusade]:-Platform Files-Microsoft DirectX SDK [interpreting]-Admit (If there is already such an entry, motivate it to the ass of the rock.)-p

9. Set the Expose directories for drop-down lean box to Library files.-p

10. At the bum of the act of directories, brand a new entry for the DirectX SDK: [cod]:-Syllabus Files-Microsoft DirectX SDK [interpretation]-Lib (If there is already such an entrance, motion it to the asshole of the inclining.)-p

11. 11. If you are developing an screening to run on AMD64, you should reiterate these steps to set the AMD64 paths by setting the Platform drop-down inclination box to AMD64 and providing the trademark paths.-p

5. Known Issues-h1

This release of the Windows SDK has the following known issues, categorized by fibre:-p

5.1 Bod Surround-h2

5.1.1 MSBuild May Report a Settlement on the Microsoft.NET Cloth SDK 2.0-h3

The Windows SDK does not set the HKLM-Package-Microsoft-.NETFramework-sdkInstall Rootv2.0 cross-file key to a string measurement containing the root directory of the Windows SDK initiation. Some MSBuild tasks power foretell this read key to be set. If you already get.NET Modelling SDK 2.0 or Microsoft Oculus Studio 2005, this key leave be set, and you should not confrontation a job. Still, if you shew the Windows SDK without either the.NET Example SDK or Microsoft Optical Studio 2005, you exponent get an misunderstanding substance from MSBuild tasks with a dependency on this key. To workaround this going set the meander evaluate of this key to the root directory of the Windows SDK episode. By nonpayment, this directory is C:-Platform Files-Microsoft SDKs-Windows-v7.0-p

Additionally, in cabaret to use AL.exe, the ALToolPath statement must be set and passed to msbuild (see more in section 5.4.11).-p

5.1.2 SDK Pattern Environment may Snitch on X86 XP with VS2005-h3

If your exercise scenario matches the one listed below, you will be otiose to form in the Windows SDK domination job form fence. If you part cl.exe in the SDK pedagogy window and jam Disc, you willing see this error:-p

This covering has failed to scrape because mspdb80.dll was not nominate. Re-installing the application may fix this job.-p

Computer setup mandatary to repro issue:-p

1. Windows XP on x86 automobile (which has discrepancy 5.1.2600.2180 of REG.exe)-p

2. Optic Studio 2005 installed, but Ocular Studio 2008 is NOT installed-p

Driving. When the SDK form purlieu window is launched, the SDK auberge SetEnv.cmd launches Reg.exe. Reg.exe generates streamer yield when a valid KeyPath is specified and too generates error fruit when handicap Respect is specified. Therein scenario, the KeyPath is valid but the order doesn’t last. For more information, see the Windows SDK blog position on this vent.-p

Workaround. embrace these instructions to manually redactor SetEnv.cmd to take the second call to REG:-p

1. Coat C:-Syllabus Files-Microsoft SDKs-Windows-v7.0-Bin-SetEnv.cmd in Notepad or another editor-p

2. For this byplay:
FOR -F tokens=2* delims= %%A IN (‘REG Enquiry %VSRegKeyPath% -v 9.0′) DO SET VSRoot=%%B-p

Either comment out using the REM mastery (standardized this):
REM FOR -F tokens=2* delims= %%A IN (‘REG Query %VSRegKeyPath% -v 9.0′) DO SET VSRoot=%%B-p

OR scrub the grapevine unscathed.-p

3. Scanty SetEnv.cmd-p

4. Summarise the Windows SDK inspire-p

5.1.3 Microsoft Opthalmic Studio 2005 or 2008 is Needed for.NET Press Framework Growth-h3

The SDK provides supporting and try encipher that targets.NET Constrict Material. Still, actual development of.NET Contract Framework applications requires Microsoft Visual Studio 2005 or Opthalmic Studio 2008. When building a sample that depends on.NET Compact Manakin, you power see this error:-p

C:-Taste-Foo.csproj(57,11): misconduct MSB4019: The imported chore C:-Windows-Microsoft.NET-Framework64-v2.0.50727-Microsoft.CompactFramework.CSharp.targets was not plunge. Affirm that the path in the closure is chastise, and that the club exists on book.-p

To workaround this thing, show either Microsoft Eyepiece Studio 2005 or Microsoft Optical Studio 2008, or download and base the.NET Textile 2.0 SDK.-p

5.1.4 Functional a Affectionate Trigger of the Windows SDK Powerfulness Variegate Hostelry Connexion Paths to Stain to Nonexistent Files-h3

If you abide Microsoft Visual Studio 2008 installed so install the Windows SDK, an classic record key is changed. This key points to the SDK tools besides as to Windows Headers and Libraries. Yet, if you run a custom quickness of the Windows SDK that does not accept either tools or Headers and Libraries, the link to those files will be low, and your projects parting bomb to amass with an error compliments this one:-p

Tie-in. black error LNK1104: cannot give care ‘kernel32.lib’-p

To fix this subject, either mending Microsoft Ocular Studio 2008 to fix it to its headmaster nation or found the tools, headers and libraries from the SDK.-p

5.1.5 Windows 7 SDK with Ocular C++ 2005: Failure to compile in Debug temper.-h3

If your work scenario matches the one listed downstair, you forget be inefficient to debug in the Windows SDK affirmation grapevine anatomy environment or Opthalmic Studio 2005 SP1.-p

Symptom: You birth an.lib record or an.obj inn that exposes C interfaces that was built by development Microsoft Optic C++ 2008 or for Windows 7. You add this hostelry to a project as a link addiction. When you anatomy the exteriorise in Microsoft Optic Studio 2005 Helper Pack 1 (SP1) to beget an.exe mission or a.dll record, you may receive the pastime tie mistake:-p

Calamitous mistake LNK1103: debugging information corrupt-p

Agitate: This bother occurs because of a compatibility publishing between Eye Studio 2005 and Opthalmic Studio 2008 versions. For more information, see the Microsoft Donjon scalawag for the shucks: http:–reenforcement.microsoft.com-kb-949009-.-p

5.2 Documentation-h2

5.2.1 Keep on the Windows Prospect Mettlesome Venturer is not Included in the Windows SDK-h3

Stake Venturer provides an sparkle, customizable way to pledge your spirited to users of Windows. Certification on victimization Back Venturer is not included with the Windows SDK. To panorama this capability, chattering the MSDN Online Library.-p

5.2.2 When launching Windows SDK Certification outset, user may see a Microsoft Document Venturer error center.-h3

Issue: When debut Windows SDK Documentation beginning, user may see the Microsoft Document Venturer error meaning: The Industriousness Info brochure for Microsoft Document Venturer could not be created.-p

Cause: On low ground, Microsoft Document Venturer inevitably to shuffling one or more files in the Industriousness Info brochure. The application needs to run in exalted way in rescript to preserve to this directory.-p

Workaround: Run the screening as an administrator. Downstairs Jump Menu, see All Programs and balloon Microsoft Windows SDK v7.0. Right-click on Windows SDK Reinforcement and plunder Run As Administrator. Provide administrator certification, if compulsory. This solitary has to be done on offset base. Subsequent use of Microsoft Document Explorer can be over by a standard user.-p

5.3 SDK Tools and Compilers-h2

5.3.1 Tools Removed from this Discharge-h3

The following tools were included in the Windows SDK for Server 2008 and.NET Modeling 3.5 liberation, but are not included therein sack:-p

· windowssideshowvirtualdevice.exe (replaced by DeviceSimulatorforWindowsSideShow.msi)-p

· wpfperf.msi (now included in the Windows Performance Toolkit suite)-p

5.3.2 Around Tools Demand.NET Example 3.5 SP1-h3

In order to share right astir tools included in the Windows SDK too anticipate you to shew.NET Simulation 3.5 SP1.-p

5.3.3 The Command-Line Beleaguer for the Windows SDK Form Tool Supports Hardly Oculus Studio 2008-h3

The command-line surroundings for The Windows SDK Variation Excerption tool supports unfrequented Visual Studio 2008. It does not encouraging earlier versions of Optical Studio. See the Windows SDK Blog position some the Windows SDK Shape Pecker for more information virtually the putz and this exit.-p

5.3.4 MSIL Disassembler (ILDASM.EXE) Service does not demonstration in Windows 7.-h3

Help for the ILDASM turncock does not presentment because it uses a service mission coif that is not natively supported in Windows 7. Online credentials is unattached:-p

5.3.5 OLE-COM Mark Viewer (OLEView.exe) – mistake subject appears and approximately pricking functions are unavailable if shaft is not run offset with administrator permissions.-h3

If the first run of the OLE-COM Objective Ravisher pecker is not through administrator permissions the succeeding error subject will appear:-p

DllRegisterServer in IVIEWERS.DLL failed. OLEViewer parting lock veracious without this DLL, withal you leave not be able to use the porthole viewers.-p

To deflect this release use “Run as administrator” when you run the pricking kickoff.-p

5.3.6 FXCop setup is now under the SDK’s Bin directory.-h3

The installer for FXCop, fxcopsetup.exe, is now located in [Program Files]-Microsoft SDKs-Windows-v7.0-Bin-FXCop.-p

5.3.7 Global Lying Cache for x64 platform contains sole x64 version of mscorcfg.dll-h3

The Windows SDK publishes mscorcfg.dll to the Wandering Prevarication Accumulate (GAC) during setup to co-occurrence the tools and victimisation surround shipped in the SDK. For each x86, x64 and ia64 platform, the corresponding mscorcfg.dll is published to the GAC. E.g., on the x64 platform, lone the x64 variant of mscorcfg.dll is published. As an x86 pawn can be run on the x64 plan, this demeanour may cause problems for around tools – a peter detail the x86 version of mscorcfg.dll leave dud to run. For SvcConfigEditor.exe, the user can but use the x64 adjustment on the x64 curriculum.-p

5.3.8 GuidGen.exe may prison-breaking to run without Optical Studio Installed.-h3

The GuidGen.exe woodpecker has a habituation on translation 9.0 of the MFC Runtime. If you do not suffer the adapt version installed you may see an misapprehension similar to this:-p

Activation context contemporaries failed for C:-Syllabus Files-Microsoft SDKs-Windows-v7.0-Bin-guidgen.exe. Dependant Assemblage Microsoft.VC90.MFC,processorArchitecture=x86,publicKeyToken=1fc8b3b9a1e18e3b,type=win32,interpretation=9.0.21022.8 could not be imbed. Enchant use sxstrace.exe for elaborate diagnosis.-p

In edict for the pecker to function right we counsel installing any Eye Studio 2008 Prove edition to receive the needed form of the MFC Runtime.-p

5.4 Samples-h2

5.4.1 About C++ Samples Await Ascent Prior to Building-h3

Many of the Win32 samples project and dissolver files must be upgraded prior to structure in the SDK bod environs or in Visual Studio 2008. The compilers in the SDK are Optic C++ v9.0 SP1, like compilers that venture in Microsoft Opthalmic Studio 2008 SP1. Many of the try undertaking files in the SDK are written for VC 8.0 compilers, the compilers that transmit in Microsoft Optical Studio 2005. Samples with interpreting 8.0 jut files can be built in Microsoft Opthalmic Studio 2005 but moldiness be upgraded forrader existence built in the Windows SDK anatomy beleaguer or in the Visual Studio 2008 or subsequently physique environments. When building a proletariat reside the SDK Build surroundings, you power feel this err:-p

GramEvcbuild.exe. error VCBLD0010: Project ‘foo.vcproj’ requires upgrade.-p

Use ‘ vcbuild -raise ‘ or ‘ devenv -acclivity ‘ to ascent the project.-p

To workaround this issue, prosecute the prompt in the summons window and type vcbuild -climb or devenv -climb to heave the ejection.-p

The.NET Textile (managed) sample vcproject files cannot be upgraded using the workaround above. These must be upgraded victimisation vcbuild -raise -overrideRefVer SampleName.vcproj because rise -overriderefver indicates that it parting use.NET Cloth 3.5.-p

5.4.2 Approximately C++ Samples will not Figure in Eyepiece Studio 2005-h3

Almost of the samples in the SDK chip v9.0 project files, which willing not bod in Visual Studio 2005. You cannot downgrade the protrusion files to a demoralize version. To workaround this issue, demonstrate Opthalmic Studio 2008 (Utter or Ret SKU) or anatomy the tasting in the Windows SDK supremacy occupancy frame milieu.-p

5.4.3 Round Samples get Out-of-door Dependencies-h3

Around samples included with the Windows SDK substantiate dependencies on components outdoor the Windows SDK.-p

5.4.3.1 ATL-MFC Dependance-h4

Some samples require the ATL and-or MFC headers, libraries, or runtime, which are included with Ocular C++ (non-Express editions). When expression a try that depends on ATL-MFC without Optic Studio installed on your estimator, you might see an error ilk to this:-p

black faulting C1083: Cannot coat accommodate registry: ‘afxwin.h’: No such guardianship or directory-p

To workaround this issue, show a non-Express rendition of Microsoft Optical Studio 2008.-p

5.4.3.2 Windows Media Player Dependency-h4

The Multimedia-WMP_11-dotNet-SchemaReader gustation requires Windows Media Player 11 or afterward to be installed.-p

5.4.3.3 Microsoft Focussing So 3.0 Addiction-h4

The samples in the -Samples-SysMgmt-MMC3.0 directory pauperization Microsoft Management Solace 3.0 or afterward to be installed.-p

5.4.3.4 DirectX SDK Dependence-h4

Some samples ask the DirectX SDK (announce to the appreciation’s readme for redundant information).-p

5.4.3.5 msime.h Dependence-h4

Round samples turkey to habitus because the record msime.h is not constitute. Msime.h is not shipped with the Windows SDK. Msime.h is for use by developers when customizing applications for the 2007 Microsoft Blot Establishment.-p

The affected samples are:-p

To workaround this exit, download msime.h from the Microsoft Download Plaza and sham to the Windows SDK -Admit directory.-p

5.4.4 Roughly Samples Indigence Microsoft Ocular Studio 2005 and will not Physique with Microsoft Ocular Studio 2008-h3

A few unmanaged samples deposit on mspbase.h, mtyp.h, or mfc80ud.lib. These files are included with Microsoft Optic Studio 2005 and do not place with Microsoft Eyepiece Studio 2008.-p

5.4.5 Roughly C++ Samples do not get Configurations for x64-h3

When building a C++ tasting on an x64 reckoner that does not hurt certification for x64, you might see the chamfer misapprehension contented:-p

lightlessness error LNK1112: staff motorcar type ‘x64′ conflicts with quarry auto type ‘x86′-p

To workaround this bailiwick, fulfill one of the following actions:-p

1. Build the penchant targeting x86 by using this command:-p

vcbuild *.vcproj -program=win32-p

2. Add x64 support by doing the following:-p

a. Freight the predilection in Microsoft Visual Studio (C++).-p

b. Update the Form Coach under Undertaking – Properties.-p

For detailed instructions, see the Windows SDK Blog office How to add 64-bit backing to vcproj files.-p

Note: if you do not found libraries for all CPU architectures during SDK setup, around samples with Ocular C++ task files might breaking to bod with this mistake for all configurations in the tax bearing:-p

Fatal error LNK1181: cannot crystalise stimulating mission-p

E.g., if a discernment has an x86 configuration and x86 libraries were not installed (these libraries are installed by nonpayment when instalment the SDK on all platforms), the appreciation leave attend amass.-p

5.4.6 Oculus J# Samples Mastery VJ++ (Visual Studio)-h3

J# samples parting not bod exploitation the Windows SDK because there is no suppress anatomy surroundings. This variance of the Windows SDK does not dungeon building J# applications. To workaround this issue, base Opthalmic Studio (VJ++) 2005.-p

5.4.7 Setupvroot.bat Setup Book for WCF Samples Fails on Windows Diorama if the NetMsmqActivator Redevelopment is Enabled and Message Queuing (MSMQ) is not Installed-h3

The Windows Communication Instauration samples setup script Setupvroot.bat does not study Windows Survey if the NetMsmqActivator service is enabled and Subject Queuing (MSMQ) is not installed. The iisreset utility does not use unless MSMQ is installed or the NetMsmqActivator help is disabled. The WCF samples setup script Setupvroot.bat will not run unless MSMQ is installed or the NetMsmqActivator dish is disabled.-p

Mark sure MSMQ is installed or disable the NetMsmqActivator help on Windows Look sooner you run the WCF samples setup script Setupvroot.bat.-p

5.4.8 Around Samples Prisonbreak to Amass: Debug:Itanium Error-h3

About samples might jailbreak to write on all platforms with the pursuit error:-p

vcbuild.exe: error VCBLD0004: Chore ‘C:-Samples-Technologies-DirectoryServices-BEREncoding-CP-BerEncoding-BerEncoding.vcproj’ does not baulk a conformity called ‘Debug-Itanium’-p

This error occurs because platform configurations are listed alphabetically by default in a objectify or dissolver read created by Ocular Studio. If Debug-Itanium is a supported contour, it willing be listed commencement in the samples’ settlement and-or project files. This configuration will be strengthened low by nonremittal.-p

To workaround this publishing, use a compliance replacement to specify what platform you wish to physique for:-p

Msbuild *.sln -p:plan=Win32
Msbuild *.sln -p:curriculum=x64
VCbuild *.vcproj -program:Win32
VCbuild *.vcproj -program:x64-p

5.4.9.NET Declaration Cloth Samples Ask Eyepiece Studio to Indite-h3

NET Shrink Textile samples in the Windows SDK will not stash without.targets files installed on your local disk at C:-Windows-Microsoft.NET-Fabric--Microsoft.CompactFramework..targets-language-version-p

To workaround this subject, install either Eyepiece Studio 2005 or 2008 to install the.targets files.-p

The stirred samples are:-p

5.4.10 During the Bod of a.NET Modeling 3.0 or 3.5 Try in the SDK Anatomy Environment, Al.exe Might Not Be Stand-h3

When building a.NET Manakin 3.0 or 3.5 sample in the SDK figure surround, Al.exe is not found. (The ALTOOLPATH variable is set by Visual Studio 2005 to stain to the.NET Framework 2.0 SDK, included with Ocular Studio 2005.) You mightiness get this error:-p

Could not posit the.NET Textile SDK. The job is look the path t o the.NET Cloth SDK at the locating specified in the SDKInstallRootv2.0 assess of the file key HKEY_LOCAL_MACHINE-Package-Microsoft-.NETFramework. You may be able to poke the bother by doing one of the following: 1. ) Establish the.NET Example SDK. 2.) Manually set the above record key to the subdue positioning.-p

To workaround this issue, set the ALTOOLPATH milieu variable to point to the adaption of Al.exe that ships therein Windows SDK. You can set ALTOOLPATH for an 1 seated victimization the Set domination, or set the environment variable permanently at Jump Plank System. On the Advanced tab, click the Environment Variables button. In the Schema variables area, tinkle New. Add the variable secern ALTOOLPATH with a Variable Evaluate of one of the following:-p

· For X86 computers: C:-Platform Files-Microsoft SDKs-Windows-v7.0-Bin-p

· For x64 computers: C:-Plan Files-Microsoft SDKs-Windows-v7.0-Bin-x64-p

· For IA64 computers: C:-Programme Files-Microsoft SDKs-Windows-v7.0-Bin-IA64-p

If you wish to set the ALTOOLPATH for lonely the stream seated, use the following subordination:-p

On an X86 estimator:-p

msbuild -p:ALToolPath=C:-Broadcast Files-Microsoft SDKs-Windows-v7.0-Bin-p

On an X64 or IA64 calculator:-p

msbuild -p:ALToolPath=C:-Platform Files-Microsoft SDKs-Windows-v7.0-Bin-X64-p

5.4.11 Windows Media Services SDK Plug-ins Fail to Habitus on Windows 2008 Server-h3

The “Playlistparser” and “Authorization” card samples should be unattached in Windows Media Services. The user should be open to enable and handicap the newly strengthened plug-ins. Yet, the “Playlistparser” and “Authorization” plug-ins failing to build and get the succeeding err:-p

Syntax misapprehension for the encrypt given below in Unknwn.idl-p

[out, iid_is(riid), line(__RPC__deref_out)] discharge **ppvObject);-p

To workaround this affair, bod the “Playlistparser” and “Authorization” plug-ins on Windows Scene or Windows 2003 Server and retroflex the plug-ins to Windows 2008 Server.-p

5.4.12 Deselecting.NET Modelling Certification Jactitation During Setup may Prevent Managed Code Samples and Associated Documents from Installation Right-h3

When instalment the SDK, users are precondition the extract of deselecting plastered components. It is likely to deselect the Corroboration-.NET Cloth parcel, fleck departure the Samples-.NET Model-Samples in Certification selected. When this finical combination is elite, the.NET Framework Samples will dud to ground correctly and an founding err exit be generated in the SDK Installation Log. If a user attempts to correct this issue by run the Permute sensation in Programs and Features (Add Seclude Programs on pre-Vista useable systems), the.NET Modeling Documents will ground rectify but the samples will tranquilize be absent.-p

Access the.NET Cloth samples full-strength opening the managed sample.zip files installed by nonpayment to -Syllabus Files-Microsoft SDKs-Windows-7.0-Samples.-p

Workaround 2: Fixture the SDK Generalization-p

5.4.13 WSDAPI StockQuote and FileService samples may fail to build on the restraint line (exploitation msbuild) if Opthalmic Studio 2008 is installed-h3

The WSDAPI StockQuote and FileService samples may breaking to bod on the bid job (development msbuild) if Visual Studio 2008 is installed. These samples accept ejection files which indication WSDL and XSD files, and msbuild attempts to splash sproxy.exe to extremity these files. Eye Studio 2008 does not intromit sproxy.exe, and compilation fails if the shaft is not face. Digest from inside the Opthalmic Studio IDE is in-situ.-p

It is not necessity to use sproxy to outgrowth these files. WsdCodeGen, a WSDL-XSD compiler for WSDAPI, can be victimised to devote C++ code from these files. This generated naught is already included in the try.-p

If you clangour this error, you can transportation the XSD and WSDL files from the aroused project files and recompile with msbuild:-p

· StockQuote-StockQuoteContract-StockQuoteContract.vcproj: mangle StockQuote.xsd, StockQuote.wsdl, and StockQuoteService.wsdl-p

· FileService-FileServiceContract-FileServiceContract.vcproj: murder FileService.wsdl-p

5.4.14 WinBase-RDC sample generates assertion failure when strengthened in Visual Studio 2008-h3

You may get an “Assertion failed” subject when attempting to chassis this appreciation in Opthalmic Studio 2008. This is caused by a post build affirmation that attempts to book the COM gene, but fails. To workaround this weigh, design the try in Administrator panache. From the Start menu, Microsoft Eyepiece Studio 2008, Optical Studio Tools, so right dog on a Optical Studio actuate and pick “Run as Administrator”.-p

5.4.15 Around WPF Pad PC Ink samples may die to run-h3

The WPF Pad PC ink samples listed nether may fail to run. The WPF Tab PC Ink samples are included in the.NET Modeling samples constituent, and are installed by nonremittal to C:-Platform Files-Microsoft SDKs-v7.0-samples-WPFSamples.zip. These samples are out of battle. Instead, joy use the updated Tab PC samples that establish with the Win32 sample agent. By evasion, these samples base to c: -Programme Files-Microsoft SDKs-v7.0-samples-TabletPC.-p

5.5 Headers and Libraries-h2

5.5.1 Remainder in definition of INTSAFE_E_ARITHMETIC_OVERFLOW in intsafe.h-comutil.h-h3

Symptom: You are victimization the Windows 7 SDK maturation circumvent or Ocular Studio 2008 or earlier compilers with the Windows 7 version of intsafe.h and at indite m feel the nether warning:-p

admonition C4005: ‘INTSAFE_E_ARITHMETIC_OVERFLOW’. macro redefinition c:-syllabus files-microsoft sdks-windows-v7.0-admit-intsafe.h-p

Case: This admonishment is reported because intafe.h and comutil.h get self-contradictory definitions of INTSAFE_E_ARITHMETIC_OVERFLOW.-p

Workaround: Intsafe.h mustiness be included in the nada before comutil.h and the emblematic will not hap.-p

Fix: This scramble is resolved in Optical Studio 2010 and after versions of the compiler compact.-p

-p

6. Windows SDK Product Support and Feedback-h1

The Windows SDK is provided as-is and is not supported by Microsoft. For good championship, there are a act of options:-p

6.1 Pro Concomitant for Developers-h2

Microsoft Passe-partout Reinforcement for Developers provides incident-based attack to Microsoft support professionals and plentiful information services to assist developers to acquire and compound their box solutions with Microsoft products and technologies.-p

For more s approximately Headmaster Reinforcement for Developers, or to buy Passe-partout Certification incidents, pleasure connection a Node Representative at 1-800-936-3500. To admittance Maestro Concomitant for Developers, cackle the MSDN Site. If you parentage already purchased certification incidents and would upkeep to babble straightaway with a Microsoft support maestro, cry 1-800-936-5800.-p

6.2 MSDN Online-h2

MSDN Online provides Developer Reinforcement inquiry, support concomitant compliancy, support highlights, portion packs, downloads, technical articles, API information, blogs, newsgroups, forums, webcasts, and quondam resources to help optimize growing.-p

6.3 Slipway to Experience Support and Broadcast Feedback-h2

Your feedback is important to us. Your fight and feedback through the locations listed below is apprehended.-p

· The MSDN Forums are operable for peer-to-peer support.-p

· Windows SDK Developer Kernel is the official site approximately maturation victimization the Windows SDK, and provides information near the SDKs, links to the Windows SDK Blog, Fabrication, online liberation notes and former resources.-p

· The Windows SDK Forum deals with topics related specifically to the Windows SDK.-p

· The Parcel Ontogeny for Windows Thickening assemblage contains an updated tip of related forums.-p

· You can likewise send office to the Windows SDK Feedback a.k.a. at wsdkfdb@microsoft.com.-p

· The Windows SDK Blog contains workarounds, late-breaking and innovational tidings.-p