Kyle Alons wrote:
> VC++.NET has a nasty habit of adding per-file configuration settings when
> converting VC6 project files. Some of them are necessary (like precompiled
> header settings for stdafx.cpp, for instance), but many of them are often
> superfluous (like preprocessor settings). One way to resolve it is to
> manually open the .vcproj file and remove any unnecessary
> <FileConfiguration> elements (and/or its PreprocessorDefinitions
> attributes). Then your configuration-level settings will take effect for
> all files.
>

"Jonathan Rynd" <q7a3ofvtcm502@atsneakemail.com.invalid> wrote in message
news:Xns9607752D76D3Ajrr7hotmailcom@207.46.248.16...
> Hi,
>
> We have a project that was originally developed in VC++ 6.0. It had a
> dsw,
> a dsp, and a number of c, cpp, and h files.
>
> We upgraded to .NET (Microsoft Development Environment 2003 7.1.3088) and
> opened the DSP file. It was converted into a vcproj and a sln. After
> making necessary changes we got it to compile and link.
>
> Then it turned out we needed to modify some preprocessor definitions. In
> VC++ 6 we had set them in Project/Settings/C-C++/Preprocessor Definitions.
> Those settings carried over into .NET in the Project/Myproj Properties/C-
> C++/Preprocessor/Preprocessor Definitions.
>
> So we modified them there, recompiled, and found that our changes had no
> effect. The new preprocessor definitions showed up as undefined, and old
> preprocessor definitions that we had removed showed up as defined. We
> closed MSDE and re-opened it; our changes still showed up in the
> Preprocessor Definitions section but had no effect on the code.
>
> We can make other changes to the project properties and they do take
> effect
> -- the preprocessor definitions are the only ones that don't take.
>
> Is there someplace else to set up C++ preprocessor definitions in Visual
> Studio .NET?

"red floyd" <no.spam@here.dude> wrote in message
news:Oloi0dpGFHA.2280@TK2MSFTNGP15.phx.gbl...
> Where were the vaunted MS usability labs when they were developing the
> VS.NET (and VS.NET 2K3) UIs? It seems that they broke a bunch of stuff in
> the VS6 UI that worked a lot better (class wizard immediately comes to
> mind, and a bunch of stuff in the properties dialog).

>
> VC++.NET has a nasty habit of adding per-file configuration settings
> when converting VC6 project files

> What's the "official" way to set per-file configuration
> settings?