No it's not the case. The real issue is usually about what tool you use to
build MSI files. People that have only used Visual Studio setup&deployment
projects to generate MSI files get exposed to a very limited set of
capabilities. One of the features of Visual Studio setup projects is they
upgrade (in VS 2005) by effectively uninstalling the old version then
installing the new. In VS 2008 it's more of an overwrite, but in both cases
you generate a complete MSI file and use the RemovePreviousVersions option.
More advanced users of MSI setups (using tools like WiX, InstallShield,
Wise, Advanced Installer etc) have a few more choices, including generating
patches. If you think about updates to Office and Visual Studio, they are
updated using patches (msp files) and definitely not by uninstalling the
entire product first. So what you're hearing is just misinformation. People
with your deployment scenarion often use a group policy deployment object to
assign the MSI file to the machine, so it installs when a user logs on, and
this install can be done even if the actal user does not have administrative
privileges.
--
Phil Wilson
Definitive Guide to Windows Installer
http://www.apress.com/book/view/1590592972
"Sheldon" <(E-Mail Removed)> wrote in message
news:BC9AE1AE-2258-412F-A3C3-(E-Mail Removed)...
> Hello -
>
> I have a windows app that needs to be deployed via an MSI installer to
> 200+
> users.
>
> This app will require updating at various times. From what I've read,
> there
> is no way to update something deployed via MSI short of uninstalling and
> reinstalling. Is this really the case???????
>
> (I can't use ClickOnce because the users change desks and thus, machines,
> quite frequently.)
>
> Any help will be greatly appreciated!
>
>
> --
> Sheldon