[python-win32] COM

[Win95 Dog Walker]

I don't believe it is necessary to either Unregister nor Register your COM
server because you've changed its code: only if you move it to a different
location or change the GUID or it becomes unsimple (supplies different|new
objects).

If you don't need the Visual Basic IDE during testing, you could just make
an executable and then run that. Or you could run it from VC6. And I believe
there is a utility program, in the VC6 Tools,  designed for testing COM
components (but it may want a type library).

HTH

----- Original Message -----
From: Keith Hickling
To: DogWalker
Sent: Friday, December 12, 2003 11:10 AM
Subject: Re: [python-win32] COM


Thanks very very much.

I had been tearing my hair out for two days trying to figure what was
happening.

Its a bit of bind having to close VB each time a change is made but I supose
most of the testing can be done in the Python scripts.

Do I have to unregister each time or can I just re-register the changes over
the top.

Martin
----- Original Message -----
From: DogWalker
To: Keith Hickling ; python-win32 at python.org
Sent: Friday, December 12, 2003 12:10 AM
Subject: Re: [python-win32] COM


When running from the Visual Basic IDE, it is necessary to completely exit
Visual Basic in order to get a new version of a COM server. VB does not
create a separate process to run your application from the IDE. Windows
keeps the version of the COM server that you invoked until all processes
which have invoked it are terminated. Therefore you must terminate the
instance of VB that was running the COM server.
----- Original Message -----
From: Keith Hickling
To: python-win32 at python.org
Sent: Thursday, December 11, 2003 2:13 PM
Subject: [python-win32] COM


Heeeeeellllp

I have created a com server in Python.

I can access it via Visual basic and it works.

If I make changes to the python server dsepite unregistering and
re-registering the server Visual basic cannot see the changes.

I have tested the new server via Python and the changes are registered.

I have removed the .pyc created by the module and recompiled vut Visual
Basic absolutly refuses to see the changes. I have unregistered rebooted and
re registered but still can find no way to force Visual basic to accept the
changes.

Where is the copy or the code that Visual Basic is seeing. How do I
implement the changes.

Yours desparatley.

Martin



_______________________________________________
Python-win32 mailing list
Python-win32 at python.org
http://mail.python.org/mailman/listinfo/python-win32