Welcome to MSDN Blogs Sign in | Join | Help

Internal Manifest vs External Manifest

Internal manifest is the RT_MANIFEST resource in the executable. 

External manifest is App.exe.manifest.

In Windows XP, Sxs searches external manifest before internal manifest. If an external manifest is found, the internal manifest is ignored.

 In Windows Server 2003 and later, the order is reversed.  Internal manifest is preferred over external manifest.

If you use external manifest, and your scenario works in Windows XP, but not Windows Server 2003 and later, please double check the executable does not have an internal manifest

Published Monday, May 11, 2009 8:00 AM by junfeng
Filed under:

Comments

# Internal Manifest vs External Manifest | ASP NET Hosting

Monday, May 11, 2009 11:42 AM by Internal Manifest vs External Manifest | ASP NET Hosting

PingBack from http://asp-net-hosting.simplynetdev.com/internal-manifest-vs-external-manifest/

# .NET – My application works on XP but not Server 2003, Vista, Server 2008, Windows 7…

Monday, May 18, 2009 2:09 PM by Professional Software Architecture

Application manifests work differently between XP and the 2003/Visa cores.  On Windows XP the external

# re: Internal Manifest vs External Manifest

Thursday, June 04, 2009 8:41 AM by J.

Hi,

Can you explain us what was the reason behind this change?

If we consider a situation where you want to modify a manifest, it looks more handy that you can override the default one with an external file. Having the internal one more priority forces to modify the .exe which would mean to modify also the build number in most cases.

New Comments to this post are disabled
 
Page view tracker