Article ID: 153020
Article Last Modified on 6/24/2004
APPLIES TO
- Microsoft Visual Basic 5.0 Professional Edition
- Microsoft Visual Basic 5.0 Enterprise Edition
- Microsoft Visual Basic 4.0 Professional Edition
- Microsoft Visual Basic 4.0 32-Bit Enterprise Edition
This article was previously published under Q153020
SYMPTOMS
When the Setup Wizard is used to generate a setup program for an OLE
DLL, the DLL will not be registered correctly when the setup program is
used. This problem does not occur if the Setup Wizard is used to generate a
program for an OLE automation client and the OLE server DLL is included in
Step 4 of the Setup Wizard.
WORKAROUND
The Setup Wizard generates a SETUP.LST file for each set of installation
media it generates. This file is used to determine which files to copy,
where to copy them, and how they can be registered, among other things. The
SETUP.LST file can be modified to cause the Setup Wizard-generated program
to correctly register the DLL upon installation.
After generating setup media with the Setup Wizard, open the SETUP.LST file
with a text editor such as Notepad. The line that refers to the DLL file
will look something like this (all on one line):
File2=1,,DS.dl_,DS.dll,$(CommonFiles)\OleSvr,,$(Shared),2/19/1996,10240,
1.0.0.0
To cause the DLL to be registered properly when installed, simply add the
text '$(DLLSelfRegister)' between the correct set of commas, so that the
line now looks like this:
File2=1,,DS.dl_,DS.dll,$(CommonFiles)\OleSvr,$(DLLSelfRegister),$(Shared
),2/19/1996,10240,1.0.0.0
The setup program will now know to register the DLL file after it has been
copied to the hard drive.
STATUS
Microsoft has confirmed this to be an issue in the Microsoft products
listed at the beginning of this article. Microsoft is researching this
problem and will post new information here in the Microsoft Knowledge Base
as it becomes available.
Keywords: kbbug kbsetup kbdsstools KB153020