Manifest Doesn't Work
Rick Raisley
hospital, my brain doesn't seem to be working properly (yes, I'm going to
use that excuse).
I've been using manifest files on a number of apps, which appear to work
fine. But I just tried copying one for use on another app, written, compiled
and being run on WinXP, and when starting the app, I just get a big "beep",
and nothing appears. As mentioned above, I think I remember something about
that, but can't seem to find it (or remember specifics). This is my manifest
file:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
version="1.0.0.0"
processorArchitecture="X86"
name="R-View.exe"
type="win32" />
<description>R-View Manifest File</description>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*" />
</dependentAssembly>
</dependency>
</assembly>
Any idea what I'm missing?
--
Regards,
Rick Raisley
heavymetal-A-T-bellsouth-D-O-T-net
Wolfgang Enzinger
>I've been using manifest files on a number of apps, which appear to work
>fine. But I just tried copying one for use on another app, written, compiled
>and being run on WinXP, and when starting the app, I just get a big "beep",
>and nothing appears. As mentioned above, I think I remember something about
>that, but can't seem to find it (or remember specifics).
I seem to remember that the manifest file size must be a multiple of 4
for unknown reasons ... add some spaces if needed.
HTH,
Wolfgang
Rick Raisley
news:87fpe4d268qkvm773...@4ax.com...
Thanks, but that didn't do it. I'm thinking the multiple of 4 rule only
applies for embedded manifest files; I'm using an external one.
Wolfgang Enzinger
>> I seem to remember that the manifest file size must be a multiple of 4
>> for unknown reasons ... add some spaces if needed.
>>
>
>Thanks, but that didn't do it. I'm thinking the multiple of 4 rule only
>applies for embedded manifest files;
true
>I'm using an external one.
My bad, should have noticed that.
More ideas:
* Is the Version info in the manifest file the same as in the EXE? I
read domewhere that this can cause problems, however I never could
reproduce them.
* Do you call InitCommonControls immediately after the program starts?
Wolfgang
Rick Raisley
> On Wed, 8 Oct 2008 10:24:13 -0400, "Rick Raisley" wrote:
>
>>> I seem to remember that the manifest file size must be a multiple of 4
>>> for unknown reasons ... add some spaces if needed.
>>>
>>
>>Thanks, but that didn't do it. I'm thinking the multiple of 4 rule only
>>applies for embedded manifest files;
>
> true
>
>>I'm using an external one.
>
> My bad, should have noticed that.
>
> More ideas:
> * Is the Version info in the manifest file the same as in the EXE? I
> read domewhere that this can cause problems, however I never could
> reproduce them.
I don't think the actual text in the manifest describing the program is
actually used anywhere.
> * Do you call InitCommonControls immediately after the program starts?
>
No, forgot about that. I'm pretty sure that's it, at least it rings a bell.
IIRC, some programs worked fine without that, while others didn't. Thanks
for jogging my memory; I'll add it and see what happens then.
Randy Birch
you should put it somewhere prior to any forms being loaded. On vista this
has to be a bas module, from my testing. On xp, the initiate event of the
form is OK too. You don't have to worry about "calling it too many times"
.. use it by default in all projects, and you'll be assured it works.
--
Randy Birch
ms mvp - visual basic
http://vbnet.mvps.org/
"Rick Raisley" <heavymetal-A-T-bellsouth-D-O-Tnet> wrote in message
news:%23c1NX4V...@TK2MSFTNGP05.phx.gbl...
PeterD
>I think I remember something about this, but after just getting out of the
>hospital, my brain doesn't seem to be working properly (yes, I'm going to
>use that excuse).
>
>I've been using manifest files on a number of apps, which appear to work
>fine. But I just tried copying one for use on another app, written, compiled
>and being run on WinXP, and when starting the app, I just get a big "beep",
>and nothing appears. As mentioned above, I think I remember something about
>that, but can't seem to find it (or remember specifics). This is my manifest
>file:
>
First have you tried this on Vista? Vista will (about the only thing
it will do properly) generate event log information that may give you
a clue to what is going wrong. XP just won't do anything other than
fail to run.
Kevin Provance
misplaced XML in manifests. Not as well as Server 2003. :-)
I think, after having dealt with this time and time again that is has to do
with the call to Init the common controls not being present in the
executable itself.
- Kev
"PeterD" <pet...@hipson.net> wrote in message
news:rh0qe4tnods4lrmbo...@4ax.com...
Karl E. Peterson
> I think I remember something about this, but after just getting out of the
> hospital, my brain doesn't seem to be working properly (yes, I'm going to
> use that excuse).
Don't feel bad...
Seriously OT: http://www.youtube.com/watch?v=JYFm5kK4f1k
--
.NET: It's About Trust!
http://vfred.mvps.org
Rick Raisley
call a sub from the Form's event, or is that no different?
--
Regards,
Rick Raisley
heavymetal-A-T-bellsouth-D-O-T-net
"Randy Birch" <rgb_rem...@mvps.org> wrote in message
news:uACL0nWK...@TK2MSFTNGP05.phx.gbl...
Kevin Provance
Form_Initialize as this is called before the controls are created.
- Kev
"Rick Raisley" <heavymetal-A-T-bellsouth-D-O-Tnet> wrote in message
news:%23svNxYj...@TK2MSFTNGP04.phx.gbl...
Steve Easton
It has to be in sub main because it has to initialize "before" the form loads.
The following courtesy of Randy Birch:
--
Steve Easton
Option Explicit
Public Type tagInitCommonControlsEx
lngSize As Long
lngICC As Long
End Type
Public Declare Function InitCommonControlsEx Lib "comctl32.dll" (iccex As tagInitCommonControlsEx) As Boolean
Public Const ICC_USEREX_CLASSES = &H200
Public Sub Main()
' we need to call InitCommonControls before we
' can use XP visual styles. Here I'm using
' InitCommonControlsEx, which is the extended
' version provided in v4.72 upwards (you need
' v6.00 or higher to get XP styles)
On Error Resume Next
' this will fail if Comctl not available
' - unlikely now though!
Dim iccex As tagInitCommonControlsEx
With iccex
.lngSize = LenB(iccex)
.lngICC = ICC_USEREX_CLASSES
End With
InitCommonControlsEx iccex
' now start the application
On Error GoTo 0
Form1.Show
End Sub
"Rick Raisley" <heavymetal-A-T-bellsouth-D-O-Tnet> wrote in message
news:%23svNxYj...@TK2MSFTNGP04.phx.gbl...
Randy Birch
adding a sub main to call initcc before showing the form, even if that's all
sub main does.
--
Randy Birch
ms mvp - visual basic
http://vbnet.mvps.org/
"Kevin Provance" <kevin@remove_tpasoft_remove.com> wrote in message
news:uAGSBhjK...@TK2MSFTNGP04.phx.gbl...
Rick Raisley
I notice, however, that when using the Graphical style of OptionButtons that
they are not updated to the XP look as are CommandButtons, which look the
same but operate differently. (Actually, the Graphical style of any button
seems to not be updated.) Any easy answer to that? I prefer their button
look in this case to the standard ones.
--
Regards,
Rick Raisley
heavymetal-A-T-bellsouth-D-O-T-net
"Randy Birch" <rgb_rem...@mvps.org> wrote in message
news:OA239IkK...@TK2MSFTNGP02.phx.gbl...
Ken Halter
> Thanks all for the info. That was, indeed, the problem.
>
> I notice, however, that when using the Graphical style of OptionButtons
> that they are not updated to the XP look as are CommandButtons, which look
> the same but operate differently. (Actually, the Graphical style of any
> button seems to not be updated.) Any easy answer to that? I prefer their
> button look in this case to the standard ones.
INFO: Visual Basic 6.0 Does Not Support Windows XP Themes or Visual Styles
http://support.microsoft.com/kb/309366/en-us
Option buttons must be in a container that exposes an hdc property... and
all bets are off when their style is set to Graphical.
There are replacements available on PlanetSourceCode.com and/or you can
create your own option button/checkbox controls.