Visual Studio 2008, Command bars 12.0 problem

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

Hi!

I am using  windows visual styles in my application, and since I updates my project to VS 2008 (from VS 6.0), it suggested I use #include <vssym32.h> instead of tmschema.h, so I did. Now I get error C2011 when compiling my project, because both VSStyle.h (from MFC90) and tmschema.h (from Xtreeme Commandbars code) are defining same enums.

Are there some special project settings I have to set to avoid this problem?

Anyone has similar expirience, and maybe a solution?

Thanks!

Sincerely,

Bojan Hrnkas

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Tsenoh Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 08 November 2006 Status: Offline Points: 69	Post Options Post Reply Quote Tsenoh Report Post Thanks(0) Quote Reply Topic: Visual Studio 2008, Command bars 12.0 problem Posted: 09 June 2008 at 6:52am
	Hi! I am using windows visual styles in my application, and since I updates my project to VS 2008 (from VS 6.0), it suggested I use #include <vssym32.h> instead of tmschema.h, so I did. Now I get error C2011 when compiling my project, because both VSStyle.h (from MFC90) and tmschema.h (from Xtreeme Commandbars code) are defining same enums. Are there some special project settings I have to set to avoid this problem? Anyone has similar expirience, and maybe a solution? Thanks! Sincerely, Bojan Hrnkas

Oleg Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 21 May 2003 Location: United States Status: Offline Points: 11234	Post Options Post Reply Quote Oleg Report Post Thanks(0) Quote Reply Posted: 09 June 2008 at 3:55pm
	Hi, Just use tmschema.h. :-)
	Oleg, Support Team CODEJOCK SOFTWARE SOLUTIONS

Tsenoh Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 08 November 2006 Status: Offline Points: 69	Post Options Post Reply Quote Tsenoh Report Post Thanks(0) Quote Reply Posted: 10 June 2008 at 4:11am
	well, that's what I did, than. :) I assume you are going to update the Toolkit in one of the future versions to accomodate this change?

Oleg Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 21 May 2003 Location: United States Status: Offline Points: 11234	Post Options Post Reply Quote Oleg Report Post Thanks(0) Quote Reply Posted: 11 June 2008 at 1:01am
	Hi, Anoter solution is to put #include <vssym32.h> before you include toolkit in stdafx.h.
	Oleg, Support Team CODEJOCK SOFTWARE SOLUTIONS