beginner123
Programmer
what are the advantages and disadvantages of developing com component using c++ over using vb
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
developing com component using c++ or vb, what are advantages and dis 1
- Thread starter beginner123
- Start date
- Status
-
1
- #2
* If you know C++ but not VB or VB but not C++, that would be the most obvious advantage.
* If you know both, which language do you have the most COM experience in?
Beyond that it is possible that VB has some limitations like you can't do a free threading model. Hopefully a VB person could confirm or deny those types of issues, anyone?
-pete
* If you know both, which language do you have the most COM experience in?
Beyond that it is possible that VB has some limitations like you can't do a free threading model. Hopefully a VB person could confirm or deny those types of issues, anyone?
-pete
Guest_imported
New member
- Jan 1, 1970
- 0
- 0
- 0
You're right, the next version of VB, VB.NET, can write free-threaded code.
You can't help but make a COM component when you create a dll in VB. The IDE doesn't give you any other choice. That may be a drawback, since you lose control. Another advantage is that the IDL is created automatically. With few exceptions, VB does a pretty good job of creating the COM Type Library for you when the component is compiled.
All VB components are self-registering. The developer does not need to worry about this code, either.
Hope that helps.
You can't help but make a COM component when you create a dll in VB. The IDE doesn't give you any other choice. That may be a drawback, since you lose control. Another advantage is that the IDL is created automatically. With few exceptions, VB does a pretty good job of creating the COM Type Library for you when the component is compiled.
All VB components are self-registering. The developer does not need to worry about this code, either.
Hope that helps.
-IkeEllis
>All VB components are self-registering. The developer does not need to worry about this code, either.
If you use ATL in VC++ the components are also self-registering. Plus you have the advantage of change that code if need be.
-beginner123
I think that what palbano said makes all the sense. Don't make COM components with C++ if you don't have the knowledge.
It's more hard maintain C++ code that VB code, but it's more efficient. VB code is more transparent and easy to use, but you have to consider how depth you wan't to go - VB doesn't make it all...
Like Ike said VB.NET bring new features and, for all that I read, things will be must better while making VB code...
regards,
Bruno Loureiro
<brunoloureiro@usa.net>
>All VB components are self-registering. The developer does not need to worry about this code, either.
If you use ATL in VC++ the components are also self-registering. Plus you have the advantage of change that code if need be.
-beginner123
I think that what palbano said makes all the sense. Don't make COM components with C++ if you don't have the knowledge.
It's more hard maintain C++ code that VB code, but it's more efficient. VB code is more transparent and easy to use, but you have to consider how depth you wan't to go - VB doesn't make it all...
Like Ike said VB.NET bring new features and, for all that I read, things will be must better while making VB code...
regards,
Bruno Loureiro
<brunoloureiro@usa.net>
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question