Xp Manifest in clarion program

[NewsArchive]

I accidently checked off the Generate XP manifest on the global area of a
program.

errently found out that was incorrect in Setupbuilder, that they would do it
instead.

now no matter what I do, deleting everything that may cause it, I cannot get
rid if it from the CW exe file...

anyone run into this and have an answer?


--
Andy <<Cowboy>> Stapleton
www.forexmgr.com
www.BlueCollarTradingSociety.com

[NewsArchive]

Project editor, Library, object, and resource files, MyApp.exe.manifest?

Greg Fasolt

[NewsArchive]

yea, if you use Setup builder , then don't do that. screws it up...

the SB6 is supposed to create it and imbed it in the exe, that is where the
problem lies, since I had done it in the CW, I cannot for the life of me get
SB6 to realise it is gone..


--
Andy <<Cowboy>> Stapleton
www.forexmgr.com
www.BlueCollarTradingSociety.com

[NewsArchive]

Just for the record (because quite a few developers read this thread). This
has nothing to do with SetupBuilder and it's not a SetupBuilder issue!

SB6 does not realize that the manifest in Andy's application is gone because
in fact it's still there <g>. In other words, Andy's application still has
a valid XP manifest embedded and so of course, SetupBuilder cannot embed the
Vista manifest. Per definition, an application can only have one manifest.

Andy is working on it.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Reminds me of when I had to pay for a printer repair just because I was
standing next to it when it smoked!

Cheers,
Paul

friedrich linder wrote:
> Just for the record (because quite a few developers read this thread). This
> has nothing to do with SetupBuilder and it's not a SetupBuilder issue!
>
> SB6 does not realize that the manifest in Andy's application is gone because
> in fact it's still there <g>. In other words, Andy's application still has
> a valid XP manifest embedded and so of course, SetupBuilder cannot embed the
> Vista manifest. Per definition, an application can only have one manifest.
>
> Andy is working on it.
>

[NewsArchive]

But it was your fault for letting the magic smoke out...

Skip

[NewsArchive]

Hi Friedrich, Andy,

>SB6 does not realize that the manifest in Andy's application is gone because
>in fact it's still there <g>. In other words, Andy's application still has
>a valid XP manifest embedded and so of course, SetupBuilder cannot embed the
>Vista manifest. Per definition, an application can only have one manifest.

I have taken several Clarion 6.3 (9053) apps, changed the XP Manifest
setting in the Clarion app, recompiled, added Vista manifest with SB
6.5/6.6/6.7 and never had this problem with the XP manifest getting
stuck in the exe. I've done this with several of my internal apps to
avoid any issues with executables on my network when running them from
vista.

Andy: Could it be that you have some other template that is adding a
XP manifest to the app? Check your global extension - not sure if
there is any template like that out there...

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com

Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

Same here. I have posted a HexEditor screenshot in the SetupBuilder
newsgroup. It shows that Andy's application has a XP manifest embedded.
That's why the SetupBuilder compilation process reports Error 50 ("manifest
already embedded"). This XP manifest comes from the Clarion compile because
SetupBuilder cannot embed a XP manifest - SetupBuilder only embeds a
Vista-aware manifest.

I also think that some other template is adding the XP manifest during the
Clarion compilation process.

Thanks,

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Maby a little o.t. but
If SB can only embed a vista manifest, what about the XP manifest? If you
have an app that is to be used on Both WinXP And Vista, you must (as i see
it) embed both a XP and a Vista manifest, or ????
The way i do it, is to Not use the CW method, and Not use the SB method but
use the Jane method, wich is to include a Both.Manifest with this content:

<?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="Vipilon.Bowling"
type="win32" />
<description>Vipilon Bowling Turnerings Program</description>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel
level="asInvoker"
uiAccess="false" />
</requestedPrivileges>
</security>
</trustInfo>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
</assembly>


Is there a better / more correct way to do it, with SB ??

--
Kind regards / Med Venlig Hilsen
Viggo Poulsen
Vipilon ApS
www.vipilon.dk

[NewsArchive]

Hi Viggo,

>have an app that is to be used on Both WinXP And Vista, you must (as i see
>it) embed both a XP and a Vista manifest, or ????

Vista manifest works perfectly with XP:)

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com

Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Viggo,

Of course, SetupBuilder 6 embeds a Vista-aware manifest that is compatible
with XP, Vista and Windows Server 2008! The SetupBuilder manifest is fully
backward compatible. It does not make any sense to include a "XP only"
manifest any longer.

BTW, when I said that SetupBuilder can only embed a "Vista-aware manifest",
I just wanted to point out that the manifest in Andy's application is a "XP
only" manifest and so it was definitely embedded during the Clarion
compilation process and *not* during the SetupBuilder compile!

Does this help?

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Thank you, now it makes sense

--
Kind regards / Med Venlig Hilsen
Viggo Poulsen
Vipilon ApS
www.vipilon.dk

[NewsArchive]

> If SB can only embed a vista manifest, what about the XP manifest?

You don't need anything but SetupBuilder.

Just tell SB to add the manifest and your done.

PageSnip looks perfect under both Vista and XP.


I do NOT check any box in Clarion or have Clarion add one.

I DO keep an external manifest file in the development folder so that when
I compile I can see what the final results will look like.

When I run the app, the external manifest is used and that is all there is
too it.


The problem a lot of people have is that they try to overthink the
solution.


Just let Friedrich do all the work!


;-)

Charles

--
-------------------------------------------------------------------------------------------------------
Charles Edmonds

www.clarionproseries.com - "Serious imaging tools for Clarion Developers"
www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
and Forms!"
www.lansrad.com - "Intelligent Solutions for Universal Problems"
www.fotokiss.com - "World's Best Auction Photo Editor"
-------------------------------------------------------------------------------------------------------

[NewsArchive]

> I accidently checked off the Generate XP manifest on the global area of a
> program.
>
> errently found out that was incorrect in Setupbuilder, that they would do it
> instead.
>
> now no matter what I do, deleting everything that may cause it, I cannot get
> rid if it from the CW exe file...
>
> anyone run into this and have an answer?

Hi Andy,

It's not clear from the thread whether or not you solved the problem.
Try deleting the .EXP file for the APP. This is where the XP manifest
support for the built-in Clarion manifest is added. It is possible the
template isn't smart enought to realize the EXP file needs to be changed
when you uncheck the option.

JAT,
Rick

[NewsArchive]

Andy solved the problem.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner