Usercontrols - How much Overhead to the introduce?

Hi, I've separated some of my code in my project into two usercontrols which I use internally.

Does this add much overhead? How about compared to making it an ActiveX control in a separate DLL?

Also, I have put an existing ActiveX control into a UserControl, and put that on a form, is that particularily bad???

-Alex (adblack@uwaterloo.ca)

[Chris Eastwood]

Hi

I don't know about adding overhead by including them internally, but I find it certainly helps to encapsulate logic/code in one place.

As long as you've designed the application correctly, you should be able to reuse the UserControl anywhere in your application. If you need to include it in other applications then obviously you'll need to compile it as a separate ActiveX Control. The only overhead I can think of this way is the actual loading of the control at run time (negligable) - of course, you have to remember to assign a unique base address, otherwise the control will try to be loaded in memory at a point where another DLL is loaded (then keep on retrying till it's successful).

As for placing an ActiveX control into a UserControl - go ahead - it's what they were designed for (well, not really). Treat them the same as forms and you'll start to appreciate the power they give a programmer.


Regards

Chris Eastwood


CodeGuru - the website for developers
http://www.codeguru.com/vb