Repost: What files do I need to include in my msi?

[David Thielen]

Hi;

Which of the following files do I need to have in my msi file? (ie can I not
include some because they get installed with office?)

dornetfxredist_x86.msn
Extensibility.dll
Microsoft.Office.Interop.Word.dll
Microsoft.Vbe.Interop.dll
msaddndr.dll
mscorlib.dll
office.dll
shdocvw.dll
sqldmo.dll
stdole.dll
vc_user_crt71_rtl_x86_---.msm
vc_user_stl71_rtl_x86_---.msm
vjsharpredist_x86.msm

thanks - dave

 

[Mark Bower [MSFT]]

It depends which version of Office you are working with. The Office 2003
PIAs are not redistrtibutable. They are part of the Office install and so
users will already have them. If not they should install on demand anyway.

The PIAs for earlier versions of Office are redistributable and you should
ship and install them yourself.

Don't ship any of the .NET Framework assemblies (e.g. mscorlib)

Don't ship system components either (e.g. shdocvw)



--
Mark Bower
Microsoft
http://blogs.msdn.com/bowerm

This post is provided 'as-is' without warranty and confers no rights.

 

[David Thielen]

Hi;

Ok, I think what you are saying is never include:
mscorlib.dll
shdocvw.dll

If it's Word 2003 and later, then don't include:
office.dll (I am assuming office.dll is the Office PIA.)

And all the others should be installed. (Or are some of the other also
either .NET or Office dlls?)

I'm sorry to have to ask again but I can't find anywhere that says what the
source of each file is (the downside of Visual Studio bringing in file
automatically) so I don't know which belong to .NET, which belong to office,
and which are "other" that I need to bring in.

If there is a url somewhere that syas which files come from where, that
would be a gigantic help.

thanks - dave

 

[Mark Bower [MSFT]]

Office 2003 PIAs:
http://msdn.microsoft.com/library/e...officeprimaryinteropassemblies.asp?frame=true
and
http://msdn.microsoft.com/library/en-us/stagsdk/html/stconPIAs.asp?frame=true

All the .NET Framework assemblies are in your
c:\windows\Microsoft.NET\Framework\v1.1.4322 folder.

Don't ship any of that stuff.

This page has an interesting section about distributing managed Office
solutions:
http://msdn.microsoft.com/library/en-us/stagsdk/html/stconMigrating.asp?frame=true

I don't think a single page exists listing where stuff comes from - but the
information you need will be _somewhere_ on the MS site. The approach I
tend to use is to go to www.google.com/microsoft to do an MS only search,
then search for the dll name and the word distribute.
I just searched for sqldmo distribute for instance and came up with this
page: http://support.microsoft.com/?kbid=326613

Hope that's some help.

Mark.

--
Mark Bower
Microsoft
http://blogs.msdn.com/bowerm

This post is provided 'as-is' without warranty and confers no rights.

 

[David Thielen]

Thank you - this helps a lot. It looks like the only file I need to install
(besides my own) is Extensibility.dll as it is not listed in the list of
Office PIAs (which I think is weird as it is a key part).

One last thing I want to confirm. If a user has Office 2003 installed but
does not have .NET installed, then after they install .NET they need to
reinstall Office to get the PIAs. Is this correct?

If so, wouldn't it be better if I just included all of the PIAs so if they
are in the above situation, they don't need to reinstall Office 2003 - as it
is not obvious at all that that needs to be done.

??? - thanks - dave

 

[Mark Bower [MSFT]]

In developer scenario the developer would need to go to custom setup and
select the PIAs to add. No need to reinstall the whole thing.

In end-user scenario the PIAs should install on demand when your components
are first executed.

--
Mark Bower
Microsoft
http://blogs.msdn.com/bowerm

This post is provided 'as-is' without warranty and confers no rights.