0
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.
What else can I help you with?
What is the difference between in-proc and out-of-proc?
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
How do you open 16-bit .dll files?
You can't. DLL file ( Dynamic Link Library ) can only be opened by an executable ( EXE ) or compiler.
Why dll files are faster than exe files?
Because dll's aka dynamic link library, can excute many files at once.
What is the difference between an EXE and a DLL?
Dll make it more simple for u, exe's are executables, or applications while dll are resource files that executables usually depend onAnswerA DLL so called Dynamic Link Library is a Library Class (In .NET its a Final result of a User Control or a Class designed) is a file that includes the Source code or the Callable functions that provide(s) service to the Application currently being executed. An EXE is a Stand-alone Application that could be executed on any platformAn EXE is an Independent Application while DLL is a Dependent on the Application's Call and Utilise of the DLL so In Question.An EXE has a dynamic access to any resource(s) of the Computer for ex. Printer, DMA, while DLL is / may alloted a fixed resource(s) to utiilse.EXE makes use of DLLs to execute the Application, while DLLs are called by the EXEs.As the name suggest, DLL is dynamically Loaded and Executed as and when necessary been called by the application, while EXE once called is loaded in the Memory while being Executed.DLLs has to be registered Using regsrv32 utility, while EXE is not suppose to be registered.DLLs are more efficient than EXE when the question is related to the Memory Utilization.Majorly DLLs comprises of the Functions or Procedures designed by any Programming Language which is mainly considered as "PROCESSING PART", whereas EXE comprises of Graphical User Interface (GUI), the Events to perform Actions, utilizing the DLLs (Calling and Retrieving results through DLLs).EXE may directly make use of OS while DLLs may or may not directly make use of OS.
Why does VS2010 lose linked dll-libraries while compiling?
Do you mean that your compiled .exe complains about a missing .dll when run on another computer? Try linking to the C++ runtime instead of the library dll.
I have the code for the COM exe with me.How do you convert the COM exe file to dll file?
The first thing to do is to change the entry point from main() to Dllmain() and alter the code to suit a DLL. You then have to tell your compiler that you are compiling a DLL, not an EXE. How you do that depends on the compiler. For instance, in Visual Studio, you would need to change the project's properties under General | Configuration Type. Note that EXE files do not necessarily make good DLLs. You may have to alter the implementation somewhat since you are no longer running a program as such, you are essentially loading and unloading a function and/or class library that can be utilised by external programs to which the DLL is linked.
How do you convert dll file into exe file?
When Your Windows Explorer Screen Is Up Go on top Tools>Folder Options>View> Then Uncheck "Hide Extinsions For Known File Types. Then Your File Will Be Named "Example.dll" all you have to do is highlight ".dll" and change it to ".exe"
Is there a .bat to .exe converter that also makes a dll with the .exe too?
No. A bat file is sort of a script. It cannot be compiled nor changed into binary executable.
What is the difference between a DIR file and EXE file in director?
trdfx5tdifyibh cv5yhtn097g
What does file extension dll mean?
"Data link Layer"It can stand for that, but it can also stand for Dynamic Link Library... it simply means a bunch a files that come together to be used by a running program or application.
Where do you unpack a dll?
Most likely, you don't need actually unpack dll files. Unlike exe files, dll files are not packed due to their nature: one copy of a dll can be accessed by a number of application. OTOH, a particular dll can be protected from viewing and reverse engineering. or if you want unpack dll really, most often all you need to do is copy and paste into proper folder
Which applications would be the prime target for attacks?
Any web application, buggy EXE files, and DLL libraries.
