.exe vs .msi

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Does installing using .msi requires windows installer installed? and .exe
doesn't?

If so, under what circumstances would be an user NOT having windows
installer installed? My impression is that windows installer comes with OS.

Any other defferenciations between .exe and .msi?


Thanks,
 
windows installer is bundled with OS but not the Version 3 which you either
have to download or install the SP2 etc.
As for exe, a lot of setup.exe esp. form MS invokes .msi and uses Windows
installer.
 
..msi files are Windows Installer files. .exe files are executable files,
i.e. programs. Some .exe files, related to installer files, may be
self-extracting compressed files that contain .msi files.

It's not a matter, with XP, if Windows Installer is installed, it's whether
it works correctly or not.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
Thanks for the replies.

I'm actually on the dev/test side and would like to know all that's about
..exe and .msi, instead of how it would affect me as an individual installer.

I think I know that .exe acts as a wrapper would eventually call a .msi.

I guess my question is under what sceanario would a user NOT having

- windows installer?

- correct version of windows installer? ie, Version 3, what is it about?
what does it do extra than previous versions? what version comes with default
Windows (I'll be needing to ensure all Windows platform will work for our
product)

- correct functioning windows installer. when would a windows installer not
working as expected handling .msi file, would having .exe totally address any
of potential issues of this kind?

Thanks,
Jim
 
Windows Installer
http://msdn.microsoft.com/library/en-us/msi/setup/windows_installer_start_page.asp

Using Windows Installer
http://msdn.microsoft.com/library/en-us/msi/setup/using_windows_installer.asp

Windows Installer Guide
http://msdn.microsoft.com/library/en-us/msi/setup/windows_installer_guide.asp

Windows Installer Examples
http://msdn.microsoft.com/library/en-us/msi/setup/windows_installer_examples.asp

Windows Installer Reference
http://msdn.microsoft.com/library/en-us/msi/setup/windows_installer_reference.asp

How to Create an MSI Package
http://support.microsoft.com/default.aspx?scid=kb;en-us;257718

MSI Packaging Tools
http://www.windowsnetworking.com/articles_tutorials/MSI-Packaging-Tools.html

Windows Installer technologies
http://www.microsoft.com/windows200...ed/help/sag_WinInstall_Technology.htm?id=3991

How to create a nested .msi package
http://support.microsoft.com/default.aspx?scid=kb;en-us;306439

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
I think I know that .exe acts as a wrapper would eventually call a
.msi.
Click to expand...

Not necessarily. MSI is a new installation technology that includes
nifty features such as self repair and transforms. EXE type installs
(such as InstallShield) just dump the files and exit (generally
speaking).

It sounds like you aren't using any of MSI's advanced features, so an
EXE type install sounds like what you need.
I guess my question is under what scenario would a user NOT
having

- windows installer?
Click to expand...

Windows 9x. I think Windows 2000 (none-SP) has version 1.0. Later
service packs had 2.0. XP comes with 2.0 out of the box.

Adam
 
Back
Top