burningodzilla

could someone tell me ALL of the files required by VB apps? when making an installer with P&DW and then installing it, it unpacks like 7 DLLs....but to my knowledge the only required ones are MSVBVM60.DLL and OLEAUT32.DLL.

anhmytran

When it says 7 DLLs, there should be 7 DLLs.
It knows that when it compiles your code.

AnhMy_Tran

Banjo

Which files are installed will depend on your application's dependancies. Can you list these 7 files you mentioned?

anhmytran

No. I do not know which files.
I just quote your words.
It means that whatever files the VB Wizard picks are the required files.

It has nothing to do with the dependancies.
It is all required or necessary for the operation of the EXE file.

AnhMy_Tran<P ID="edit"><FONT class="small"><EM>Edited by anhmytran on 09/12/01 11:52 AM.</EM></FONT></P>

Banjo

Not all of them are needed by the app. Some are required by the PDW setup package.

I can't remember the exact filenames but one of them is something like 'vbskit.dll'.

burningodzilla

i didn't ask you to name the seven files. i am fairly confident that all 7 are NOT indeed needed for the app to run.

BillSoo

Look in Tutors corner for a list of required DLLs/Files.

"I have a plan so cunning you could put a tail on it and call it a weasel!" - Edmund Blackadder

burningodzilla

plenty of links, no list

BillSoo

You have to set the date selector to "all dates" instead of "last week".

<a href="http://www.xtremevbtalk.com/bbs/showflat.php?Cat=&Board=tu&Number=25279&page=0&view=collapsed&sb=5&o=a ll&part="> Here is the link</a>



"I have a plan so cunning you could put a tail on it and call it a weasel!" - Edmund Blackadder

burningodzilla

[img]images/icons/frown.gif[/img] sorry...i did set to all dates an did a search in tutor's corner for "required DLLs", no dice. thanks for the spoon feed though!

ChiefRedBull

The DLLs that are required vary depending on which controls you use in your app.
To the best of my knowledge, the only required DLL's are MSVBVM60.DLL. This covers everything that is included when you originally open a new standard EXE project. But yes, the P&DW probly needs a couple too....

Chief

"Dammit Smithers, this is brain surgery not rocket science!! Now hand me that ice cream scoop..."

BillSoo

I got my list directly from the VB help file, under the topic "Files You Need to Distribute". I'll post the text of the topic below:


Visual Basic Concepts

Files You Need to Distribute


The first step in creating a custom setup program is to determine which files to distribute. All Visual Basic applications need a minimum set of files, referred to as bootstrap files, that are needed before your application can be installed. In addition, all Visual Basic applications require application-specific files, such as an executable file (.exe), data files, ActiveX controls, or .dll files.

There are three main categories of files needed to run and distribute your application:

Run-time files


Setup files


Application-specific files
Run-Time Files
Run-time files are files your application must have in order to work correctly after installation. These files are needed by all Visual Basic applications. The following are the run-time files for Visual Basic projects:

Msvbvm60.dll


Stdole2.tlb


Oleaut32.dll


Olepro32.dll


Comcat.dll


Asycfilt.dll


Ctl3d32.dll
While these files are needed by all Visual Basic applications, they may not be necessary for every type of installation package. For example, when creating an Internet package, the Package and Deployment Wizard assumes that any computer capable of performing an Internet download already has all of these files except for Msvbvm60.dll. Therefore this is the only run-time file that the wizard includes in an Internet package.

Note Run-time files can be further classified by their installation location. See "Where to Install Files on the User's Machine" for more information.

Setup Files for Standard Packages
Setup files are all of the files required to set up your standard application on the user's machine. These include the setup executables (setup.exe and setup1.exe), the setup file list (Setup.lst), and the uninstall program (st6unst.exe).

Visual Basic applications that are designed to be distributed on disk, on CD, or from a network location use the same setup files, regardless of whether you use the Package and Deployment Wizard or the Setup Toolkit to create your setup programs. These files are listed below.

File name Description
setup.exe Program that the user runs to pre-install the files that are needed for your application to be installed on the user's machine. For example, the setup.exe file installs the setup1.exe file, the Visual Basic run-time DLL, and other files without which the rest of the setup process cannot run.
setup1.exe The setup program for your Visual Basic application. This executable file is generated by the Setup Toolkit and included in the package by the Package and Deployment Wizard. You can rename this file as long as the new name is reflected in the Setup.lst file.
Setup.lst Text file that contains installation instructions and lists all the files to be installed on the user's machine.
Vb6stkit.dll Library containing various functions used in Setup1.exe.
St6unst.exe Application removal utility.


Note Applications designed to be delivered over the Internet generally do not use any of these files. See "Internet Packages" earlier in this chapter for more information on the files involved in Internet delivery.

Application Dependencies
In order to run your application, end users will need certain files in addition to the common run-time files and special setup files. Many of these files will be obvious to you: the executable file, any data files, and any ActiveX controls that you used. The less obvious files are your project's other dependent files. For example, some of the ActiveX controls used by your project may in turn require other files. One of the tasks of the Package and Deployment Wizard is to determine the complete list of such required files.

For More Information See "Dependency Files" earlier in this chapter for information on using the Package and Deployment Wizard to create dependency files for your application.


--------------------------------------------------------------------------------
Send feedback to MSDN.Look here for MSDN Online resources.


"I have a plan so cunning you could put a tail on it and call it a weasel!" - Edmund Blackadder