DOCUMENT:Q191001  07-AUG-1998  [vbwin]
TITLE   :BUG: PDW May Handle .REG Files Incorrectly
PRODUCT :Microsoft Visual Basic for Windows
PROD/VER:
OPER/SYS:WINDOWS
KEYWORDS:

======================================================================
---------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Visual Basic Professional and Enterprise Editions for
   Windows, version 6.0
---------------------------------------------------------------------

SYMPTOMS
========

When installing an application using a setup program generated by the
Package and Deployment Wizard (PDW), unwanted information may be added to
the registry if a .Reg file is included in the distribution set.

CAUSE
=====

When creating a distribution set with the Package and Deployment Wizard,
there is an option to add files in addition to those files already in the
Visual Basic project.

If a .REG file is added, a dialog is shown asking if the .REG file should
be copied to the destination computer and if it should be used to update
the registry. The dialog indicates that neither, one, or both of the
options can be used.

If "No" is selected for both of these options, the PDW will default to "No"
for Copy and "Yes" for "Update Registry." Then, when the setup program is
run, the registry will be updated with the information in the .REG file.

RESOLUTION
==========

If a .REG file is not to be copied to the target machine nor used to update
the registry, do not include it in the distribution set or give the file an
extension other than .REG.

STATUS
======

Microsoft has confirmed this to be a bug in the Microsoft products
listed at the beginning of this article. We are researching this
bug and will post new information here in the Microsoft Knowledge
Base as it becomes available.

REFERENCES
==========

Online Help for Microsoft Visual Basic

Additional query words: kbVBp600bug kbAppSetup kbdss kbDSupport kbVBp
kbRegistry
======================================================================
Platform          : WINDOWS
Issue type        : kbbug

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1998.