B
Brian
Hello,
I have developed an Office XP COM Add In for a client in VB6. The Add In is
rather simple. It adds a toolbar with a single button to the command bars.
When a user clicks on the button, a dialog/form is displayed asking them to
choose an option. The value selected is then placed in a Custom Document
Property. I also do a little manipulation of the footer based on what was
selected in the form.
The add in is available allows for basically the same functionality for 3 of
the Office products (Word, Excel, PowerPoint). The only thing that is
really different for each is the manipuation of the footers.
It is a single .dll, but contains 4 classes - 1 for each supported Office
product (i.e. Word, Excel, and PowerPoint), the 4th class is the entry point
to the addin regardless of application. So each applications add in
registry keys point to the Connect class, the connect class then
instantiates the appropriate version of the add in class based on which
application it is being called from.
I am noticing, however, some stability problems with the add in. Certain
users are experiencing errors at "random" times from the addin (I know it is
my add in because I catch all exceptions and display a friendlier message to
the user). The only thing that might be common among these users is that
they may be using Word as their email editor for Outlook.
Also, it should be noted that there are a few other addins installed and
loaded on any given user's machine. I believe they have 2 addins
functioning in Outlook (one written in .NET 1.1, the other in VB6). I
believe there is also another addin that is loaded for Word, in addition to
my addin, not sure which language this was written in, but my guess is .NET
1.1.
I am pretty confident that the issue is not a result of buggy code, as I,
and many other users run these addins with no problems and I have
implemented the code into the events I need to hook into.
1. Does anyone have any suggestions or ideas that might help resolve this
issue? For example, is it OK the way I have implemented it with a single
..dll and 4 classes, or should each office application have had it's own .dll
for the addin?
2. Are there known issues with stability and addins running on Office XP
(running in .NET or VB6)?
3. If I moved my addin to VB.NET 1.1, would I gain anything in terms of
stability?
Any links or other references that might help me would be appreciated!!!
Thanks in advance!!!!
-Brian
I have developed an Office XP COM Add In for a client in VB6. The Add In is
rather simple. It adds a toolbar with a single button to the command bars.
When a user clicks on the button, a dialog/form is displayed asking them to
choose an option. The value selected is then placed in a Custom Document
Property. I also do a little manipulation of the footer based on what was
selected in the form.
The add in is available allows for basically the same functionality for 3 of
the Office products (Word, Excel, PowerPoint). The only thing that is
really different for each is the manipuation of the footers.
It is a single .dll, but contains 4 classes - 1 for each supported Office
product (i.e. Word, Excel, and PowerPoint), the 4th class is the entry point
to the addin regardless of application. So each applications add in
registry keys point to the Connect class, the connect class then
instantiates the appropriate version of the add in class based on which
application it is being called from.
I am noticing, however, some stability problems with the add in. Certain
users are experiencing errors at "random" times from the addin (I know it is
my add in because I catch all exceptions and display a friendlier message to
the user). The only thing that might be common among these users is that
they may be using Word as their email editor for Outlook.
Also, it should be noted that there are a few other addins installed and
loaded on any given user's machine. I believe they have 2 addins
functioning in Outlook (one written in .NET 1.1, the other in VB6). I
believe there is also another addin that is loaded for Word, in addition to
my addin, not sure which language this was written in, but my guess is .NET
1.1.
I am pretty confident that the issue is not a result of buggy code, as I,
and many other users run these addins with no problems and I have
implemented the code into the events I need to hook into.
1. Does anyone have any suggestions or ideas that might help resolve this
issue? For example, is it OK the way I have implemented it with a single
..dll and 4 classes, or should each office application have had it's own .dll
for the addin?
2. Are there known issues with stability and addins running on Office XP
(running in .NET or VB6)?
3. If I moved my addin to VB.NET 1.1, would I gain anything in terms of
stability?
Any links or other references that might help me would be appreciated!!!
Thanks in advance!!!!
-Brian