Member Avatar for mandar2886

I'm developing a medical software & I want to make an exe of this
project. Pls tell me how to proceed. I have no idea about this

  • 7 Contributors
  • 6 Replies
  • 317 Views
  • 3 Years Discussion Span
  • Latest Post Latest Post by IconKana

Dani AI

Generated

A concise deployment primer that fills gaps left in the thread (references to , , , and others): a quick compile is only the first step. The common problems seen later are missing/third‑party OCX or DLL dependencies, wrong compile mode, installer failures on modern Windows, and UAC/registration issues. The checklist and tips below summarize a practical, repeatable workflow and cover fallbacks when the IDE’s Make command is unavailable.

Pre-build checklist (catch compile-time faults and set project metadata). Perform a full compile to expose undeclared variables and broken references; add Option Explicit to modules where feasible. Confirm Project Properties (exe name, startup object, version info) and choose compile type (P-Code vs Native) depending on size vs performance needs — P-Code is smaller, Native is faster. For automation or when the IDE lacks the menu option, use the VB6 command-line build: for example

"C:\Program Files (x86)\Microsoft Visual Studio\VB98\vb6.exe" /make "C:\MyProject\MyProj.vbp" /outdir "C:\builds"

(the VB6 executable accepts /make and /outdir switches). (learn.microsoft.com)

Dependencies and installer notes (what most threads miss). The VB6 runtime and a small set of extended OCX/DLL files must be redistributed or relied upon in the OS; Microsoft documents which runtime files ship in Windows and which should be packaged with the app. Test for “MISSING” entries under Project→References and Project→Components and include or replace those files with supported redistributables. For creating an installer, modern free tools such as Inno Setup or NSIS are recommended; they support registering OCX/DLL entries during install (Inno’s regserver flag and NSIS’s RegDLL/RegDLL macros are common). On 64‑bit Windows pay attention to WOW64 registration and use 32‑bit registration paths when needed. (learn.microsoft.com)

UAC, manifests and signing. Embed or ship a manifest if elevation is required (requestedExecutionLevel) so UAC behaves predictably. Sign the installer/EXE with a code‑signing certificate (SignTool) to reduce SmartScreen warnings and improve trust. Test the final installer and EXE on clean VMs (non‑admin accounts and the target Windows versions). (learn.microsoft.com)

Quick troubleshooting reminders: run a full compile before building an installer; fix missing references first; register required COM/OCX files during install (don’t rely on users to run regsvr32 manually); keep a known‑good test VM matching the target OS. If the IDE edition truly lacks build support, compile on a machine with a full VB6 installation or use the command‑line /make approach mentioned above.

Recommended Answers

All 6 Replies

Member Avatar for debasisdas

To create jut an exe select makeEXE in File menu.

To create a complete setup use the Package and Deployment wizard .

commented: I agree +1
Member Avatar for Jupiter 2

You may only have Working Model Edition of VB6. It does not include the MakeExe option. You need a special tool to enable this option. You need to purchase a Full edition.

Member Avatar for abu taher

try as like debasis. he said easy way.

Member Avatar for Wins7

How TO make Setup Of V.B. Project?????????????????

Member Avatar for ChrisPadgham

please start your own thread if you have a question.

Member Avatar for IconKana

point to top left of project, hit file, make exe. Note, the exe file will be created in the same folder as the project.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.