Question

Locked

Manifest files

By Slayer_ ·
I came across an interesting MSDN page
http://support.microsoft.com/kb/309366
Describing a little file called a manifest that allows XP theming to be applied to VB6 programs (and apparently VB5 programs :) ).
So I tried it out on some of our applications at work, and it worked... mostly. Some controls, such as date pickers, are not getting themed.
My boss saw my experiment and got very excited.
I am having trouble researching these files and how they work. the word manifest seems popular among languages. Can someone point me in the right direction?

Thanks.

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

test

by PurpleSkys In reply to Manifest files
Collapse -

Reponse To Answer

by Slayer_ In reply to test
Collapse -

Reponse To Answer

by PurpleSkys In reply to test

yeah...sorry about that SS...i was difficulty trying to get some thing to post in another spot so i picked a spot to "test". :) And the other test failed too...only it just plain didn't post

Collapse -

I had a look at them but for .net and local COM

by Tony Hopkinson In reply to Manifest files

Turned out to be non-starter for other reasons, but like you I struggled to find decent information about what did what. VB6 being pre XP makes it even more problematic.

Looks like MS have been pulling some of the stuff they used to have on it as well.

Regoogling found this, don't know whether it's right though.

In VB6, you must initialise the common controls (via an API call) for every form, before the form becomes visible:

Private Declare Function InitCommonControls _
Lib "Comctl32.dll" () As Long
Private Sub Form_Initialize()
InitCommonControls
End Sub

Makes sense in a way, as the equivalent tip for .net was to chnage the flatsyle of every ui component to system, to get the manifest to be used with it.

Collapse -

Reponse To Answer

by Slayer_ In reply to I had a look at them but ...

I did do that, but I notice it is not required. On a program with no custom controls, it works fine. According to MSDN, InitCommonControls is a dead function since version 6 of the common controls.

Hopefully someone can find some good documentation on it.

Collapse -

Documentation for things they do not want you to know sucks

by seanferd In reply to Manifest files

almost as bad as the documentation for things you normally need to know.

Manifest XML files seem to be pretty standard for applications meant to run under Windows. But what exactly do you want to know about them? I don't think they are going to fix the unsupported theme-ing problem, that's not what they do.

The specification: http://www.osta.org/mpv/public/specs/XML-Manifest-Spec-1.01.pdf

The result I get here look pretty good, but again, I'm not to sure what you are looking for. http://www.google.com/search?ie=UTF-8&oe=utf-8&q=XML+manifest+files
or
http://www.google.com/search?ie=UTF-8&oe=utf-8&q=MS+Windows+application+XML+manifest+files

Like this MSDN article http://msdn.microsoft.com/en-us/library/aa3741**.aspx

Themes are applied just due to the fact that the app has a manifest, so I'd just find some MS manifest files from Windows or other MS applications and have a look at the format. Just search the system directory for *.manifest for Microsoft examples.

If you really want to get deep into uncertain territories, look at the XP theme sites, which provide themes and a hacked version of uxtheme.dll which allows you to apply them.

edited due to shifting my hand one key over (upi → you)

Back to Software Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums