Author lemburg
Recipients aheider, cgohlke, christian.heimes, jdetaeye, koen, lemburg, loewis, mhammond, zhirsch
Date 2009-10-12.22:24:01
SpamBayes Score 1.14444e-08
Marked as misclassified No
Message-id <1255386243.56.0.505772662943.issue4120@psf.upfronthosting.co.za>
In-reply-to
Content
Looking at the description of manifest files, it appears that just
removing the assemblyIdentity-element results in an invalid manifest file:

http://msdn.microsoft.com/en-us/library/aa374219(VS.85).aspx

It appears that the entire dependency-element referencing the MS VC90
CRT DLL has to be removed in order to make the manifest correct again.

Looking at the schema, it's enough to just remove the
dependentAssembly-element:

http://msdn.microsoft.com/en-us/library/aa375635(VS.85).aspx

Reading up on the manifest trouble-shooting page at (near the end of the
page):

http://msdn.microsoft.com/en-us/library/ms235342.aspx

it may actually be enough to just place the Microsoft.VC90.CRT.manifest
file into the Python folder (the one with python.exe and the CRT DLLs):

"""
If the operating system fails to find the CRT or any other assembly as a
shared assembly, it starts looking for the assembly as a private
assembly. It searches for private assemblies in the following order:

   1. Check the application local folder for a manifest file with name
<assemblyName>.manifest. In this example, the loader tries to find
Microsoft.VC90.CRT.manifest in the same folder as appl.exe. If the
manifest is found, the loader loads the CRT DLL from the application
folder. If the CRT DLL is not found, load fails.
"""
History
Date User Action Args
2009-10-12 22:24:03lemburgsetrecipients: + lemburg, loewis, mhammond, christian.heimes, koen, aheider, zhirsch, jdetaeye, cgohlke
2009-10-12 22:24:03lemburgsetmessageid: <1255386243.56.0.505772662943.issue4120@psf.upfronthosting.co.za>
2009-10-12 22:24:02lemburglinkissue4120 messages
2009-10-12 22:24:01lemburgcreate