I'm researching something ( new to me )... deploying VSTO add-ins. The
project that I'm working on involves several addins targeting both Office 2003
( vsto 2005se) and Office 2007 ( vsto 3.0 ). There are also components
outside of office that ressemble a more traditional windows application.
We want to bundle all of his together so ClickOnce doesn't seem approriate. (
Correct/Wrong? )
So the articles I've read point to using MSI to copy the files to the target
FS and calling %CommonProgramFiles%\Microsoft Shared\VSTO\9.0\VSTOInstaller.exe
to install the vsto packages.
Has anyone seen an alternative to this EXE CA pattern? Are there any
automation interfaces, WiXExtensions, etc to make this a better story? It
seems like another case of "devenv /setup" to me.
---------------------------------
Looking for last minute shopping deals? Find them fast with Yahoo! Search.-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
