|
In VS2005 for an upgraded project (originally created in VS2003) I also needed to insert the following in my stdafx.h:
#ifdef _UNICODE
#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
Hope that helps...
|
|
|
|
|
Hi all,
I have an application in vc6,in that i am using XP style.
The way I am giving XP Style to my application is by adding an XML File
to my resource . The content of the Xml file is given below
/******************************************************************************/
manifestVersion="1.0">
version="1.0.0.0"
processorArchitecture="X86"
name="Microsoft.Windows.YourApplication"
type="win32"
/>
LitmusPro
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
/****************************************************************************/
It is working fine in VC6 .
But, when I compile my application in Visual Studio 2005 , this is not working . How can I make it work.
Please Help me
Thanks
Vinod
|
|
|
|
|
In VS 2005 you can include via the project settings "Manifest" and "include additional Manifest".
Then delete it out of your resources and watchout that no other Manifests are in your Projects your you ran into troble.
"There only be can One"
Greetings from Germany
|
|
|
|
|
That was great help!!! Thanks a lot...
There is a much easier way to do this in Visual Studio 2005...
http://www.mathies.com/weblog/?p=225
|
|
|
|
|
|
THANK YOU! It was just the thing I was looking for! THANK YOU!THANK YOU!THANK YOU!
|
|
|
|
|
Your article just slove my problem!
Thankyou!
|
|
|
|
|
VS 2005 automatically generates manifest files with its manifest tool. This tools is enabled by defualt when you create a new project.
Following these directions will cause a resource collision error. There are two simple steps to resolve this:
1. Turn off this feature (loses manifest generation by code)
Project->Properties->Configuration Properties->Manifest Tool:
Set Embed Manifest to "No"
2. Use this code as an additional manifest (Best) by saving the code above in an xml file
Project->Properties->Configuration Properties->Manifest Tool->Input and Output
Add the code as an "Additional Manifest File"
|
|
|
|
|
Hi I am creating a ATL/COM Addin dll in VS 2005. The Project already creates manifest files. If I set
Manifest Tool:
Set Embed Manifest to "No" My application is not working because of the default dependency on ATL80.dll. Only if Embedded Manifest is allowed My Addin works but with out the XP theme. Please help me.
|
|
|
|
|
Could some one point me in the direction of a general manifest creation tutorial or give me a manifest file that will link well with my x64 application? My 32bit version works fine ;o)
|
|
|
|
|
Found it myself in another file, I cant get this forum to post it right, but the neccesary parts are there.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"><br />
<assemblyIdentity<br />
version="1.0.0.0"<br />
processorArchitecture="amd64" name="Logitech.GamingDesktop.LGDCore" type="win32"<br />
/><br />
<br />
<description>Logitech Gaming Desktop Core Service.</description><br />
<dependency><br />
<dependentAssembly><br />
<assemblyIdentity<br />
type="win32"<br />
name="Microsoft.Windows.Common-Controls"<br />
version="6.0.101.0"<br />
processorArchitecture="amd64"<br />
publicKeyToken="6595b64144ccf1df"<br />
language="*"<br />
/><br />
</dependentAssembly><br />
</dependency><br />
</assembly>
|
|
|
|
|
I have tried following this procedure, but get the following error when I try to run the application on XP (it runs OK on 2000):
"The application has failed to start because the application configuration is incorrect."
The only difference I can see is that I have no WinMain - as its an MFC project, so I have put the InitCommonControls() call into InitInstance(). Should this work with an MFC application?
Can anyone help?
|
|
|
|
|
Hi Kinnos,
I've had the same problem!
While doing the copy/paste, somehow a <PRE...> tag was added to the manifest code. I simply removed this tag (and of course the final </PRE> tag also) in notepad and copied/pasted again to DevStudio. And viola ... the App was XP-ready
Ahh, one second slight change: I changed 'processorArchitecture="x86"' to 'processorArchitecture="*"'
The final manifest code looks as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly
xmlns="urn:schemas-microsoft-com:asm.v1"
manifestVersion="1.0">
<assemblyIdentity
processorArchitecture="*"
version="5.1.0.0"
type="win32"
name="RapidX.exe"/>
<description>RapidX</description>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
publicKeyToken="6595b64144ccf1df"
language="*"
processorArchitecture="*"/>
</dependentAssembly>
</dependency>
</assembly>
My App is also MFC, the InitCommonControls call is also placed at 'InitInstance'.
Hopefully this helps,
Hartmut
|
|
|
|
|
I should have realized "<pre...>" tag.
I've just copy and paste. foolish..
ew
|
|
|
|
|
Thank you Man. It worked.
|
|
|
|
|
When changing the color of the editbox control in the dialog, the control behave strange. Try entering some text and remove it using backspace. The text does not seem to remove from the control until you tab to other controls.
This does not happened when using window classic theme.
Any ideas how to solve this issue?
|
|
|
|
|
Just to clarify that the strange behaviour is still there even changing to classic theme in WinXP.
|
|
|
|
|
Is it possible to add Windows XP Theme Style manifest to a Microsoft Visual C++.NET projekt?
I tried to upgraded the "Add Windows XP Theme Style to your current projects" source to a C++.NET projekt, but i just want a Form1 with the manifest instead of a Dialog, which the XP style are added to.
Microsoft Visual Studio.NET / File / New / Projekt / C++ / Forms Application (.NET)
What shall i do from this position, to add the WinXP Theme Style, in the new C++.NET project?
-- modified at 15:43 Thursday 1st December, 2005
|
|
|
|
|
I have succeeded in applying the XP Visual Styles in one of my project compiled in VC++ 6.0 following the steps of Jiang Hong, but when I converted it to Visual Studio 2005 for VC++, it went back to the old style .
The Microsoft MSDN website refers to the FlatStyle of the control, but I couldn't find it anywhere in the VC++ .NET 2005!
If any of you know about it, please let us know.
Thanks.
|
|
|
|
|
From VS2005 this is even easier with no additional code.
You can simply embed your manifest file into your executable.
See you project properties. Configuration Properties > Manifest Tool > Input and Output. And simply add your manifest file to 'Additional Manifest File' and rebuild. It's that simple.
|
|
|
|
|
Its not that simple, if you link against MSVCRT80.dll it requires a manifest. If you use your own manifest VS2005 will overwrite it. If you disable the manifest your app won't be able to start.
|
|
|
|
|
Can finally get rid of this manifest file. To me, it's always better to present one exe to the customer, iso an exe and a manifest file.
Best rgds,
--Geert
= Prediction is very difficult, especially about the future +
|
|
|
|
|
I'm using PropertySheet window under WinXP that I do not have control over and it doesn't have XP visual styles. Is there a way to apply this manifest on the fly when program is running?
|
|
|
|
|
|
Hi,
I am a bit lost here... where exactly in VC++ 6 IDE do I need to apply step #3 (change ID to 1)?
Please advice, thanks!
-dD
|
|
|
|