I have a program I am using to send email using the vbSendMail.dll. The
program works great on the development machine and on test machines
after the dll is manually registered using regsvr32.

I used the P&D Wizard to create a setup package, and I'm wondering if
the DLL will be automatically registered on ever OS from 98 up when the
installation is done using the setup files? Or is it good practice to
register it from VB before the program needs to use the dll, e.g. from
Sub Main() at program startup?

The file is listed in the setup.lst here:

[Setup1 Files]
Fil***@vbSendMail.dll,$(WinSysPath),$(DLLSelfRegister),$(Shared),3/22/06
6:45:18 PM,139264,3.6.0.5

TIA,
Mike

There shouldn't be any problems with this dll, unless it is already in use at
the time of the setup.
On NT5 systems (W2000, XP) you should consider using another installer, such
as the free MS Visual Installer for VS6, for simple installations.
If some of the files to be installed are system files, then you will have
eventually problems with P&D. The NT5 OS System files should be updated only
by the system Servive Packs, as most are protected, and the P&D cannot
replace them. During setup, other files which may be in use by other resident
programs will also be a problem, and the P&D may request a reboot to replace
these, but after the reboot it has the same problem, because it cannot
replace them (you could just remove all those system files from the setup,
except for pre-NT5 systems, and as for the other files in use, leave them
out, and then hope for the best.) Most standard stuff (MDAC, VB basic
components, etc. are already on those NT5 systems)

The Visual Installer is a VS (Visual Studio) IDE for the Windows Installer.
It is somewhat limited as to what it can do for you, and the Visual Installer
from VS .NET, which can be used to also install what you are trying to
install with P&D, is better than that from VS6, but if you want to do more
than what the default Forms and basic custom actions provided in Visual
Installer, you'll need to learn how to edit the MSI setup file, or just get a
third party installer which is more capable.

Show quoteHide quote

Best to add it to the System32 folder though.

   The trick is to just make sure that file versions
shipped are earlier than Win2000 versions.
Especially if you're working on a later Windows
system, the support file versions should match
the service pack versions and to be on the safe
side a copy should go into the
Wizards\PDWizard\Redist folder where PDW
will find it.

Convert HTML to text
Error when running vb app with FlexGrid control
Help with disconnected recordset!
question -- close adodb connection inside dll
Vendor ActiveX control
Adding treeview programacticlly
Comparing UDTs
ADODB Recordsets into Array
WebBrowser vs Pdf.ocx
Error creating Oracle object