Splitting an Add-in package over several Add-ins

  • Thread starter Thread starter R Avery
  • Start date Start date
R

R Avery

I am concerned that an add-in of my design is ballooning to become
unwieldy. Does anyone have any tips, advice, warnings about splitting
it up over several add-ins, only a few of which are loaded at a time to
respond to user actions?

Or would it be better to leave in a single add-in? What is the size at
which an add-in becomes too large?

I know these are all vague questions, but even fuzzy answers would be
better than none. Thanks!
 
R Avery said:
I am concerned that an add-in of my design is ballooning to become
unwieldy. Does anyone have any tips, advice, warnings about splitting
it up over several add-ins, only a few of which are loaded at a time to
respond to user actions?

Or would it be better to leave in a single add-in? What is the size at
which an add-in becomes too large?

I know these are all vague questions, but even fuzzy answers would be
better than none. Thanks!
Click to expand...

As a general rule consider splitting out functions that are generic
enough to use in other applications.

At the very least put your code in multiple code modules and
document it internally with lots of comments. There's little
more frustrating tha having to debug an app with no
information about what its supposed to be doing and
you'd be surprised how little time it takes to lose track
of what code is supposed to be doing even when you
wrote it yourself

You may want to consider moving to compiled dll's or COM
add-ins which offer rather more security for your code than a
conventional add-in and which as registered components
are somewhat easier to keep up to date if your application
is distributed.

Keith.
 
Back
Top