This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 35%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMY%3C/text%3E%3C/svg%3E)
I have a multi-project solution built in Visual Studio 2022. I'd like to set the default Windows SDK Version explicitly so all projects use the same library. However, it seems like I have to change it in each library, explicitly.
Can this setting be put into a shared props file that all my projects inherit? Or is there a place where it can be configured explicitly?
A high-level, general-purpose programming language, created as an extension of the C programming language, that has object-oriented, generic, and functional features in addition to facilities for low-level memory manipulation.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 40%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJP%3C/text%3E%3C/svg%3E)
Hello @Max Yaffe ,
As RLWA32 mentioned, the AI's solution with Directory.Build.props won't work if your individual .vcxproj files already have the SDK or Toolset hardcoded.
To fix this, you need to right-click on each individual C++ project in the Solution Explorer and open their Property Pages. If the Windows SDK Version or Platform Toolset values appear in bold, they are currently overriding the global settings. You must clear those values (or select <inherit from parent or project defaults>).
Once the bold formatting is removed from all projects individually, they will correctly inherit the unified values from your root Directory.Build.props file.
If you found my response helpful or informative, I would greatly appreciate it if you could follow this guide provide feedback. Thank you.
Thanks, I will try this again. It would be great though if these configurations were allowed in a simple props file that I could edit from the config manager window.
Hello Max Yaffe,
Have you had a chance to try my workaround? Could you please let me know the result?
Hello @Max Yaffe
Hi, I wonder if there is any update on this post. If you have any question, feel free to reach out. I'm happy to support you.
@Max Yaffe If opening many projects in the VS IDE to manually remove properties stored in their .vcxproj file is overly burdensome you could remove such settings programmatically. The time and effort to write a small utility to update a .vcxproj file's xml for a large number of projects may be worth it.
Thanks to all.
I have tried the Directory.Build.Props approach and am using Notepad++ to do global search and destroy on the vcxproj files.
The way that vcxproj tries to manage all the variants is a crying shame. They are just dangerous to the unwary.
If I could manage everything from props files things would be simple. I build a props file for each variant/output type and stack these up for the project. Finally I have a props file corresponding to the project name that sets the final, unique settings for a given project, e.g. additional libraries, paths, names...
Hi @Max Yaffe
If my explanation was helpful so far, I would greatly appreciate it if you could follow this guidance provide feedback.
I am essentially doing that but trying to carefully remove entries in the text file.
There is a caveat to the "bold format" hint. One can override a directive at any level with blank text. But blanks don't show up in bold format. A better design would leave a hint like <EMPTY> in the field.
Hi @Max Yaffe ,
Thanks for your explanation. I appreciate your feedback, and I’ll share it with the Product Group team for consideration in future updates.
Thanks again.
Yes. The Windows SDK version and Platform Toolset can be centralized in shared MSBuild props so all projects inherit the same values.
A common approach is to use a Directory.Build.props file placed at the solution root. MSBuild automatically imports this file for all projects under that directory, so properties defined there apply to every project unless overridden in the individual .vcxproj.
For example, create Directory.Build.props next to the solution file with content similar to:
<Project>
<PropertyGroup>
<!-- Shared Windows SDK version -->
<WindowsTargetPlatformVersion>10.0.19041.0</WindowsTargetPlatformVersion>
<!-- Shared Platform Toolset (for example, v143 for VS 2022) -->
<PlatformToolset>v143</PlatformToolset>
</PropertyGroup>
</Project>
All C++ projects under that folder will then use the same WindowsTargetPlatformVersion and PlatformToolset, unless a project explicitly overrides them in its own .vcxproj.
The same mechanism is used in the GDK documentation to override MSBuild properties globally via Directory.Build.props for things like PlatformToolset, Windows SDK paths, and Visual Studio–specific overrides.
References:
I tried the AI's solution by placing the file Directory.build.props in the solution root directory. It did not work.
@Max Yaffe If the .vcxproj files include settings for the WindowsTargetPlatformVersion and PlatformToolset properties they will override the Directory.Build.props file.
If you open the project property pages and the properties appear in bold it means they have been set in the .vcxproj file and are not coming from the Directory.Build.props file.
Yes, I am aware that these entries can be set in the .vcxproj files and that they appear in bold. What I am looking for is one overriding place I can set these in the solution.
Normally, I create a props file with solution-wide configuration info and layer special-case props files over that. I would love to be able to set compiler and windows version info in this props file but I have not been able to. Is there a way around that?
@Max Yaffe The manner in which .props and .target files are imported into a project ensures that the content of the .vcxproj file is the final override.
You can see this here - Customize C++ builds