If it's simple pre-requisite then maybe I agree. But when the Pre-requisite 
itself has several rules and requirements then slowly that itself will be a 
major project than a simple bootstrapper. In my case, pre-requisite has more 
things to check and install than the software.

Let me give few of them
1. OS requirements
2. Admin rights/Vista UAC
3. Screen resolution
4. Harddisk requirements
5. Computername requirements
6. Network requirements
7. .NET Framework
8. SQL Server
9. Previously installed versions of our products (they may not be of the same 
GUID, I have query by some specific registry values)
10.IIS check
12.Certains ports needs to be opened(check Firewall)
13. MDAC check
14. DirectX
15. Certain Device driver check
These are some of the basics pre-requisites I need to make sure it's valid. On 
top some custom requisite from customers that a named Instance check with 
setting Alias names and Preset SQL Server Configuration for protocols. There 
are other post requisite that I may have check well I have to see how Wix is 
going to help me on that.

It's not difficult to achieve this but if a bootstrapper can do some of this 
work easily then I can concentrate on others things.


Arun Perregattur


-----Original Message-----
From: Michael Owings [mailto:mi...@swampgas.com]
Sent: Wednesday, January 07, 2009 9:23 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Multi-project development

I don't know that I'd really agree with that priority. A bootstrapper is
really not that hard to write to start with.

Arun Perregatturv wrote:
> Brian,
>
> I would vote for Burn to kick start sooner than other things. The most 
> important thing for any or all installer is the BootStrapper without that 
> installing will be very difficult.
> As I said before, the Setup.exe I have to write in Win32 since .NET Framework 
> won't installed to begin with, I already have code in Win32 that checks for 
> .NET/SQL Server/Special characters in computer names and manually check 
> product version and so on from the Registry.
>
> If I can suggest Bob Arnson/Rob Mensching to add some additional features for 
> Burn such as CD Browser which can read from an XML file that would great.
> Burn can create a setup.exe using XML and add Buttons and Actions to read XML 
> file which will have something like this
> <CD>
>         <Button Text="Install Server" Action="DoInstall"/>
>         <Button Text="Install .NET Framework" Action="DoFrameworkInstall"/>
>         <Button Text="Install SQL Server" Action="DoSQLInstall"/>
> </CD>
>
> Then use <CustomAction> to Either Install from <CD>\NET35\Setup.exe something 
> like this would be great.
> All the work we do in Wix is to install software but I am sure everyone will 
> have some sort of Pre-requisite before installing they want users to either 
> click on it or do it silently.
>
> Thanks,
--
Teleoperate a roving mobile robot from the web:
http://www.swampgas.com/robotics/rover.html

------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to