Different styles in different builds

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

   Hello, I encountered problem when doing different builds. For my project I was using codejock .lib for my main project. 

The project setting and code are basically the same except the following parameters:

For my debug build, 
Use Of MFC: Use MFC in a Shared DLL
Runtime Library: Multi-threaded Debug DLL (/MDd)
Everything seems alright and the resulting program shows interface with new styles as shown on new1.jpg and new2.jpg

For my release build,
Use of MFC: Use MFC in a Static Library
Runtime Library: Multi-threaded (/MT)
Same interface but with old styles as shown on old1.jpg and old2.jpg

 uploads/20090311_031811_controls.zip

Any reason for that? 

-- 
     Product: Xtreme Controls 2006 Q3
     Platform: Windows XP (32bit) - SP 2 
     IDE: Microsoft Visual C++ 2005
--

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
ferr Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 11 March 2009 Status: Offline Points: 2	Post Options Post Reply Quote ferr Report Post Thanks(0) Quote Reply Topic: Different styles in different builds Posted: 11 March 2009 at 3:12am
	Hello, I encountered problem when doing different builds. For my project I was using codejock .lib for my main project. The project setting and code are basically the same except the following parameters: For my debug build, Use Of MFC: Use MFC in a Shared DLL Runtime Library: Multi-threaded Debug DLL (/MDd) Everything seems alright and the resulting program shows interface with new styles as shown on new1.jpg and new2.jpg For my release build, Use of MFC: Use MFC in a Static Library Runtime Library: Multi-threaded (/MT) Same interface but with old styles as shown on old1.jpg and old2.jpg uploads/20090311_031811_controls.zip Any reason for that? -- Product: Xtreme Controls 2006 Q3 Platform: Windows XP (32bit) - SP 2 IDE: Microsoft Visual C++ 2005 --

Oleg Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 21 May 2003 Location: United States Status: Offline Points: 11234	Post Options Post Reply Quote Oleg Report Post Thanks(0) Quote Reply Posted: 12 March 2009 at 2:07am
	Hi, Add in stdafx.h #if (_MSC_VER > 1310) // VS2005 #if defined _M_IX86 #pragma comment(linker,"/manifestdependency:\"type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='x86' publicKeyToken='6595b64144ccf1df' language=''\"") #elif defined _M_IA64 #pragma comment(linker,"/manifestdependency:\"type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='ia64' publicKeyToken='6595b64144ccf1df' language=''\"") #elif defined _M_X64 #pragma comment(linker,"/manifestdependency:\"type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='amd64' publicKeyToken='6595b64144ccf1df' language=''\"") #else #pragma comment(linker,"/manifestdependency:\"type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='' publicKeyToken='6595b64144ccf1df' language='*'\"") #endif #endif
	Oleg, Support Team CODEJOCK SOFTWARE SOLUTIONS

ferr Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 11 March 2009 Status: Offline Points: 2	Post Options Post Reply Quote ferr Report Post Thanks(0) Quote Reply Posted: 12 March 2009 at 5:35am
	Hi, thanks for your suggestion, but I had no luck with this. Actually suggested code is already in stdafx.h. Any other clue?

mitcheljh Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 20 July 2008 Location: United States Status: Offline Points: 35	Post Options Post Reply Quote mitcheljh Report Post Thanks(0) Quote Reply Posted: 04 March 2010 at 2:07pm
	We just updated to Visual Studio 2008. After updating, we noticed alpha blending issues. I suspected it had something to do with the manifest, and discovered this post. Added the suggested changes to our stdafx.h, and it cleared up our problems. Thanks!