|
Not sure you still need this, but you can define the manifest directly into your project options. Check for something called Manifest whatever, then go to Input and Output. There should be there a field called additional manifest files, so write there the name of your manifest at it will be embedded instead of the regular one (which doesn't allow XP themes).
As for the reply above, your method didn't work for me. :/
|
|
|
|
|
I'm developing a DLL addin of Outlook which will be called by Outlook. I do like the articale said, but it does not work. Anyone has this kind of experience?
Thanks
Justin Li
-----------
www.rollingsoftware.com
|
|
|
|
|
Not long ago, I had the same question, and I remembered reading an essay which says 'change resource ID to 2(or someone else? It's been such a long time that I am not so sure now) in implementing dll', however, I still failed.
But just now, when I came back 2 rebuild my dll program, an idea suddenly come in 2 my mind: How abt. just 2 insert this resource into the app. who calls my dll, and finally I think I got the solution.
And I still wondering if there is any other methods like just changing the resource ID in the dll itself, and anyone who got the idea > share it with us..please
|
|
|
|
|
Hello,
I create a simple IE toolbar in VC6 ATL COM. But it appears in Classic style. Is there any method to convert it into XP style.
Ansif
|
|
|
|
|
Hello.
I guess your IE Toolbar is a DLL.
To enable XP style on your project create manifest file described on this article and do the two single steps:
Put this line on your stdafx.h
#define ISOLATION_AWARE_ENABLED 1
And these lines on your resource file
#include <windows.h><br />
ISOLATIONAWARE_MANIFEST_RESOURCE_ID RT_MANIFEST "yourapp.dll.manifest"
I hope it works.
More information can be found here http://msdn2.microsoft.com/en-us/library/ms649781.aspx[^]
Best Regards
Rafael Franco.
|
|
|
|
|
Hi,
My toolbar is a DLL. And I´m doing these steps, but my toolbar for IE doesn´t work with XP styles.
Could you help me?
Thanks in advance.
|
|
|
|
|
I added Xp style to my application.
But the problem was there was a border around the button i created using
CButton::Create()
So i need to get rid of that problem.pls reply me
bhw
|
|
|
|
|
How to add xp style in visual studio 2008 please help me i an unable to add xp style and cant use in windows form appplication
|
|
|
|
|
I add Windows XP Theme Style via manifest file in the same application folder.
And now I not see the focus rectangle when a button gets the focus.
Anyone knows how to fix it?
Note: I don't use MFC, I calls the Windows API directly.
Thanks for your useful article.
Conxita
|
|
|
|
|
I can't change the check box text color after I apply the XML to my project.
I change the text color in OnCtlColor via SetTextColor.
But It doesn't work.
How can I change the text color?
|
|
|
|
|
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.
|
|
|
|