Tuesday, 7 July 2009

Visual C++/Studio: Incorrect Application Configuration ?

Ref : http://typethinker.blogspot.com/2007/12/visual-c-application-configuration.html

The author has indicated the copyright violation, thus content has been removed and just the link has been kept.

Please advise if the link is invalid by adding a comment.



  1. Well said. Now if only Microsoft would listen.

    It gets worse though. Say you wish to create a library and you don't want to distribute the DLL install pack with it, so you link statically. If someone then compiles against your library using a different runtime library (say like...the default) then BAD things happen. If you pass any object (memory, a file pointer etc) across those boundaries, you get a seg fault with an equally vague error message. This, to me, seems like a crazy restriction. Microsoft knows all about this (see http://msdn.microsoft.com/en-us/library/ms235460.aspx), but doesn't seem to have any plans to fix it. Even a compile warning would be good - if dependency walker can figure out what runtime you're using, why can't the MS compiler?

  2. Hey, stealing other people's content is not cool