Member Avatar for piyush gandhi

What are the following types of files that can be created in VB

for eg.:

1>> ActiveX EXE
2>> ActiveX DLL
3>> DLLs

etc, etc, etc..

and all of them that we can create in VB
e

I know only the Standard EXE applications that we create in VB

please explain in detail if possible...

please help me as soon as possible

Unique identifier for each user.

Edited by pritaeas because: fixed formatting
  • 4 Contributors
  • 3 Replies
  • 110 Views
  • 15 Hours Discussion Span
  • Latest Post Latest Post by QVeen72

Dani AI

Generated

Good follow-up to the thread: , and each touched useful points. Below is a concise, practical breakdown of what VB builds actually are, when to pick each, and common deployment/troubleshooting notes.

VB project outputs fall into a few hosting models. A Standard EXE is a normal standalone application. An ActiveX DLL is a COM class library that runs inside the caller’s process (in-process server) — good for performance and direct object sharing. An ActiveX EXE is a COM server that runs in its own process (out-of-process) — adds isolation and can survive host crashes but incurs COM marshaling overhead. An ActiveX Control (.ocx) is a visual control packaged as a COM component. VB’s “DLL” output produces COM-based components; VB does not create native C-style exported-function DLLs (use C/C++ for those).

Pick based on trade-offs: use ActiveX DLLs when you want fast in-process calls and shared state; use ActiveX EXEs when you need isolation, separate lifetime, or cross-process access. VB COM components are typically STA-oriented, so threading and marshaling behavior matter — that affects performance and design. Also consider class instancing settings and, importantly, binary compatibility so existing clients don’t break when you rebuild.

Deployment/troubleshooting essentials: register in-process servers and OCXs with regsvr32 MyComponent.dll; register an EXE server by running it with /regserver (for example MyServer.exe /regserver). “Class not registered” usually means the component isn’t registered or GUIDs changed; use VB’s binary-compatibility option to preserve GUIDs. If native exported APIs are required (non-COM consumers), build a native DLL in C/C++ or create a thin wrapper. For low-level background, see Microsoft’s documentation on dynamic-link libraries and the Component Object Model (COM).

Recommended Answers

All 3 Replies

Member Avatar for jbennet

DLLs are shared libaries. For example, i could write a card game DLL with a number of shared functions (shuffle, deal x cards etc...) and then use it for many programs (blackjack, poker etc..)

Member Avatar for debasisdas

simply in laymans language DDL files are supporting files for EXE files.

Member Avatar for QVeen72

Hi,

DLL->Dynamic Link Library.
Suppose u want to connect to a database or generate a Report, u need some Objects, These Objects allow u to connect to DB's or do whatever task, They are called as Dll's. They have certain Properties, Members,Objects ,Methods. They act as a Layer between VB Interface and the Back Layer.
Users need not worry how the Dll's work, but once a Dll is included in the project, they can take full use of all the Methods/properties Exposed.

Regards
Veena

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.