B
- B@rney
Hi Guys'n Dolls!
I've been working quite som time on a Shared Add-in for Word, Excel and
PowerPoint. I started with a Extensibility Project and the wizard also added
a Deployment Project. Using the .msi created works great on client machines
that have DotNetFrameWork, and the Office PIA's installed.
The Deployment Project suggest copying the Office InterOp .dll's to the
application folder on the client's machines. Is this the recomended way of
getting the PIA's onto machines without them?
And what about the DotNetFrameWork? I've installed the DotNet bootstrapper
project thingy, so I get a setup.exe that checks for the framework, and
installs it if neccessary, but it sure isn't pretty. What's the Best Practise
when deploying .NET Shared Add-ins to client computer when you don't know
whether dotnetfx and/or the Office PIA's are installed?
And how about larger organisations that might use SMS or AD to deploy
applications? What type of installation package is recommended then?
I've been working quite som time on a Shared Add-in for Word, Excel and
PowerPoint. I started with a Extensibility Project and the wizard also added
a Deployment Project. Using the .msi created works great on client machines
that have DotNetFrameWork, and the Office PIA's installed.
The Deployment Project suggest copying the Office InterOp .dll's to the
application folder on the client's machines. Is this the recomended way of
getting the PIA's onto machines without them?
And what about the DotNetFrameWork? I've installed the DotNet bootstrapper
project thingy, so I get a setup.exe that checks for the framework, and
installs it if neccessary, but it sure isn't pretty. What's the Best Practise
when deploying .NET Shared Add-ins to client computer when you don't know
whether dotnetfx and/or the Office PIA's are installed?
And how about larger organisations that might use SMS or AD to deploy
applications? What type of installation package is recommended then?