Using the Windows 7 RC SDK in Visual C++ 2010 Beta 1

re: Using the Windows 7 RC SDK in Visual C++ 2010 Beta 1

vcblog — Thu, 21 May 2009 03:04:39 GMT

Hello

And if you want to get VS2010 Beta 1 then Soma has all the details: http://blogs.msdn.com/somasegar/archive/2009/05/18/visual-studio-2010-and-net-fx-4-beta-1-ships.aspx

Thanks

Damien

Visual C++

re: Using the Windows 7 RC SDK in Visual C++ 2010 Beta 1

Phaeron — Thu, 21 May 2009 12:52:17 GMT

Just to be clear, is it a supported scenario to use the Windows SDK includes and libs with the stock Visual C++ toolset? The reason I ask is that I've had some headaches recently with the SDK's <winnt.h> declaring intrinsics in a manner incompatible with <intrin.h>, and was wondering if the SDK headers were officially supported only with the SDK toolset.

re: Using the Windows 7 RC SDK in Visual C++ 2010 Beta 1

Jalf — Thu, 21 May 2009 17:58:09 GMT

I just installed the beta, and I'm a bit surprised to see that property sheets are still there. Weren't the MSBuild .targets files supposed to replace them? Care to enlighten us? :)

re: Using the Windows 7 RC SDK in Visual C++ 2010 Beta 1

Marian Luparu — Thu, 21 May 2009 19:45:22 GMT

@Jalf: both are valid statements :) property sheets are still there and they are MSBuild files. More specifically .props files.

The .props extension is a convention to represent MSBuild files that only contain properties, item definitions and items but no target definitions.

During conversion, your .vsprops files (VC property sheets) will get converted to semantically equivalent .props files.

Our overall goal was to ease migration from previous versions - you will notice that most of the VC Project System features are still there even if now under the covers they are expressed in MSBuild terms (i.e. property sheets, custom build rules, property inheritance in Property Pages, single file builds, etc.)

Thanks,

Marian

Visual C++

re: Using the Windows 7 RC SDK in Visual C++ 2010 Beta 1

Jalf — Thu, 21 May 2009 22:53:45 GMT

Thanks for the explanation. :)

I did notice that the extension had changed, and that the contents looked different in a text editor.

What had me confused was that there are still build options that are not exposed through the property pages for a property sheet (such as switching unicode on/off, or changing between .exe/.dll/.lib), but which should be possible to override with the new MSBuild build system.

So can I simply edit the .props file manually to specify those missing options? (Would be a lot nicer if I could simply include a .props file to build a static library instead of an executable. That was pretty much the scenario that sold me on the idea of switching to MSBuild)

Targets files for X64

Javier Blazquez — Fri, 22 May 2009 07:55:00 GMT

Even though the configuration files for building an X64 application targeting the Windows 7 RC SDK are not included in the ZIP above, it's easy to derive their contents judging from the differences between Microsoft.Cpp.Win32.v100.props and Microsoft.Cpp.X64.v100.props.

The contents of Microsoft.Cpp.X64.Windows7SDK.props would be the following:

<WindowsSdkDev10Dir Condition="'$(UseEnv)' != 'true'">$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.0A@InstallationFolder)</WindowsSdkDev10Dir>

<WindowsSdkDir Condition="'$(UseEnv)' != 'true'">$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.0@InstallationFolder)</WindowsSdkDir>

<ExecutablePath>$(VCInstallDir)bin\x86_amd64;$(VCInstallDir)bin;$(WindowsSdkDev10Dir)\bin\NETFX 4.0 Tools;$(WindowsSDKDir)\bin;$(VSInstallDir)Common7\Tools\bin;$(VSInstallDir)Common7\tools;$(VSInstallDir)Common7\ide;$(ProgramFiles)\HTML Help Workshop;$(FrameworkSDKDir)bin;$(FrameworkSDKDir)lib\win64;$(MSBuildToolsPath);$(FxCopDir);$(PATH);</ExecutablePath>

<IncludePath>$(VCInstallDir)include;$(VCInstallDir)atlmfc\include;$(WindowsSdkDir)\include;$(FrameworkSDKDir)include;</IncludePath>

<LibraryPath>$(VCInstallDir)lib\amd64;$(VCInstallDir)atlmfc\lib\amd64;$(WindowsSdkDir)\lib\x64;</LibraryPath>

<ExcludePath>$(VCInstallDir)include;$(VCInstallDir)atlmfc\include;$(WindowsSdkDir)\include;$(FrameworkSDKDir)include;$(MSBuildToolsPath);$(VCInstallDir)atlmfc\lib\amd64;$(VCInstallDir)lib\amd64;</ExcludePath>

</PropertyGroup>

</Project>

The other file, Microsoft.Cpp.X64.Windows7SDK.targets, would be identical to Microsoft.Cpp.Win32.Windows7SDK.targets, so you can just copy it and rename it.

Put both files under the MSBuild\Microsoft.Cpp\v4.0\Platforms\X64\PlatformToolsets\Windows7SDK directory and you'll be able to build an X64 application using the Windows 7 RC SDK. I tried building a simple X64 project and it worked fine on a Windows Server 2008 R2 RC virtual machine.

re: Using the Windows 7 RC SDK in Visual C++ 2010 Beta 1

Lisa Supinski, Windows SDK team — Sat, 23 May 2009 00:15:50 GMT

Phaeron - If you're asking whether it's a supported scenario to install Visual Studio and install a Windows SDK release and then use the headers and libraries that ship with the Windows SDK release while creating apps using Visual Studio, the answer is yes. If you are having problems with the headers that the SDK ships while you're writing code using Visual Studio, we want to know what the problems are so we can investigate. Does that answer your question?

re: Using the Windows 7 RC SDK in Visual C++ 2010 Beta 1

Stephan T. Lavavej [MSFT] — Sat, 23 May 2009 10:01:02 GMT

[Phaeron]

> I've had some headaches recently with the SDK's

> <winnt.h> declaring intrinsics in a manner

> incompatible with <intrin.h>

We've had the same headaches. VC10's <intrin.h> is finally compatible with <winnt.h>.

re: Using the Windows 7 RC SDK in Visual C++ 2010 Beta 1

David — Mon, 25 May 2009 20:52:32 GMT

I spent some time looking at the various .target files supporting the new C++ build system to get a grip of how it works, and noticed that the compiler and linker are compiled tasks - not defined entirely in XML as originally envisioned. Is this design final? I am trying to see how I would go about making a custom VC6 platform toolset for a legacy embedded platform, and having to write cusom task assemblies really complicates things. Simply being able to adapt existing XML files would be ideal.

Related question: How does the new MSBuild system do dependency analysis of header files? Is it even possible without custom compiled tasks?

re: Using the Windows 7 RC SDK in Visual C++ 2010 Beta 1

Gary — Wed, 27 May 2009 08:13:29 GMT

Does this break .NET Framework 4.0 development?

re: Using the Windows 7 RC SDK in Visual C++ 2010 Beta 1

Marian Luparu — Wed, 27 May 2009 08:53:40 GMT

@David: relying on XAML based tasks for build extension implementations is a supported scenario and something we'd like to get your feedback on.

We don't plan though to use XAMLTaskFactory for VC shipping tasks as there is some functionality needed that we don't plan to add to XAMLTaskFactory:

- dependency analysis (i.e. track header files)

- parent/child property relations

- build cancellation.

For dependency analysis, VC tasks use FileTracker which is a new feature in MSBuild 4.0. We'll share more information as more of our documentation becomes available. This will be something 3rd party task developers will be able to take advantage as well.

Thanks,

Marian

PS: I'd love to chat more about the VC6 platform toolset project you're working on if you'd like. Can you send me an email to mluparu at microsoft.com?

Visual Studio 2010 Beta1 includes the Windows 7 Beta SDK

ascend slowly, breathing normally — Wed, 10 Jun 2009 00:01:39 GMT

Wondering how to use the new Windows 7 SDK with Visual Studio 2010 Beta1? The Windows 7 SDK Beta version

re: Using the Windows 7 RC SDK in Visual C++ 2010 Beta 1

Criminet — Sun, 05 Jul 2009 08:10:41 GMT

I see this is only for C++ .. is there any way to use Win7 RC SDK with C#?

(i know you C++ guys are smart enough to make it happen)

assistance appreciated

re: Using the Windows 7 RC SDK in Visual C++ 2010 Beta 1

Criminet — Sun, 05 Jul 2009 08:22:28 GMT

erm ... C# 2010 Beta 1 that is

re: Using the Windows 7 RC SDK in Visual C++ 2010 Beta 1

reklam — Thu, 16 Jul 2009 01:54:38 GMT

This is very good news was well informed that the followers of the issue I am. Thanks...