Visual Studio Tools for Office

[NewsArchive]

Friedrich,

Is it possible to add the VSTO runtime as part of the SB7 redistributable
manager?

Here's 2 URLs covering the topic:
http://blogs.msdn.com/vsto/archive/2008/12/17/deploying-office-2003-solutions-with-windows-installer-mary-lee.aspx
http://code.msdn.microsoft.com/VSTO2005SEMSI
--

Mark Riffey
http://www.rescuemarketing.com/blog/
Now featured on the Visa Business Network
If Guy Kawasaki, the staff of the Wall Street Journal,
Fast Company, Marketing Profs & Business Week read it,
maybe you should too.

Follow me on Twitter at http://twitter.com/MarkRiffey
Friend me on Facebook at http://facebook.com/MarkRiffey

[NewsArchive]

> Is it possible to add the VSTO runtime as part of the SB7 redistributable
> manager?

Here's a more up-to-date coverage of VSTO deployment.
--

Mark Riffey
http://www.rescuemarketing.com/blog/
Now featured on the Visa Business Network
If Guy Kawasaki, the staff of the Wall Street Journal,
Fast Company, Marketing Profs & Business Week read it,
maybe you should too.

Follow me on Twitter at http://twitter.com/MarkRiffey
Friend me on Facebook at http://facebook.com/MarkRiffey

[NewsArchive]

The link would help:)

http://blogs.msdn.com/mshneer/archive/2008/04/24/deploying-your-vsto-add-in-to-all-users-part-iii.aspx
--

Mark Riffey
http://www.rescuemarketing.com/blog/
Now featured on the Visa Business Network
If Guy Kawasaki, the staff of the Wall Street Journal,
Fast Company, Marketing Profs & Business Week read it,
maybe you should too.

Follow me on Twitter at http://twitter.com/MarkRiffey
Friend me on Facebook at http://facebook.com/MarkRiffey

[NewsArchive]

Hi Mark,

> Is it possible to add the VSTO runtime as part of the SB7 redistributable
> manager?

The "Redistributable Manager" only supports some of the "main" Core
PreRequisites (e.g. VC++2008).

But you don't need VSTO as part of the "Redistributable Manager" to deploy
it :) Just download the VSTO redistributable from the Microsoft web site
and launch it from your installer. To make it "reusable", you can add the
redistributable and some deployment logic to an Include Script (.sbi) and
call the VSTO.sbi from your main installer projects. That's exactly what
the packages in the "Redistributable Manager" do. A runtime include script
is nothing more (or less) than the original redistributable and some
deployment logic packaged into a .sbi. Such a .sbi can be used to deploy
any redistributable (original Microsoft runtimes, 3rd party runtimes, etc.).

Because there are 20,000+ different redistributables out there for all kind
of Windows operating systems, development environments, etc., it's
impossible (and quite often not allowed) to develop a pre-defined
Redistributable Manager item for each and every standard redistributable.
Our Script Writing Consulting can be hired to develop runtime include
scripts for specific redistributables. We have developed 400+ different
runtime include scripts during the last few years, mostly for large
companies doing complex runtime distribution. But I think for VSTO, the
Script Writing Consulting would be an overkill.

As I understand it, you only have make sure (from the installer script) that
the .NET Framework 3.5 and Office (components) are available before you
launch vstor30.exe

http://www.microsoft.com/DOWNLOADS/details.aspx?FamilyID=54eb3a5a-0e52-40f9-a2d1-eecd7a092dcb&displaylang=en
http://msdn.microsoft.com/en-us/library/ms178739.aspx

What do you think?

Friedrich

[NewsArchive]

> Because there are 20,000+ different redistributables out there

Is that all?<g>

Thanks Friedrich.
--

Mark Riffey
http://www.rescuemarketing.com/blog/
Now featured on the Visa Business Network
If Guy Kawasaki, the staff of the Wall Street Journal,
Fast Company, Marketing Profs & Business Week read it,
maybe you should too.

Follow me on Twitter at http://twitter.com/MarkRiffey
Friend me on Facebook at http://facebook.com/MarkRiffey

[NewsArchive]

>> Because there are 20,000+ different redistributables out there
>
> Is that all?<g>

<G> :)

Friedrich