Estimado Rafael Antonio, algunos comentarios (y son tan solo eso :-):
- verifica que sea legal encapsular .dll u otras dependencias de otros
autores (la msvbvm60.dll por ejemplo)
- aun no probe las app que mencionaste mas, que tamaño tendra al final?
--ASycFilt.dll 2.30.4261.1 144KB (147,728 bytes)
--ComCat.dll 4.71.1460.1 21.7KB (22,288 bytes)
--MSVBVM60.dll 6.0.81.76 1.34MB (1,409,024 bytes)
--OLEAut32.dll 2.30.4261.1 584KB (598,288 bytes)
--OLEPro32.dll 5.0.4261.1 160KB (164,112 bytes)
--STDOLE2.tlb 2.30.4261.1 17.5KB (17,920 bytes)
Estos archivos son dependencias base para cualquier componente o app
creada en VB6.
-- otras dependencias >> ??
- integra el help en el exe?
- tan complicado es realizar un instalador? Pues con este metodo los users
deben crear el grupo en el menu y para desinstalarlo buscar el .exe.
Igual es una opcion como cualquier otra y seguramente adecuada dependiendo
el escenario, ademas siempre es bueno conocer algo mas ;-)
Por ultimo, si la app es simple podrias utilizar la opcion que te propone la
gente de MS:
============>Comienzo Texto pegado=======================
Q192461
----------------------------------------------------------------------------
----
The information in this article applies to:
Microsoft Visual Basic Learning Edition for Windows, version 6.0
Microsoft Visual Basic Professional Edition for Windows, version 6.0
Microsoft Visual Basic Enterprise Edition for Windows, version 6.0
----------------------------------------------------------------------------
----
SUMMARY
VBRun60.exe is a self-extracting executable file that installs the Microsoft
Visual Basic run-time files that all applications created with Visual Basic
6.0 need in order to run.
NOTE: The following Microsoft Knowledge Base article contains the latest
versions of the Microsoft Visual Basic run-time files included with Visual
Studio 6.0 Service Pack 5. For additional information about the Service Pack
5 version of the Visual Basic 6.0 run-time files, click the article number
below to view the article in the Microsoft Knowledge Base:
Q290887 FILE: VBRun60sp5.exe Installs Visual Basic 6.0 SP5 Run-Time Files
MORE INFORMATION
The following file is available for download from the Microsoft Download
Center:
VBRun60.exe
Release Date: September 18, 2000
For additional information about how to download Microsoft Support files,
click the article number below to view the article in the Microsoft
Knowledge Base:
Q119591 How to Obtain Microsoft Support Files from Online Services
Microsoft used the most current virus detection software available on the
date of posting to scan this file for viruses. Once posted, the file is
housed on secure servers that prevent any unauthorized changes to the file.
VBRun60.exe installs the following core files, which ship with Visual Basic
6.0:
File Version Size
ASycFilt.dll 2.30.4261.1 144KB (147,728 bytes)
ComCat.dll 4.71.1460.1 21.7KB (22,288 bytes)
MSVBVM60.dll 6.0.81.76 1.34MB (1,409,024 bytes)
OLEAut32.dll 2.30.4261.1 584KB (598,288 bytes)
OLEPro32.dll 5.0.4261.1 160KB (164,112 bytes)
STDOLE2.tlb 2.30.4261.1 17.5KB (17,920 bytes)
These files are the base dependencies for any component or application
created in Visual Basic 6.0. In addition, the following files are also
installed by VBRun60.exe:
File Version Size
ADVPack.dll 4.71.1015.0 73.2KB (74,960 bytes)
W95Inf16.dll 4.71.704.0 2.21KB (2,272 bytes)
W95Inf32.dll 4.71.0016.0 4.50KB (4,608 bytes)
VBRun60.inf N/A 1.04KB (1,069 bytes)
These files are supporting files for the VBRun60.exe self-extracting file.
For information about the command-line arguments available for the
VBRun60.exe file, enter the following at the command-line:
"VBRun60.exe /?"
NOTE: You may need to specify the complete path to the VBrun60.exe file in
the command.
For additional information about documentation on command-line arguments,
click the article number below to view the article in the Microsoft
Knowledge Base:
Q189520 XCLN: Outlook Deployment Kit (ODK) Setup Command-Line Options
Do I Need VBRun60.exe File?
The VBRun60.exe file is not intended to replace the Package and Deployment
Wizard (PDW) for distributing Visual Basic applications. For example, if
your application includes components, such as ActiveX controls or DLLs, you
should use the PDW or a third-party setup package for distribution. However,
if your Visual Basic application only depends upon the files included in the
VBRun60.exe file, you can distribute your application by providing end users
with the executable (.exe) file and VBRun60.exe.
To determine whether your application requires additional files for
distribution, you can use the PDW to create a set of setup files as a test.
When the PDW creates a setup package, it creates a Setup.lst file. You can
open the Setup.lst file in any text editor (for example, Notepad). If the
[Setup1 Files] section of the resulting Setup.lst file only lists your .exe
file, end users should be able to run your application after running
VBRun60.exe to install the core run-time files. However, if the [Setup1
Files] section contains multiple files, you should consider using the PDW or
a third-party setup package for distribution instead.
In addition to distributing simple executables, you can also use the
VBRun60.exe file for the following:
To minimize the size of Internet downloads of Visual Basic applications
By running the Vbrun60.exe file ahead of time, users can download your
application from the Web faster.
As a troubleshooting step when an installation of Visual Basic or a Visual
Basic application fails
If Setup fails with an error message that mentions one of the core files or
if registration of a component fails during Setup, the core files on the
target computer might be mismatched. If the versions of the files in the
VBRun60.exe file are newer than the versions on the target computer, you
might resolve the problem by running the VBRun60.exe file before you run
Setup.
For additional information about a specific example of a Setup problem that
is resolved by running VBRun60.exe, click the article number below to view
the article in the Microsoft Knowledge Base:
Q194754 SETUP.EXE File Linked to Missing Export OLEAUT32.DLL:185
You can also obtain the VBRun60.exe file by extracting it from the
VBRun60.cab file available on the Visual Basic and Visual Studio CDs. The
VBRun60.cab file is located in the following folder on the Visual Basic 6.0
CD (Disk 1):
\common\tools\vb\cabinets
On the Visual Studio 6.0 Professional CDs, the VBRun60.cab file is located
in the same relative path on Disk 2. On the Visual Studio 6.0 Enterprise
CDs, it is located on Disk 3.
NOTE: The version of the VBRun60.exe file that is included in this Knowledge
Base article contains the same run-time file as the one on the installation
CD-ROM.
For additional information about how to get the files for Visual Basic 6.0
SP5, click the article number below to view the article in the Microsoft
Knowledge Base:
Q290887 FILE: VBRun60sp5.exe Installs Visual Basic 6.0 SP5 Run-Time Files
You can use the Extract utility to extract the VBRun60.exe file from the
cabinet file, VBRun60.cab. The Extract.exe file is located in your Windows
folder or on your Windows 95, Windows 98, or Windows NT installation CD.
From an MS-DOS command prompt, you can run the following command to extract
the file in the cabinet file into the current directory:
Extract Vbrun60.cab
For additional information about using the Extract utility, click the
article number below to view the article in the Microsoft Knowledge Base:
Q129605 How to Extract Original Compressed Windows Files
REFERENCES
For additional information, click the article numbers below to view the
articles in the Microsoft Knowledge Base:
Q194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why
Q180071 FILE: Msvbvm50.exe Installs Visual Basic 5.0 Run-Time Files
For additional information about documentation on command-line arguments,
click the article number below to view the article in the Microsoft
Knowledge Base:
Q189520 XCLN: Outlook Deployment Kit (ODK) Setup Command-Line Options
For additional information about a specific example of a Setup problem that
is resolved by running VBRun60.exe, click the article number below to view
the article in the Microsoft Knowledge Base:
Q194754 SETUP.EXE File Linked to Missing Export OLEAUT32.DLL:185
For additional information about using the Extract utility, click the
article number below to view the article in the Microsoft Knowledge Base:
Q129605 How to Extract Original Compressed Windows Files
For additional information about how to get the files for Visual Basic 6.0
SP5, click the article number below to view the article in the Microsoft
Knowledge Base:
Q290887 FILE: VBRun60sp5.exe Installs Visual Basic 6.0 SP5 Run-Time Files
Additional query words: runtime run-time run time vbrun600 ASycFilt ComCat
MSVBVM60 OLEAut32 OLEPro32 STDOLE2 ADVPack W95Inf16 W95Inf32 VBRun60 vb6
Keywords : kbfile kbtophit kbAppSetup kbDeployment kbVBp600 kbGrpDSVB
Issue type : kbinfo
Technology : kbVBSearch kbAudDeveloper kbZNotKeyword6 kbZNotKeyword2
kbVB600Search kbVBA600 kbVB600
============<Fin Texto pegado============================
--
Cordiales Saludos,
Diego N. Contin mailto:***@ESTOArgentina.com
--
Uso del Foro
http://www.mvp-access.com/rubenvigon/foro/
NOTA: este mensaje se proporciona TAL CUAL.
Sin ningun derecho o garantia
Post by Rafael AntonioHola a todos, antes que nada gracias por sus respuestas, navegando y
navegando por ahi encontre este par de programitas VB-powerwrap y Alloy, a
estos hay que agregar el exe y se encargan de buscar todas las referencias y
dependencias del exe de tal forma que lo empaquetan en un solo exe ya
comprimido y solo se le hace doble click y ya!!! tu aplicacion comienza a
correr y sobre todo sin haber instalado NADA!!!.