redoing manifest file for .NET 2.0

[Brian Henry]

I get an error with .NET 2.0 saying the manifest file is invalid for my
archatecture (x86-64bit) it is the same one i used on my old machine
x86-32bit, but it is set up for the 6.0 controls in 32bit only...so i cant
set the files to compile to "any cpu" i have to set it to "x86" only... if
at any cpu if fails to start at a manifest error (and im not going to use
the app framework this is a converted app that is huge and doesn't need
rewritten for the app framework)

here is my old manifest file from 1.1, how would i change this to get it to
work on any cpu (32bit or 64bit) in .net 2.0? thanks!

<?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="Microsoft.Winweb.BenefitsApp"

type="win32"

/>

<description></description>

<dependency>

<dependentAssembly>

<assemblyIdentity

type="win32"

name="Microsoft.Windows.Common-Controls"

version="6.0.0.0"

processorArchitecture="X86"

publicKeyToken="6595b64144ccf1df"

language="*"

/>

</dependentAssembly>

</dependency>

</assembly>

 

[Brian Henry]

because the controls still do not load with version 6 ones with out it in
converted projects from 1.1... they also do this when you make new 2.0
projects with out using the "application framework" which would require
rewriting a large portion of code since our exe's are only loader apps that
run external dll's that are the main application so since you can't have a
sub main when the app framework is enabled, it makes it really hard to do...
so disableing the framework makes the old non version 6 comm controls come
back and things like alpha channels and such no longer work... and
application.enablevisualstyles does nothing to help either....

 

[Herfried K. Wagner [MVP]]

I get an error with .NET 2.0 saying the manifest file is invalid for my
archatecture (x86-64bit) it is the same one i used on my old machine
x86-32bit, but it is set up for the 6.0 controls in 32bit only...so i cant
set the files to compile to "any cpu" i have to set it to "x86" only...

I am curious why you would want to use a manifest file with .NET 2.0...

 

[Brian Henry]

nevermind, I guess enable visual styles does work right now with out the
manifest..

because the controls still do not load with version 6 ones with out it in
converted projects from 1.1... they also do this when you make new 2.0
projects with out using the "application framework" which would require
rewriting a large portion of code since our exe's are only loader apps
that run external dll's that are the main application so since you can't
have a sub main when the app framework is enabled, it makes it really hard
to do... so disableing the framework makes the old non version 6 comm
controls come back and things like alpha channels and such no longer
work... and application.enablevisualstyles does nothing to help either....