Re: VB6 Regfree Com
- From: Ulrich Korndoerfer <ulrich_wants_nospam@xxxxxxxxxxxx>
- Date: Fri, 20 Jul 2007 02:18:41 +0200
Hi,
Anthony wrote:
...
For clarification, here is what I would like to do.
1) Place all DLL and OCX files in app directory, and create the appname.exe.local file to force the exe to use local files
2) Use Regfree COM to get those registered on the fly (I *do* need to do this, right?)
Is this possible? This seemingly simply thing that would make things soooo easy? Can anyone point me to a good article on how to do this (complete with CLSID's) for the Regfee com manifests)?
There is a ready to use, very small and *free* dll (named DirectCOM.Dll), specifically tailored for the use with VB6. Get it from
http://www.thecommon.net/10.html
The dll itself is a standard (non COM server) dll and needs no registering. Put it in your applications path (simplest) or anywhere else. It allows you to instantiate objects from COM servers *without* the need to register them. There is a CreateObject method for this, which needs the prog id of the class.
The COM server file may be anywhere on disk, not necessarily in the application directory. You even can use multiple versions of a COM server side by side. Or distribute your own copy of an eg MS control, such beeing sure using the correct version, no matter wether the control (possibly with an other version than yours) already exists and is registered on the pc. Of course you also can use a registered COM server with this dll, it does not matter. The point is: the COM server may be unregistered, and stays unregistered when used with DirectCOM.Dll.
The dll uses standard, completely legal win api calls. There is nothing peculiar with the inner working of the dll, no hacks, just using official, legal methods. It is little known that Windows allows using of COM objects that have not been registered. Registering is not necessary for using COM objects, it just helps finding the necessary informations for instantiating.
For best comfort during development the procedure would be:
- Register the COM server you want to use *on the development pc*.
- In the VB IDE add a reference to it.
Above two steps are the same as with normal, not reg free, development. Now the COM server can be used as usual, getting all he comfort like intellisense and so on. The only difference is that for instantiating you must not use VBs New operator or VBs CreateObject method. Instead you use the the DirectCOM.dlls CreateObject method.
- When development has finished, deploy the application, the COM server and the DirectCOM.dll to the target system by just copying them to the target system (real xcopy deployment). On the target system there is no need to register the COM server! But of course the VB runtime with its supporting files must be present, as usal.
--
Ulrich Korndoerfer
VB tips, helpers, solutions -> http://www.proSource.de/Downloads/
.
- Follow-Ups:
- Re: VB6 Regfree Com
- From: Anthony
- Re: VB6 Regfree Com
- From: Schmidt
- Re: VB6 Regfree Com
- Prev by Date: Re: Problems with WMI
- Next by Date: Re: Problem with DTPicker in Win98
- Previous by thread: Re: VB6 Regfree Com
- Next by thread: Re: VB6 Regfree Com
- Index(es):
Relevant Pages
|
Loading
