DLL hell - existing installs of different versions of pywin32 cause dll conflicts in win32 code

[GoogleCodeExporter]

Standard pywin32 install puts a pywintypes25.dll in C:\Windows\System32. If
the build is different to that included in the MetaGETA package, a dll
conflict occurs.

To do:

Check if having a later version in C:\Windows\System32 than is included in
MetaGETA solves the problem. E.g try installing build 214
http://sourceforge.net/projects/pywin32/files/pywin32/Build%20214/pywin32-214.wi
n32-py2.5.exe/download
as normal and installing an earlier build to the MetaGETA python
site-packages dir.
Also, check what pywin32 build comes with ArcGIS.

Original issue reported on code.google.com by pinner.luke@gmail.com on 12 Feb 2010 at 1:10

[GoogleCodeExporter]

Windows DLL search path
http://msdn.microsoft.com/en-us/library/7d83bc18%28VS.80%29.aspx checks the 
directory
where the executable module for the current process is located first. To avoid
conflicts, pywintypes25.dll and pythoncom25.dll were copied to the MetaGETA
%PYTHONHOME% folder (and to %PYTHONHOME%\Lib\site-packages\pythonwin though this
should probably be left out of the download archive)

Original comment by pinner.luke@gmail.com on 12 Feb 2010 at 5:51

• Changed state: Fixed

[GoogleCodeExporter]

This issue was updated by revision r198.

import pywintypes & pythoncom before any other win32 import so the correct dlls 
get loaded as per - 
http://www.voidspace.org.uk/python/movpy/reference/win32ext.html

Original comment by pinner.luke@gmail.com on 12 Feb 2010 at 6:14

[GoogleCodeExporter]

This issue was updated by revision r199.

Backporting changes related to Issue 9 from trunk to 1.2

Original comment by pinner.luke@gmail.com on 15 Feb 2010 at 12:21