A guide to .vcxproj and .props file structure

re: A guide to .vcxproj and .props file structure

Fri, 05 Apr 2013 07:39:12 GMT

NA6RDRWS9K KVNXJJXJJVJIXMCJNCIKM JCIJXNZCHB UVOXCKVJU9VFPKGJFI0VVJIFO0FOF9OF0OFK,VNMKD;PXLJBIGOFOLFOLFODOOPD

re: A guide to .vcxproj and .props file structure

Maddie — Mon, 11 Mar 2013 13:02:13 GMT

Would you please provide solution for the problem I mentioned at following link?

www.codeproject.com/.../includepluspropertyplussheetplusinplusVisualplusC

Thanks.

re: A guide to .vcxproj and .props file structure

bgcjdh — Sun, 13 Jan 2013 21:08:42 GMT

fyhfovhfgvp\zhsdfhijfiv\iogfj

re: A guide to .vcxproj and .props file structure

DM — Thu, 18 Oct 2012 19:52:45 GMT

Has the ability to define project configurations in an import been implemented in VS 2010 SP1 or VS 2012?

Can anyone from the VS team confirm?

Thank you in advance,

re: A guide to .vcxproj and .props file structure

Steve Dillon — Tue, 01 Mar 2011 19:22:04 GMT

I would like a way to get a property sheet before the CPP settings, so that we can share default settings between projects. Namely we would like to set WindowsSdkDir off to a common location and not depend on locally installed wsdk.

With the current setup the IncludePath is already formed (and the Default WindowsSdkDir is injected in it) by the time the property sheet import happens. I need to overwrite and re-create the whole include path.

It's not the end of the world but a way to get a property sheet into the "Globals" section via the Property Manager would be cool.

Thanks,

Steve

re: A guide to .vcxproj and .props file structure

Attila Szabo — Mon, 21 Feb 2011 16:58:47 GMT

Now that VS 2010 SP1 beta is out, can someone confirm if the ability to define project configs in an imported property sheet is a feature of VS 2010 SP1?

Thanks

-Attila

re: A guide to .vcxproj and .props file structure

Visual Studio Blog — Tue, 25 May 2010 01:53:56 GMT

@Matt, @Filip, @jalf,

The ability to define project configurations in an import is being considered for SP1. And there is a good chance that it will actually make it.

Thanks,

Pavan Adharapurapu

Software Developer,

Visual Studio Project & Build Team,

Microsoft.

re: A guide to .vcxproj and .props file structure

dan moseley — Sun, 16 May 2010 00:31:54 GMT

@jalf it is something I hope is fixed. I will ask the VC folks about it.

Meanwhile there is a sort-of-workaround which may help, or not, depending on what you are trying to do. What it is looking for is just the configuration definitions. So this minimal .vcxproj will load successfully:

<?xml version="1.0" encoding="utf-8"?>

<Configuration>Debug</Configuration>

</ProjectConfiguration>

<Configuration>Release</Configuration>

</ProjectConfiguration>

</ItemGroup>

</Project>

In "test.targets" I just pasted the rest of the body of a regular .vcxproj project file, plus the root <Project> tag of course.

If what you're trying to move out is what each configuration "does" -- for example, in Debug configuration define _DEBUG -- rather than what the various configuration names are, then this workaround might be good enough. Be aware that VS won't allow you to edit items that are defined in an imported file, so you'd want to keep those in the main project file. Also, it may not edit the main project file quite how you want, especially if you modify configuration-dependent properties for a particular project. But I guess if you do that, you're telling it that you want a special value for that project.

Does this help?

Dan [msbuild dev lead]

re: A guide to .vcxproj and .props file structure

jalf — Sat, 15 May 2010 12:50:49 GMT

Yep, what Matt said.

I tried creating an Import statement factoring the ProjectConfigurations out into a separate file. Visual Studio reported that my project file was no longer valid.

I don't see why this scenario isn't supported though. It seems pretty obvious that if you have multiple projects, you want to be able to define new ProjectConfigurations once, in a common file, instead of by editing each and every project.

Hopefully it is just a bug in the current version of VS. Right?

re: A guide to .vcxproj and .props file structure

Filip — Sat, 15 May 2010 03:09:01 GMT

Good, helpful post. I'm with Matt on the issues of sharing configuration between different projects. We are having exactly this problem at work.

It would be awesome to just import one settings file and have all projects use the same settings. I totally don't understand why each project file needs to have its own "configuration" (debug/release/etc). Can the common settings file contain configuration definitions for all projects? Not sure if VS is smart enough to understand that... Also, is there a way of telling VS to honor whitespace in project files? It's really annoying when each time a project is saved the whitespace gets deleted. Whitespace is essential. Especially for the C++ crowd. Lots of folks are coming from the makefile world. Reading tons of XML makes their brains hurt. Space between elements would help.