Article ID: 190046 - View products that this article applies to.
This article was previously published under Q190046
The information below includes the documentation and workarounds for Visual Basic 6.0. This information can also be found in the README.htm file that ships with Visual Basic 6.0 on the Visual Basic 6.0 CD-ROM. Please see the REFERENCES section of this article for a list of the Microsoft Knowledge Base articles relating to the Visual Basic 6.0 readme.
Following is a list of all parts of the readme file:
Part 1. Important Issues Please Read First!
Part 2. Data Access Issues and DataBinding Tips.
Part 3. Control Issues.
Part 4. Language Issues.
Part 5. Samples Issues.
Part 6. Wizard Issues.
Part 7. Error Message Issues.
Part 8. WebClass Designer Issues.
Part 9. DHTML Page Designer Issues.
Part 10. Extensibility Issues.
Part 11. Miscellaneous Issues.
Part 12. Microsoft Transaction Server (MTS) Issues.
Part 13. Dictionary Object.
Part 14. Visual Component Manager.
Part 15. Application Performance Manager.
Package and Deployment Wizard (PDW): Automatically Picks Up Files From Redist DirectoryA new feature of the Package and Deployment Wizard is its ability pick up files from the Redist folder. An example of how the feature is used would follow the steps below:
Package and Deployment Wizard Has [Do Not Redist] SectionA new section has been added to the Package and Deployment VB6Dep.ini file: [Do Not Redist]
Two kinds of files are listed under the new section:
Package and Deployment Wizard: In Silent Mode the Notification Window May Not Be First in the Window Z-orderWith Visual Basic, it is possible to run the Package and Deployment Wizard in silent mode from a command prompt. When doing so, you can also set a path for logging the wizard's output (/l ). With the path set, the wizard will create a log of events. If you do not use the argument, the wizard will instead display a dialog box to notify you of the wizard's completion. However, the window is not always obvious because it may be underneath other windows. In order to see it, you may need to close or minimize all other windows.
For more information, search online for "running as a stand-alone" in Visual Basic Concepts in the MSDN Library Visual Studio 6.0 documentation.
Package and Deployment Wizard: Command Line Mode Argument Added for Specifying Executable PathAn argument has been added to the command line mode of the Package and Deployment Wizard. The argument is shown in the table below:
The argument allows the command line mode to be used in a multi-developer environment where a computer is dedicated to compiling the project and creating the package.
Argument Description /e path Use the argument to set the path for the project's executable file if it is different from the project's path.
For more information, search online with Package and Deployment Wizard selected, for running as a stand-alone in the MSDN Library Visual Studio 6.0 documentation.
Package and Deployment Wizard: Manually Add User Control License FilesWhen creating a package for a user control that requires a license key, the license file (.vbl) is not automatically included. Instead, you must add the file manually.
When you are at the dialog titled "Package and Deployment Wizard Included Files," click the Add button and search for the appropriate .vbl file.
Package and Deployment Wizard: Steps in the Web Deployment ProcessWhen you post an Internet package to a Web server using the Package and Deployment Wizard, the wizard uses a technology known as WebPost to copy your package to the server and process it appropriately. These are the steps that the WebPost process goes through when processing your .cab:
Package and Deployment Wizard: Web Deployment Tips for HTTP or FTP Protocol
Package and Deployment Wizard: Start Menu Items: Run Option Not SupportedWhen creating a package for deployment, you can also create a Start menu item. Although it is mentioned in the Help topic for the dialog box, the Run option is not supported.
System Configurations for WebPost's Posting AcceptorWhen you deploy your packages to a Web server, the Package and Deployment Wizard uses a technology known as WebPost to move your files to the desired location. WebPost consists of two main components:
NOTE: Posting Acceptor does not work on any platforms that are using Personal Web Server or Peer Web Server. You must use IIS. Steps for installing Microsoft Posting Acceptor 2.0 if you have Visual Studio or Visual Basic Enterprise Editions.
Use this if you are running Comments -------------------------------------------------------------------------- Posting Acceptor 2.0 Windows NT 4.0 with SP3 Posting Acceptor 2.0 IIS 4.0 supports both content posting and the unpacking of cabinet (.cab) files on the server. Posting Acceptor 1.0 Windows NT 4.0 You cannot unpack .cab with SP3 with this version IIS 3.0 files of posting acceptor. Use this for content posting only. You can move your files to the server and then manually register any necessary files that would have been registered by the .cab process.
Package and Deployment Wizard: Edit Setup.lst File If You Rebuild Cabs From Batch FileAfter creating a standard setup package using the Package and Deployment Wizard, you can manually recreate the setup files (Setup.exe, Setup.lst, and all .cab files) by running the batch file found in the in the Support folder. Doing this allows you to manually customize the package or to recreate a package without running the wizard again. Running the batch file will copy setup.exe and setup.lst from the Support folder to the Package folder and will generate the cab file(s) in the Package folder. However, once the batch file is finished, setup.lst will not know how many .cab files were generated. Unless this problem is remedied, the setup program will fail.
To remedy this situation, do the following:
Package And Deployment Wizard: Error 80042114If you are creating a package for Internet deployment and you get the following error:
This error occurs because you have specified that your package should be posted to an FTP site using an HTTP URL. If you are certain that you have access privileges to the web server, you can click "Yes" and the deployment will proceed.
"Unexpected error 80042114 has occurred: The Web server you selected does not indicate support for the service provider you selected. Do you want to proceed anyway?"
To avoid this error in the future, when creating a package for deployment on the same server, specify the site and its protocol. When you do so, the following dialog box will appear:
"The specified URL and publishing method can be saved in the registry as a Web publishing site. This ensures that the URL and publishing method are valid and saves you time in future deployments to this site. Do you want to store this information as a Web publishing site?"
If you select "yes," this saves the site information and you will no longer receive the 80042114 error.
Package and Deployment Wizard: Use Mdac_typ.Cab and Mdac20.Cab to Distribute Data Access ComponentsWhen your Internet Package includes any of the following four files, the wizard will by default set these files to be downloaded from:
Similarly, the wizard will, by default, set the following files to be downloaded from:
In both cases, these defaults are indicated as the "Download from Microsoft Web site" option on the File Source screen. These cab files (mdac_typ.cab and mdac20.cab) perform special handling that should not be attempted manually. In order to ensure that the proper handling takes place, your Internet cab should not include these files but rather should reference the cabs. Therefore, you should never choose the "Include in this cab" option for any of these files. In addition, if you choose the "Download from alternate Web site" option, you should be careful to specify cabs that are copies of these cabs to ensure that the proper handling takes place.
Do not change the default settings for these files.
Package and Deployment Wizard: Manually Include .ASP and .HTM Files For IIS Applications When Using Standard SetupIf you use the Package and Deployment Wizard's standard setup to deploy an IIS application, you must manually include any .asp or .htm files with the package. Add the files using the Include Files dialog box.
Package and Deployment Wizard: Bad Date and Time FormatsIn certain situations, the Package and Deployment Wizard will incorrectly write time and date information to the Setup.lst file. When this occurs, the setup will fail because the dates will be written in a form that the setup.exe can't read. The problem occurs when you create a deployment package using the US version of Visual Basic on:
Package and Deployment Wizard: Unable to Run Setup.exe on First Windows 95 VersionAny setup package built with the wizard will not launch on certain installations of Windows 95 due to lack of support for an API in the original version of the Oleaut32.dll. This failure will not occur on OS release 2 of Windows 95 or any versions of Windows NT 4.0 and later, and will not occur if Microsoft Office 97 or Internet Explorer 3.0 or 4.0 has been installed. Any installation of a Visual Basic 5.0 application will also remedy the situation. You can also work around this failure by first overwriting the older version of Oleaut32.dll with the latest version. Be sure to shut down all applications before attempting to manually update Oleaut32.dll.
Package and Deployment Wizard: Packaging ActiveX DocumentsThe Visual Basic 6.0 Package and Deployment Wizard can insert CODEBASE= and VERSION= information directly embedded into the .vbd file for your ActiveX Document project. This eliminates the need for having the extra .htm file previously used to launch ActiveX Documents. The embedded information allows Internet Explorer to read the .cab file name for your ActiveX Document code and version information from the .vbd file and carry out the installation. You can now navigate directly to the .VBD file and your User document code will download if necessary.
The same functionality was available for Visual Basic 5.0 setup using the SetCodeBase utility found on the Visual Basic Owners Area.
The following are some issues with Visual Basic 6.0 Package and Deployment Wizard generated setups for User documents:
For additional information, please see the following articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/170164/EN-US/ )INFO: VB 6.0 Readme Part 1: Important Issues Read First!
(http://support.microsoft.com/kb/170163/EN-US/ )INFO: VB 6.0 Readme Part 2: Data Access/Databinding Issues
(http://support.microsoft.com/kb/170162/EN-US/ )INFO: VB 6.0 Readme Part 3: Control Issues
(http://support.microsoft.com/kb/170161/EN-US/ )INFO: VB 6.0 Readme Part 4: Language Issues
(http://support.microsoft.com/kb/170160/EN-US/ )INFO: VB 6.0 Readme Part 5: Samples Issues
(http://support.microsoft.com/kb/170158/EN-US/ )INFO: VB 6.0 Readme Part 7: Error Message Issues
(http://support.microsoft.com/kb/189539/EN-US/ )INFO: VB 6.0 Readme Part 8: WebClass Designer Issues
(http://support.microsoft.com/kb/190249/EN-US/ )INFO: VB 6.0 Readme Part 9: DHTML Page Designer Issues
(http://support.microsoft.com/kb/170154/EN-US/ )INFO: VB 6.0 Readme Part 10: Extensibility Issues
(http://support.microsoft.com/kb/170157/EN-US/ )INFO: VB 6.0 Readme Part 11: Miscellaneous Issues
(http://support.microsoft.com/kb/170156/EN-US/ )INFO: VB 6.0 Readme Part 12: Transaction Server (MTS) Issues
(http://support.microsoft.com/kb/191792/EN-US/ )INFO: VB 6.0 Readme Part 13: Dictionary Object
(http://support.microsoft.com/kb/191791/EN-US/ )INFO: VB 6.0 Readme Part 14: Visual Component Manager
(http://support.microsoft.com/kb/191790/EN-US/ )INFO: VB 6.0 Readme Part 15: Application Performance Explorer
Article ID: 190046 - Last Review: February 11, 2005 - Revision: 2.1