aft
asked on
ocx and dlls
if i create a dll or ocx control using visual basic or visual c
is there is any different in the speed of execution when using this control or dll in another application in case of build it using visual c or visual basic?
is there is any different in the speed of execution when using this control or dll in another application in case of build it using visual c or visual basic?
Yeah...angelIII is right..if properly implemented..Visual C is always faster than Visual Basic.
Yeah...angelIII is right..if properly implemented..Visual C is always faster than Visual Basic.
Yeah...angelIII is right..if properly implemented..Visual C is always faster than Visual Basic.
Yeah...angelIII is right..if properly implemented..Visual C is always faster than Visual Basic.
Saying that Visual Basic is faster is not always true. An application written in Visual C++ MFC is not faster than a VB WIN32 written application. This is because the MFC framework is a lot bigger and slower than the plain Win32 API.
Comparing a VB WIN32 written application with a Visual C++ WIN32 written application you feel find no difference in performance. They make use of the same dll's and the same compiler (at least VB6 and VC6 that I am sure about). The same goes for DLL's.
If you create an ocx or dll with the functions, and other stuff available, with the DllRegisterServer and the IClassFactory in either one of those products you will find no difference in execution.
Even DLL's and OCX's written in VB, though only a little bit slower depending on how you write the code (late binding mostly), and which functions you use are only a little bit slower in execution.
regards,
CJ
Comparing a VB WIN32 written application with a Visual C++ WIN32 written application you feel find no difference in performance. They make use of the same dll's and the same compiler (at least VB6 and VC6 that I am sure about). The same goes for DLL's.
If you create an ocx or dll with the functions, and other stuff available, with the DllRegisterServer and the IClassFactory in either one of those products you will find no difference in execution.
Even DLL's and OCX's written in VB, though only a little bit slower depending on how you write the code (late binding mostly), and which functions you use are only a little bit slower in execution.
regards,
CJ
Basically what I am saying is that the way you decide to write your code will make the application run faster or not. Win32 API will give you the best performance, and never using late binding.
Regards,
CJ
Regards,
CJ
ASKER
why visual basic controls is more slower?
ASKER
it have to be with the same speed because both converted to machine code
ASKER
it have to be with the same speed because both converted to machine code
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The controls are all the same. The ones you use in MFC and VB are both coming from the same ocx-files. It's just the functions you use that matters, and how they are being handled with. A
Machinecode will be different for each compiler, prashant_n_mhatre is correct with what he said.
Regards,
CJ
Machinecode will be different for each compiler, prashant_n_mhatre is correct with what he said.
Regards,
CJ
Cheers