VB Controls, Windows XP Style Manifest doesn't work on ActiveX Control Projects

Windows XP Style Manifest doesn't work on ActiveX Control Projects

Author	Message
Maxi #1 / 4	Windows XP Style Manifest doesn't work on ActiveX Control Projects Hi All! I'm testing some of my VB projects applying the XP Style Mainfest, so that my application will use the new XP style buttons, scroll bars, progress bars and so on. What I did was just put the manifest file into the project directory and done. I've tried this method and it works well on "Standard EXE" projects. However, when I tried this method to an "ActiveX OCX" project, it doesn't work. This is what I've tried: - First I created a ActiveX Control Project with one ActiveX Control in it. I named that control "MyTestControl" and the project "MyTestProject". - Next, I put a VB.CommandButton on "MyTestControl". - Then I save the project and complie it into "MyTestProject.ocx". - Then I put the Manifest file in my control project directory, and renamed "MyTestProject.ocx.manifest". After creating the control, I created a Standard EXE project to test the control. Steps are as follows... - I create a New Standard EXE project. - Then, I reference the control via Componets dialog. - Next, I create an instance of the "MyTestControl" control on the form. And the VB.CommandButton in the MyTestProject.MyTestControl doesn't appear as Windows XP style. So I've tried this: - Complie the test Standard EXE to Test.exe - Run the Test.exe And the VB.CommandButton in the MyTestProject.MyTestControl STILL doesn't appear as Windows XP style. So my conclusion to the manifest files is that, they only work against the Standard EXE projects and NOT to the other projects such as OCXs and DLLs. Am I right? OR did I overlook something? How to set the Windows XP Style to OCX projects? Cheers, Maxi
Thu, 08 Sep 2005 13:41:09 GMT

Markus Weber Megali #2 / 4	Windows XP Style Manifest doesn't work on ActiveX Control Projects You must create Manifest always for EXE never for OCX. If you created for EXE all OCX (also your self created) are converted. For Windows Common Control Version 6 this doesn't work. You get also problems if you want to use buttons or optionbuttons within a frame. Quote: >Hi All! >I'm testing some of my VB projects applying the XP Style Mainfest, so that >my application will use the new XP style buttons, scroll bars, progress bars >and so on. What I did was just put the manifest file into the project >directory and done. >I've tried this method and it works well on "Standard EXE" projects. >However, when I tried this method to an "ActiveX OCX" project, it doesn't >work. >This is what I've tried: >- First I created a ActiveX Control Project with one ActiveX Control in it. >I named that control "MyTestControl" and the project "MyTestProject". >- Next, I put a VB.CommandButton on "MyTestControl". >- Then I save the project and complie it into "MyTestProject.ocx". >- Then I put the Manifest file in my control project directory, and renamed >"MyTestProject.ocx.manifest". >After creating the control, I created a Standard EXE project to test the >control. Steps are as follows... >- I create a New Standard EXE project. >- Then, I reference the control via Componets dialog. >- Next, I create an instance of the "MyTestControl" control on the form. >And the VB.CommandButton in the MyTestProject.MyTestControl doesn't appear >as Windows XP style. So I've tried this: >- Complie the test Standard EXE to Test.exe >- Run the Test.exe >And the VB.CommandButton in the MyTestProject.MyTestControl STILL doesn't >appear as Windows XP style. >So my conclusion to the manifest files is that, they only work against the >Standard EXE projects and NOT to the other projects such as OCXs and DLLs. >Am I right? OR did I overlook something? How to set the Windows XP Style to >OCX projects? >Cheers, >Maxi
Fri, 09 Sep 2005 19:27:29 GMT

Rayne Bai #3 / 4	Windows XP Style Manifest doesn't work on ActiveX Control Projects Quote: > For Windows Common Control Version 6 this doesn't work. You get also > problems if you want to use buttons or optionbuttons within a frame. I noticed that on an application that I am working on. My listview didn't get the xp style. What is the easiest way to get the listview control and the others to be "skinned" by the xp style? Also, I read that you can add the manifest to your resource file instead of putting it in your application's directory. What are the benefits, if any, to doing it that way and also how exactly do I do this? Add it as a string? or custom file? Thanks. Rayne
Sun, 11 Sep 2005 02:34:38 GMT

Markus Weber Megali #4 / 4	Windows XP Style Manifest doesn't work on ActiveX Control Projects If you use Manifest file and your Listview has no XP style you use "Windows Common Controls 6". XP Style doesn't work with this version. You must use Version 5 of the control.. On Tue, 25 Mar 2003 12:34:38 -0600, "Rayne Bair" Quote: >> For Windows Common Control Version 6 this doesn't work. You get also >> problems if you want to use buttons or optionbuttons within a frame. >I noticed that on an application that I am working on. My listview didn't >get the xp style. What is the easiest way to get the listview control and >the others to be "skinned" by the xp style? >Also, I read that you can add the manifest to your resource file instead of >putting it in your application's directory. What are the benefits, if any, >to doing it that way and also how exactly do I do this? Add it as a string? >or custom file? >Thanks. >Rayne
Sun, 11 Sep 2005 19:50:15 GMT

Page 1 of 1

[ 4 post ]