[Visual C++ 2005 Express Edition] Configuration Manager

[benny!]

Hi.

I just downloaded the Visual C++2005 Express Edition from Mircosoft. I wanted to set up a project using
a certain configuration. I successfully created a new configuration file using configuration manager. But it
I cannot change any of the property values in the core windows librabry property pages (e.g. I
wanted to change some things in C/C++ --> Runtime library and so on). All entries are diabled 

Can anyone point me into the right direction !?

Any help appreciated.

[Rbz]

I guess that you need to follow, step by step, this link -> http://msdn.microsoft.com/vstudio/express/visualc/usingpsdk/

[benny!]

@Rbraz:

Thanks for the link ... but I already did this step to make sure I can create pure winApi-executables.
Are you sure these steps are related to my problem. Or are there any more values I can change in
the AppSettings.htm ?

[benny!]

@topic:

Strange ... now I found out how it works ... but it really make no sense for me 

So, if anyone else run into this trouble - here the result of my "research".


You cannot change the properties of e.g. :

Debug|Win32 -> Core Windows Library -> C++ -> General

if you do the following:

(1) Go into the Property Manager
(2) Right Click on Debug|Win32 -> Core Windows Library
(3) Choose Property

At least on my configuration all Entries are disabled and you cannot change them.


However, here the way you can change them :

(1) Go into the Property Manager
(2) Right Click on Debug|Win32
(3) Choose Property

And now you can change all properties...


At least in my eyes this is a bit confusing ... but who cares in the end

[taj]

Well for sure not microsoft.

[Rbz]

@benny: Very strange, but for me I never see that happening because I ways go to Project --> ProjectName Properties or press ALT+F7

Cheers,

[benny!]

Well for sure not microsoft.

@taj:

yup ... but besides that I start to like the ide. I touched VC++ 6.0 years ago and didn't really like it.
But the current version works very well for me ... although I cant resist the feeling that m$ copied
some of the features of eclipse 


@rbraz:

Hmm .. I'll try that way as soon I am back home ... I always clicked on the Project Properties
bottom tab and did it like I described above ... well ... never tried the keyboard shortcut though..

[Clyde]

Cheers for the heads up Benny dude.

[benny!]

No problem mate. 

[taj]

@taj:

yup ... but besides that I start to like the ide. I touched VC++ 6.0 years ago and didn't really like it.
But the current version works very well for me ... although I cant resist the feeling that m$ copied
some of the features of eclipse 

Well its not a bad tool but two pet peeves:
1. Its damn hard to get it working first time. I know experienced users who are just completely screwed up by it. Luck has a lot to do with it working it seems.
2. Deprecation of standard C functions!! Yes I know the security issues with string functions but *no* Microsoft does not have the righ to mess with the C standard outside the ANSI process.

[Jim]

You can define a pre-processor symbol in the project->properties->C++->pre-preprocessor->pre-preprocessor definitions called _CRT_SECURE_NO_DEPRECATE.  That stops all the warnings about C runtime.

It's a PITA but just reading Bugtraq http://www.securityfocus.com/archive/1 for a few minutes tells you that buffer overflows are the major cause of security problems.  If I was writing the next secure OS using VS2005, I think I'd do something similar.

The standard Microsoft has implemented to get round these warnings is TR 24731, an open standard for Safer C runtime http://www.open-std.org/jtc1/sc22/wg14/www/projects, so it's not a total hack, I can see most C/C++ compilers shipping with this runtime in the near future, and it being portable.  Download n1146.pdf for the unratified standard.

Jim

[taj]

Jim,

Stopping warnings is not the issue. There are of course lots of ways to stop them (eg pragmas).

I agree, its wise to address these issues. No doubt. No dispute. Thats not my issue either.
I agree, its done referring to an open recommendation. I read the document last week.

My point is that it is not being agreed with the ANSI committee first. Even _if_ the standard is likely to be the one adopted, it is not being done to an agreed timeframe and procedure. Yes, members of the ANSI committee are spitting furballs over this. No company should be allowed to railroad decisions like this. It took nearly ten years to get C stable, and whilst I do understand the need for a company to move faster than standards, the correct procedure is to define a standard (or use an existing one as you refer to), to mandate its use throughout your company and in parallel to work with the standards committee to agree on fine detail and procedure.

Even if one is a Microsoft fan, but this is just plain railroading. It is unacceptable behaviour of a (near) monopolist and should not be tolerated. Hell I even spoke to one of their compiler development team and
a) She didnt know for sure they were speaking to ANSI
b) She didnt really care
c) She flippantly referred to a web document she found to prove Microsoft were talking to ANSI
c) She dismissed the matter with the usual security marketing rubbish without even trying to understand why say strcpy is more risky than strncpy and hence why they *might* be treated differently.

I dont put a lot of weight in Microsoft decisions with this kind of attitude in their team.

[Jim]

I agree with you that in general the attitude they've taken is aggressive and unilateral.  That's what Microsoft do.
I'd prefer a 'Use Safer C library' check box defaulting to off.

Jim