FUSION error

Hello,

I'm trying to compile a console application that should run on various
Windows OSs including Vista for x64. Because of Vista I need to embed a
manifest file. However using the build tool with the DDK 3790.1830 I get
an error

2>NMAKE : U1234: 'FUSION_MANIFEST_VALIDATOR' :
objfre_wnet_AMD64\amd64\regpmc.m
an(11) - Element content is invalid according to the DTD/Schema.

The manifest I try to embed is as follows
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
version=SXS_ASSEMBLY_VERSION
processorArchitecture=SXS_PROCESSOR_ARCHITECTURE
name=SXS_ASSEMBLY_NAME
type="win32"
/>
<description>Port Monitor registration command line tool</description>
<asmv2:trustInfo xmlns:asmv2="urn:schemas-microsoft-com:asm.v2">
<asmv2:security>
<asmv2:requestedPrivileges>
<asmv2:requestedExecutionLevel
level="asInvoker"
uiAccess="false"/>
</asmv2:requestedPrivileges>
</asmv2:security>
</asmv2:trustInfo>
</assembly>

The problem seems to be that the validator doesn't accept the asmv2
construction. I tried to work around this by declaring the whole
assembly urn:schemas-microsoft-com:asm.v2 but this causes x64 executable
to run under Windows XP x64. Is there anyway around this?

Kind regards,
Theo

Maxim
Thu Mar 20 06:15:35 CDT 2008

I never validated the manifest besides of testing it, I just included it to
the .RC file and did nothing else.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

"Theo Landman" <tlandman_NO_SPAM@justcroft_NO_SPAM.com> wrote in message
news:%23y0ZEFniIHA.5152@TK2MSFTNGP02.phx.gbl...
> Hello,
>
> I'm trying to compile a console application that should run on various
> Windows OSs including Vista for x64. Because of Vista I need to embed a
> manifest file. However using the build tool with the DDK 3790.1830 I get
> an error
>
> 2>NMAKE : U1234: 'FUSION_MANIFEST_VALIDATOR' :
> objfre_wnet_AMD64\amd64\regpmc.m
> an(11) - Element content is invalid according to the DTD/Schema.
>
> The manifest I try to embed is as follows
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
> <assemblyIdentity
> version=SXS_ASSEMBLY_VERSION
> processorArchitecture=SXS_PROCESSOR_ARCHITECTURE
> name=SXS_ASSEMBLY_NAME
> type="win32"
> />
> <description>Port Monitor registration command line tool</description>
> <asmv2:trustInfo xmlns:asmv2="urn:schemas-microsoft-com:asm.v2">
> <asmv2:security>
> <asmv2:requestedPrivileges>
> <asmv2:requestedExecutionLevel
> level="asInvoker"
> uiAccess="false"/>
> </asmv2:requestedPrivileges>
> </asmv2:security>
> </asmv2:trustInfo>
> </assembly>
>
> The problem seems to be that the validator doesn't accept the asmv2
> construction. I tried to work around this by declaring the whole
> assembly urn:schemas-microsoft-com:asm.v2 but this causes x64 executable
> to run under Windows XP x64. Is there anyway around this?
>
> Kind regards,
> Theo

Theo
Thu Mar 20 08:11:36 CDT 2008

I'm using the following keywords in my Sources file

SXS_ASSEMBLY_NAME=Print.Monitors.regpmc
SXS_ASSEMBLY_LANGUAGE_INDEPENDENT=1
SXS_MANIFEST=regpmc.manifest
SXS_MANIFEST_IN_RESOURCES=1
SXS_NO_BINPLACE=1

I found it in the localui sample delivered with the DDK. Apparently this
triggers the validation.

Maxim S. Shatskih schreef:
> I never validated the manifest besides of testing it, I just included it to
> the .RC file and did nothing else.
>

Alexander
Thu Mar 20 08:24:08 CDT 2008

If you see these SXS_ASSEMBLY_VERSION, SXS_PROCESSOR_ARCHITECTURE,
SXS_ASSEMBLY_NAME, then they didn't get substituted to necessary strings.

"Theo Landman" <tlandman_NO_SPAM@justcroft_NO_SPAM.com> wrote in message
news:%23y0ZEFniIHA.5152@TK2MSFTNGP02.phx.gbl...
> Hello,
>
> I'm trying to compile a console application that should run on various
> Windows OSs including Vista for x64. Because of Vista I need to embed a
> manifest file. However using the build tool with the DDK 3790.1830 I get
> an error
>
> 2>NMAKE : U1234: 'FUSION_MANIFEST_VALIDATOR' :
> objfre_wnet_AMD64\amd64\regpmc.m
> an(11) - Element content is invalid according to the DTD/Schema.
>
> The manifest I try to embed is as follows
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
> <assemblyIdentity
> version=SXS_ASSEMBLY_VERSION
> processorArchitecture=SXS_PROCESSOR_ARCHITECTURE
> name=SXS_ASSEMBLY_NAME
> type="win32"
> />
> <description>Port Monitor registration command line tool</description>
> <asmv2:trustInfo xmlns:asmv2="urn:schemas-microsoft-com:asm.v2">
> <asmv2:security>
> <asmv2:requestedPrivileges>
> <asmv2:requestedExecutionLevel
> level="asInvoker"
> uiAccess="false"/>
> </asmv2:requestedPrivileges>
> </asmv2:security>
> </asmv2:trustInfo>
> </assembly>
>
> The problem seems to be that the validator doesn't accept the asmv2
> construction. I tried to work around this by declaring the whole assembly
> urn:schemas-microsoft-com:asm.v2 but this causes x64 executable to run
> under Windows XP x64. Is there anyway around this?
>
> Kind regards,
> Theo

Theo
Thu Mar 20 09:02:28 CDT 2008

These are preprocessing macros which are declared in the Sources file.
This is expanded by build to
<assemblyIdentity
version="5.1.0.0"
processorArchitecture="AMD64"
name="Print.Monitors.regpmc"
type="win32"
/>
Note: The program has to be build for different architectures, so that's
the reason I'm using the SXS_XXXX macros. Else I could use a fixed
manifest file.

Alexander Grigoriev schreef:
> If you see these SXS_ASSEMBLY_VERSION, SXS_PROCESSOR_ARCHITECTURE,
> SXS_ASSEMBLY_NAME, then they didn't get substituted to necessary strings.
>
> "Theo Landman" <tlandman_NO_SPAM@justcroft_NO_SPAM.com> wrote in message
> news:%23y0ZEFniIHA.5152@TK2MSFTNGP02.phx.gbl...
>> Hello,
>>
>> I'm trying to compile a console application that should run on various
>> Windows OSs including Vista for x64. Because of Vista I need to embed a
>> manifest file. However using the build tool with the DDK 3790.1830 I get
>> an error
>>
>> 2>NMAKE : U1234: 'FUSION_MANIFEST_VALIDATOR' :
>> objfre_wnet_AMD64\amd64\regpmc.m
>> an(11) - Element content is invalid according to the DTD/Schema.
>>
>> The manifest I try to embed is as follows
>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
>> <assemblyIdentity
>> version=SXS_ASSEMBLY_VERSION
>> processorArchitecture=SXS_PROCESSOR_ARCHITECTURE
>> name=SXS_ASSEMBLY_NAME
>> type="win32"
>> />
>> <description>Port Monitor registration command line tool</description>
>> <asmv2:trustInfo xmlns:asmv2="urn:schemas-microsoft-com:asm.v2">
>> <asmv2:security>
>> <asmv2:requestedPrivileges>
>> <asmv2:requestedExecutionLevel
>> level="asInvoker"
>> uiAccess="false"/>
>> </asmv2:requestedPrivileges>
>> </asmv2:security>
>> </asmv2:trustInfo>
>> </assembly>
>>
>> The problem seems to be that the validator doesn't accept the asmv2
>> construction. I tried to work around this by declaring the whole assembly
>> urn:schemas-microsoft-com:asm.v2 but this causes x64 executable to run
>> under Windows XP x64. Is there anyway around this?
>>
>> Kind regards,
>> Theo
>
>