Re: XP Manifest hell?

Tech-Archive recommends: Fix windows errors by optimizing your registry

Anthony <Anthony@xxxxxxxxxxxxxxxxxxxxxxxxx>'s wild thoughts
were released on Wed, 25 Oct 2006 12:46:03 -0700 bearing the
following fruit:

I am unable to figure out this manifest thing. I use a manifest file for my
vb6 apps (just like everyone else) so they take on the theme of the OS.

For certain apps, with no apparent common thread of relation, I cannot get
the manifest to work -- meaning, the application simply refuses to start,
UNLESS I either...

1) remove the manifest file
2) Set the compatibility mode of the executable to ANYTHING other that winXP
(and then it takes on the theme like I expect)

The same identical manifest works on other applications just fine.

I have pasted the manifest below. Does anyone know what I could be looking
for to solve this issue?

Since you didn't mention it I suspect Ken has given you the
solution. If the manifest file already exists when you run
the application AND you havened made the call to
InitCommonControls then you get exactly the circumstance you
describe - your app won't run.

J

===========================
<?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="CompanyName.ProductName.YourAppName"
type="win32" />
<description>Your application description here</description>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*" />
</dependentAssembly>
</dependency>
</assembly>
=========================


Jan Hyde (VB MVP)

--
Artifacts: Information on painters (Jonathan Delaney)

.

Relevant Pages

  • Re: ! Manifests not added to resources in VS.NET 2003
    ... > of my apps created with VS.NET 2002 properly initialize and use the ... manifest resource entry is a bug pure and simple, ... Either this was all the fix they had time for, ... personally recall hearing tell of them. ...
    (microsoft.public.vc.mfc)
  • Re: Vista and Name function
    ... In regard to the manifest issue, the Vista manifest has a "uiaccess" node ... Except for admins, that wouldn't even work under Win2000 ... Gotta test your apps under non-admin accounts. ...
    (microsoft.public.vb.general.discussion)
  • Re: How to work around UAC?
    ... Yoiu are going to need to manifest all *your* apps as this will prevent ... virtualization, and it will properly cause "Administrator" prompts to appear ... Nothing works with UAC turned on. ...
    (microsoft.public.platformsdk.security)
  • Re: ! Manifests not added to resources in VS.NET 2003
    ... of my apps created with VS.NET 2002 properly initialize and use the manifest ... When I generate an MFC dialog based project with a manifest, ... > Well, here's a wrinkle...The project is created with a conditional manifest> entry in the *.rc file, but as soon as I make even the slightest change --> like deleting that default "Place controls here" static, the manifest> resource entry is removed. ...
    (microsoft.public.vc.mfc)
  • ClickOnce and Side-by-Side com components
    ... + Parsing and DOM creation of the manifest resulted in error. ... COMPONENT STORE TRANSACTION FAILURE SUMMARY ...
    (microsoft.public.dotnet.framework.windowsforms)