[python-win32] Problem registering COM server at installation time

[Malte Forkel]

According to eryk, it might help to "create a context at runtime from
the manifest that's
embedded in python27.dll". How would I do that? It sounds to me like it
requires Windows programming skills (which unfortunately I don't have).

Does "later MSVC versions no longer have this stupid requirement" mean
that I shouldn't have a problem creating the COM server at installation
time if a moved to Python 3.x?

Malte


Am 01.02.2016 um 23:24 schrieb Mark Hammond:
> Eryk's reply is right on the money - I'd forgotten about that. IIRC,
> having that manifest directly in pythoncomxx.dll or pywintypesxx.dll
> ended up using a different activation context, which had its own
> problems; that loader module exists purely to work around these problems.
>
> I'm still a bit confused as to why bdist_wininst isn't working for you
> when that's the exact same stub used by the pywin32 installer, which
> obviously does manage to load Python ok.
>
> (The good-ish news is that later MSVC versions no longer have this
> stupid requirement, but that doesn't help the 2.x series)
>
> Mark
>
> On 2/02/2016 9:17 AM, Malte Forkel wrote:
>> Am 01.02.2016 um 05:42 schrieb Mark Hammond:
>>> On 17/01/2016 6:51 AM, Malte Forkel wrote:
>>>> Hi,
>>>>
>>>> I'm trying the register a COM server using the install script of a
>>>> built
>>>> distribution, created with the  bdist_wininst format of distutils. But
>>>> the script fails with a message that MSVCR90.dll can't be found.
>>>> Registering the server after the installer is done works fine. I'm
>>>> using
>>>> Python 2.7.11 and pywin32-220 on Windows 7.1 64 bit.
>>>
>>> That sounds a little strange - the script should only be executed
>>> after python27.dll is loaded, which itself relies on msvcr90.dll.
>>>
>>> Does it happen to work if you put the installer executable in the same
>>> directory as python27.dll?
>>>
>>> Mark
>>
>> Yes, same problem if the installer is run from C:\Windows\System32.
>>
>> Malte
>>
>
>