Vb stands for Visual Basic.
An ActiveX Exe is an out of process server which runs in it's own separate memory space. The component can run as a standalone desktop application, like Microsoft Excel or Microsoft Word, in addition to providing objects. It can process requests on an independent thread of execution, notifying the client of task completion using events or asynchronous call-backs. This frees the client to respond to the user. If an error occurs the client processes can continue to operate.
On Windows Run prompt, type regsvr32 "<complete path of control>" and press Enter.
Yes it is possible, most things are in VB
viva question for vb
well there is lot of thing you can use in the vb
form1.vb
acitex data object database control
EXECUTABLES - .exe PROJECTS - .vbproj FORMS - .vb SOLUTION - .sln
If you save your VB.NET project, it will be a .vb file. You can also build your program, then it becomes an executable (.exe)
COM Components (either AcitveX dll or ActiveX exe) provide a way to decouple and deploy applications in a way allows for reuse of these components. Additionally, COM allows you to deploy components on different machines for distributed use. For example, if you have an application server and a number of client machines you could write an ActiveX dll which you would install in a COM+ application on the application server which could then be accessed by all the client machines. This is often done to centralize business or data logic. Alternatively, if you didn't want to use COM+, you would write an ActiveX exe and use DCOM directly (which COM+ uses behind the scenes) for the client apps to be able to access the ActiveX exe. Now days, it is not as common as it used to be in enterprise apps to use ActiveX exe's for the purpose of distributing since most of the time the cross machine work is done using COM+. However, there are still many reasons to use ActiveX exe's: One is to automate a stand-alone application so it's features can be directly used by a client app. Another is to allow one process to spawn other processes to be able to do work that runs asynchronously. Since you cannot do multi-threaded work in VB6, this allows you to control a number of processes from a single controller app to achieve a similar result. ActiveX dlls are often used by a GUI form-based front end to provide the business layer in an n-tier application. For example, you could have a class that calculates tax. Once you have it working well, you want to use it for any application you write. By placing this class into its own ActiveX dll and registering it on a machine, any application that needs to use this code will be able to do so (as long as you write the code for it to do so). In my use, almost all logic that is not directly GUI based is in an ActiveX dll.
On Windows Run prompt, type regsvr32 "<complete path of control>" and press Enter.
I have to activate activex control!....
In-proc - Com object is present within application processOut-Proc - Com object has it's own process area In-proc - E.g. Activex DllOut-Proc - E.g. Activex exe In-proc - FasterOut-Proc - Comparitively slower In-proc - Useful for local comOut-Proc - Useful for remote com
s ActiveX a Mobile code
ActiveX controls can modify the properties of objects in an application.
Google Chrome doesn't naturally support ActiveX, but there is one way to force it: Internet Explorer does support ActiveX.
Digital code signing
Yes it is possible, most things are in VB