Re: pull request #829 (Reduced vs2010+ file sizes by removing redundant config settings)

[Geoff Evans]

Hi,

LTTP on this one, sorry.  Google groups has locked the prior thread from David. I agree that one of the nice things about project generation is that it can render settings that have native "look & feel" their respective environments, and would second a motion to back out any change that breaks how properties are natively organized in the target environment.

My day job has switched to props files for a lot of build configuration management, and the fact that it renders much of the property window useless is frustrating. Granted that UI wasn't great to begin with, but it's a nice feature to continue to support when something isn't building as expected, and one goes digging through the build properties to figure out why.

Cheers,

-geoff

[Tom van Dijck]

I don't think backing out infrastructure vital to some projects is a good idea.... but I can see options to make it an 'optional' feature.

as in... switch it on/off...

But as said in another thread... this forum is hardly the place to be these days... I advise to take suggestions or bug reports like this to github's issue tracker, and discuss things there.

Tom.

[Geoff Evans]

Uh, ok.

Sorry, there were no infrastructure callouts in the PR; at face value it seemed motivated more toward the experience of reading the generated file (callouts to redundancy) than fixing any issue or helping to operate at some scale.

[David Gregory]

I had no idea that these forums were considered "dead". I have reposted this question as an issue in github, so consider this thread closed now.

-Dave