Publisher Addins Built With VS2005 Don't Work

[Mark W]

I have just upgraded Visual Studio from 2003 to 2005 and am in the process of
converting my VB applications. Most conversions have gone quite smoothly.

However, I have several Add-Ins that I developed to add button bars to
Publisher 2003. When built these under VS 2003, they worked. I used the
conversion wizard in VS 2005 to convert them. I then rebuilt and installed
them. They refused to work in Publisher. I checked the registry and it
appeared that the install was clean.

I notice that there were two warnings (see below) that were generated in the
builds, so I decided to try creating a small add-in from scratch. Using the
Shared Add-in template under the Extensibility section of Other Project
Types, I specified that I wanted to develop in VB and that the solution would
be used by Publisher alone. The generated code did not have the warnings
that my old add-in was showing. I made sure that the proper references,
imports, etc. were all specified. I added msgbox displays to each of the
event sections. I did not add any other code. I built and installed this
solution, then started Publisher... Nothing.

I have searched every possible help source that I can find and cannot find
anything that directly addresses this problem. I noticed that VSTO is
mentioned a lot. I am having trouble understanding what it will do for me,
if anything. I cannot find any mention of it working with Publisher.

1. Does anyone have any idea as to how I can get these add-ins to work?
2. What exactly, if anything, will I gain by downloading VSTO? (I am not
eager to give up another 2 gigs of my C: drive, if I can avoid it.)

The two warnings that I got after I converted one of the add-ins were:

"Type of parameter 'RemoveMode' is not CLS-compliant "

in the following code:

Public Sub OnDisconnection(ByVal RemoveMode As
Extensibility.ext_DisconnectMode, _
ByRef Custom As System.Array) _
Implements Extensibility.IDTExtensibility2.OnDisconnection

and...

"Type of parameter 'ConnectMode' is not CLS-compliant "

in this code:

Public Sub OnConnection(ByVal Application As Object, _
ByVal ConnectMode As Extensibility.ext_ConnectMode, _
ByVal AddInInst As Object, ByRef Custom As System.Array) _
Implements Extensibility.IDTExtensibility2.OnConnection

Any assistance will be greatly appreciated.

Thanks,

Mark.

 

[Bob Butler]

I have just upgraded Visual Studio from 2003 to 2005 and am in the

You might want to take microsoft.public.vb.addins off the cross-post list
and add groups with "dotnet" in the name. microsoft.public.vb.addins is for
VB 6.0 and earlier and not the misnamed VB200x languages.

 

[Mark W]

Bob,

How does one go about changing the cross-post list?

 

[Bob Butler]

Bob,

How does one go about changing the cross-post list?

If I'm reading the header right you are using Outlook Express; if so, when
you reply to the post just edit the list of newsgroups included. You can't
edit the ones that have already been posted.

 

[Mark W]

Hi Bob,

No, I am doing this in Internet Explorer, not Outlook Express.

I now notice that "Advance Options" is available at the bottom of this
"Reply To" page.

However, I have gone through every newsgroup under Microsoft.English and I
cannot see any forums that have dotnet as part of their names. Also, under
Visual Studio .Net (Microsoft.Public.VSNet), I do not see any discussion
groups that deal with VB.Net or Add-ins or Publisher.

Thanks...

 

[Mark W]

Oops, sorry Bob,

I just noticed Microsoft.Public.dotnet.languages.vb. I'll cross post to
there.