I'm just curious. I load everything via code at runtime. The only thing I
use the Designer for is only for controls that *have* to be placed on a form
(or usercontrol) ahead of time. But even then I don't configure them in
designmode. I spend 99% of my time editing code, etc.
Am I taking a performance hit with the above practice? From my view, having
everything load via code makes it easier to know whats going on when I'm
editing the code.
Any responses would be appreciated.
Lacy
joeycalisay - 18 Mar 2005 03:04 GMT
All I can say is:
DesignTime features = Less Coding
Things like setting a property for a number of controls in one go, layout
management features of VS (alignment, size adjustments, etc.), and
design-time features of your controls (designerverbs, etc.) are definitely a
plus in programming...
Seeing the appearance of controls sometimes give you already an idea on what
property is improperly set, rather than scanning your property sets in code.

Signature
Joey Calisay
http://spaces.msn.com/members/joeycalisay/
> I'm just curious. I load everything via code at runtime. The only thing I
> use the Designer for is only for controls that *have* to be placed on a form
[quoted text clipped - 8 lines]
>
> Lacy
Eric Cadwell - 18 Mar 2005 18:02 GMT
It's a trade off, you'll never end up losing your layout when a control
disappears.
I'd lay it out in the designer, then move your code to a method you write.
There's no performance hit.
I often end up editing the InitializeComponent block direclty. I have also
moved some code into external functions called in the constructor (mostly
for custom controls that use non-default constructors).
HTH;
Eric Cadwell
http://www.origincontrols.com
Bram - 22 Mar 2005 12:28 GMT
Usually, when you lose your layout when working in design mode, closing
the design window (_without_ saving or rebuilding first) and rebuilding
after that solves the problem. This bug is my only (major) annoyance
with the Form Designer.