Windows installer structure



I am a big fan of innosetup but I have had no need for msi installers in 
the applications I have used it for.

Far be it for me to suggest an MS alternative but wix is their "open 
source" installer which supports MSI.  I have never used it in anger.

http://msdn.microsoft.com/smartclient/default.aspx?pull=/library/en-us/dnwingen/html/wixsetup.asp

Herb Martin wrote:

>>I like the existing installer. I installed a working version on a 
>>windows XP computer at my school without being an Administrator. 
>>I use Power BASIC and it runs without Administrator access. 
>>What is the advantage to .msi?
>>    
>>
>
>Works as well as the above for direct (or local)
>install, and has the features to be projected from
>Group Policy to many computers in an Active Directory
>domain.
>
>Also supports (custom) MST 'template' files so that
>an admin can override and control the MSI deployment
>without modifying the MSI (i.e., you write an MST to
>customize the existing MSI to bypass options, change
>options, etc.)
>
>  
>
>>I can remember the complicated process of installing software on 
>>windows 2000. The only way you could uninstall some software was to 
>>uninstall all of windows 2000. 
>>    
>>
>
>Bad software (installer).  MSI also supports Group
>Policy REMOVING the software, fixing it if damaged,
>"install on first use", (simple) publishing in Add/
>Remove programs etc.
>
>  
>
>>I still have Macsyma and DERIVE 
>>running on a windows 98 computer and a windows 95 computer. I like 
>>the power of XP but windows 95 turns on and off in seconds. 
>>    
>>
>
>MSIs work on Win95 if IE has been upgraded to at least IE 5.0.
>(Practically all.)
>
>MSIs provide the extra features to Win2000+ when running
>in a domain.
>
>MSIs are the basis of Windows & Microsoft Update as
>well as Automatic Updates, and of course GPO installs
>in a domain.
>
>Imagine someone with hundreds of university machines
>in an AD domain; the MSI makes adding, removing,
>repairing, and updating the software almost trivial
>from the AD Group Policy.
>
>Anyone with a "bunch" of computers and an AD domain
>can benefit, but for those without an AD the MSI
>works just like other installers.
>
>  
>
>>I hope you keep Maxima simple.
>>    
>>
>
>Maxima is not simple, but it should be kept simple to
>install and as simple as practicable to use.
>
>
>Herb Martin, MCSE, MVP
>HerbM at LearnQuick.Com http://LearnQuick.Com
>512 388 7339   -or-   1 800 MCSE PRO
>Accelerated MCSE in a Week Seminars 
>
>  
>
>>-----Original Message-----
>>From: maxima-admin at math.utexas.edu 
>>[mailto:maxima-admin at math.utexas.edu] On Behalf Of Jim FitzSimons
>>Sent: Friday, June 16, 2006 9:14 AM
>>To: maxima at math.utexas.edu
>>Subject: RE: [Maxima] Windows installer structure
>>
>>
>>
>>-----Original Message-----
>>From: maxima-admin at math.utexas.edu 
>>[mailto:maxima-admin at math.utexas.edu] On
>>Behalf Of Vadim V. Zhytnikov
>>Sent: Thursday, June 15, 2006 7:39 AM
>>To: Herb Martin
>>Cc: maxima at math.utexas.edu
>>Subject: Re: [Maxima] Windows installer structure
>>
>>Herb Martin writes:
>>    
>>
>>>>I worry that Windows Installer packaging is not planned
>>>>at least now.  Do you know any free tool for making .msi
>>>>packages?
>>>>
>>>>        
>>>>
>>>The WinInstallLE (light edition) comes with Server for
>>>certain (I am unsure but believe it may also be on the
>>>XP CDROM).
>>>
>>>The Visual Studio (of course is not free) has an installer
>>>packager.
>>>
>>>It is my impression that there are others which have
>>>working free versions but I have no further information.
>>>
>>>The key point about MSI is that it allows for mass installs
>>>by Active Directory Administrators.  (It's pretty good
>>>technology too, but not -- to my knowledge Open Source.)
>>>
>>>      
>>>
>>Let me explain may position.  Maxima build on Windows
>>should no rely on any additional software besides
>>Windows itself and packages freely available on the net.
>>Anyone having Windows and Internet access should be
>>able to build maxima without trouble.  At present Windows
>>Maxima build requires:
>>
>>1. msys, mingw and some msys packages as compiler/linker
>>2. starkit as tcl/tk wrapper
>>3. gnuplot
>>
>>Thus Visual Studio based solution will not do as the only solution.
>>We can't require extra software which costs hundreds of dollars
>>just to build Maxima on Windows.  WiX is probably OK.
>>It is free, it doesn't require any additional software.
>>Votive (WiX's user-fiendly project designer)
>>is Visual Studio plug-in but the project it
>>produces can be processed by freely available WiX.
>>But honestly now I'm not ready to switch to WiX
>>completely.  For forthcoming Maxima 5.9.4 I plan to provide
>>traditional Inno Setup installers.  If anyone volunteer
>>to make any kind of .msi packagin as alternative
>>this will be great.
>>
>>Best wishes,
>>
>>Vadim
>>
>>
>>-- 
>>      Vadim V. Zhytnikov
>>
>>       <vvzhy at mail.ru>
>>      <vvzhy at netorn.ru>
>>
>>
>>_______________________________________________
>>Maxima mailing list
>>Maxima at math.utexas.edu
>>http://www.math.utexas.edu/mailman/listinfo/maxima
>>
>>    
>>
>
>_______________________________________________
>Maxima mailing list
>Maxima at math.utexas.edu
>http://www.math.utexas.edu/mailman/listinfo/maxima
>  
>