[dba-Tech] MS Excel COM Add-In in VB.NET...

> But what is the difference between two or three add-ins and one -
> except that if one only it must hold more code?
Gustav,

You can package them two or three of four or ... together - and sell them
for different price for your customers...
And it's easier (at least for me) to manage such code - the specific
features for each add-in are in its own .dll, common are in a common .dll
etc.

> it simply the size
> of an add-in that - when growing - causes the add-in to act more and
> more unreliably?
In MS Excel 2003 is takes 6 to 10 seconds to save the code on ~2GHz/1GB RAM
PC when I just click [Save] button.
And because the more code you put in it the less stable it becomes you have
to click [Save] often (of have AutoSave) - all that makes development a
crazy process especially when you forget to click [Save] and your add-in
GPFed...

In VB.NET it autosaves the code each time you run the Add-in and it takes
nothing to wait the compile.

And VB.NET's autocompile is just incredible - very quick, very useful: you
just see the list of errors in the task list, use F8 to switch between them
and code window follows these switching and as soon as you correct the
problem it's task list entry is removed...

Shamil

----- Original Message ----- 
From: "Gustav Brock" <gustav at cactus.dk>
To: "Discussion of Hardware and Software issues"
<dba-tech at databaseadvisors.com>
Sent: Monday, November 01, 2004 10:25 AM
Subject: Re: [dba-Tech] MS Excel COM Add-In in VB.NET...


> Hi Shamil
>
> Interesting indeed!
>
> But what is the difference between two or three add-ins and one -
> except that if one only it must hold more code? Is it simply the size
> of an add-in that - when growing - causes the add-in to act more and
> more unreliably?
>
> /gustav
>
>
> > Date: 2004-11-01 02:43
>
> > Hi All.
>
> > I've just finished converting three Excel Add-ins (.xla) from VBA to
> > VB.NET -> COM Add-ins.
>
> > What I can say?
> > VS.NET 2003 is a great tool!
>
> > Last summer I tried to combine two MS Excel add-ins into one, spent
quite
> > some time but in the end I found that the result can't be predicted -
the
> > more code I put into combined VBA Add-in for MS Excel the less were the
> > chances that this code be stable at all. I stopped that efforts last
summer
> > because combined MS Excel started to gpf, it wasn't even possible to
open
> > VBA project....
>
> > And with VB.NET it all works!
> > The add-in uses DAO, ADO, several legacy COM components, MS XML Core
> > Services etc. - no problem so far...
>
> > To convert all that stuff totalling about 20,000 code lines took two+
> > working days...
>
> > I've packed all that into four .DLLs, they all communicate one with
another,
> > there is no duplicated code....
>
> > MS forever!
>
> > Shamil
>
> _______________________________________________
> dba-Tech mailing list
> dba-Tech at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-tech
> Website: http://www.databaseadvisors.com