Do I still need a shim with Word 2007?

[David Thielen]

For the authenticode signing to work?

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm

 

[Patrick Schmid [MVP]]

Are you developing a RibbonX based solution? If yes, then you won't be
able to use the COM shim wizard, because it doesn't support those
solutions yet.

Patrick Schmid [OneNote MVP]
--------------
http://pschmid.net
***
Office 2007 RTM Issues: http://pschmid.net/blog/2006/11/13/80
Office 2007 Beta 2 Technical Refresh (B2TR):
http://pschmid.net/blog/2006/09/18/43
***
Customize Office 2007: http://pschmid.net/office2007/customize
RibbonCustomizer Add-In: http://pschmid.net/office2007/ribboncustomizer
OneNote 2007: http://pschmid.net/office2007/onenote
***
Subscribe to my Office 2007 blog: http://pschmid.net/blog/feed

 

[David Thielen]

Oh...

Let me ask a more basic question. We have an AddIn that must run on Word
2000/2002/2003 as well as 2007. For 2000/2002/2003 it all works very nicely.
We use the IDTExtensibility2 API and we have a single set of source code (C#
and J#) and we build in 3 projects using the same source but the PIAs
specific to each version.

The Word 2003 version runs fine on Word 2007. But I figure we should build a
version using the 2007 PIAs and if we can the RibbonX API.

Should we just copy the 3 PIAs over and build a forth version and ignore
RibbonX for now?

And in that case I assume we still need a shim?

Also, is RibbonX for VSTO only? Is VSTO usable for a commercial AddIn yet?
Under Word 2003 it required an associated template and that template required
a fixed path so we couldn't use it.

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm

Are you developing a RibbonX based solution? If yes, then you won't be
able to use the COM shim wizard, because it doesn't support those
solutions yet.

Patrick Schmid [OneNote MVP]
--------------
http://pschmid.net
***
Office 2007 RTM Issues: http://pschmid.net/blog/2006/11/13/80
Office 2007 Beta 2 Technical Refresh (B2TR):
http://pschmid.net/blog/2006/09/18/43
***
Customize Office 2007: http://pschmid.net/office2007/customize
RibbonCustomizer Add-In: http://pschmid.net/office2007/ribboncustomizer
OneNote 2007: http://pschmid.net/office2007/onenote
***
Subscribe to my Office 2007 blog: http://pschmid.net/blog/feed

For the authenticode signing to work?

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm

 

[Patrick Schmid [MVP]]

Let me ask a more basic question. We have an AddIn that must run on
Word

2000/2002/2003 as well as 2007. For 2000/2002/2003 it all works very nicely.
We use the IDTExtensibility2 API and we have a single set of source code (C#
and J#) and we build in 3 projects using the same source but the PIAs
specific to each version.

The Word 2003 version runs fine on Word 2007. But I figure we should build a
version using the 2007 PIAs and if we can the RibbonX API.

You can. Simply use the 2007 PIAs. As far as I have been able to figure
out, a .net shared add-in compiled with the 2007 PIAs works without a
problem in 2003.

Should we just copy the 3 PIAs over and build a forth version and ignore
RibbonX for now?

Your call. It's mainly the question where in the UI your add-in will
appear. If you don't use RibbonX, your add-in's UI will be limited to
the Add-Ins tab.

And in that case I assume we still need a shim?

You should always have a shim, but you cannot use the COM shim wizard
for anything that uses RibbonX. The COM Shim Wizard doesn't support
IRibbonExtensibility yet, which is the interface you need to implement
besides IDTExtensibility2

Also, is RibbonX for VSTO only? Is VSTO usable for a commercial AddIn yet?
Under Word 2003 it required an associated template and that template required
a fixed path so we couldn't use it.

RibbonX is for VBA, .NET shared add-ins, VSTO and COM (e.g. VB6)
add-ins. As mentioned above, you just need to implement the additional
interface.
VSTO is usable for commercial add-ins and with Office 2007 the
restriction of VSTO to only the higher-end SKUs is gone. The big problem
with VSTO 2005 SE and Office 2007 is that I don't know of any single
working deployment of it, neither on XP or Vista. I know of VSTO add-ins
working fine on the dev machines, just not of a single working add-in on
a machine it was deployed to...

Patrick Schmid [OneNote MVP]
--------------
http://pschmid.net
***
Office 2007 RTM Issues: http://pschmid.net/blog/2006/11/13/80
Office 2007 Beta 2 Technical Refresh (B2TR):
http://pschmid.net/blog/2006/09/18/43
***
Customize Office 2007: http://pschmid.net/office2007/customize
RibbonCustomizer Add-In: http://pschmid.net/office2007/ribboncustomizer
OneNote 2007: http://pschmid.net/office2007/onenote
***
Subscribe to my Office 2007 blog: http://pschmid.net/blog/feed

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm

Are you developing a RibbonX based solution? If yes, then you won't be
able to use the COM shim wizard, because it doesn't support those
solutions yet.

Patrick Schmid [OneNote MVP]
--------------
http://pschmid.net
***
Office 2007 RTM Issues: http://pschmid.net/blog/2006/11/13/80
Office 2007 Beta 2 Technical Refresh (B2TR):
http://pschmid.net/blog/2006/09/18/43
***
Customize Office 2007: http://pschmid.net/office2007/customize
RibbonCustomizer Add-In: http://pschmid.net/office2007/ribboncustomizer
OneNote 2007: http://pschmid.net/office2007/onenote
***
Subscribe to my Office 2007 blog: http://pschmid.net/blog/feed

For the authenticode signing to work?

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm

 

[Ken Slovak - [MVP - Outlook]]

I've deployed a few VSTO 2005 SE solutions, but only locally on my lab
machines. But as a principle it works.

I've been able to change the reference from Office 2003 to Office 2007
within the VSTO project, while keeping the Outlook 2003 reference and have
the addin work on both Outlook 2003 and 2007 systems.

Of course mixing and matching different versions of the Office and Outlook
PIA references is completely unsupported, so your mileage may vary. I
haven't done any mixed Word/Excel/PPT addins that way so far in VSTO, but I
have done shared addins for those Office applications that way in both
VB.NET and C#.

 

[David Thielen]

Hi;

First of all, this was very easy to create a Word 2007 version (as you
said). Most of the work was the GUIDs that have to match in the shim and
adding the 4th version to our WIX installer. It all worked the first time.

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm