http://www.csscript.net/WixSharp.html
"Wix# (WixSharp) is a new member in the CS-Script family. Wix# is a managed
interface to WiX (Windows Installer XML toolset for building Windows
installation packages from XML source code)."
"Wix# allows building a complete MSI or WiX source code by executing script
files written with the C# syntax. It uses a C# class structure to mimic WiX
entities and their relationships in order to produce a valid deployment model."
In general, I personally find the library to be limiting but it does try to
follow some reasonable design principles for simple projects. It has a bad
policy of including the compiled EXE used to generate the MSI once for each and
every managed custom action you define rather than including it once and
referencing the binary multiple time. That's just one of my complaints on Wix#.
I see that it does include nbsbuilder.exe:
PS C:\WixSharp.0.1.30> .\nbsbuilder.exe /?
Building bootstrapper...
Native Bootstrapper Builder v 1.0.0
Copyright (C) 2010 Oleg Shilo.
Builds simple native (Win32) bootstrapper. It alows building a bootstrapper for
two deployment applications: primary setup and its prerequisite.
NBSBUILDER /out:<outFile> /first:<firstMSI> /second:<secondMSI> /regkey:<reg>
[/verify:<yes|no>] [/icon:<path>]
first - the setup application to be run the first (prerequisite).
second - the setup application to be run the second (after
running prerequisite)
out - name of the output file (bootstrapper) to produce
reg - the registry key that indicates if firstMSI should be run.
If the 'reg' value exists in registry the firstMSI will be
considered already installed and will not run.
Registry value should comply with the following pattern.
<HKEY>:<SubKey>:ValueName>
Examples:
'HLKM:SOFTWARE\Microsoft\.NETFramework\v2.0.50727:' .NET v2.0,
'HLKM:SOFTWARE\Microsoft\.NETFramework:' any version of .NET,
'HLKM:SOFTWARE\MyCompany\MiProduct:InstallDir' InstallDir value
verify - flag (yes/no) indicating if the registry key (/regkey:<reg>)
should be checked again after running prerequisite. Default: yes.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
> -----Original Message-----
> From: Ken Halprin [mailto:khalp...@autosoln.com]
> Sent: Tuesday, March 23, 2010 1:32 PM
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] Using Microsoft CRT 8.0 and 9.0 merge modules
> in thesame MSI
>
> What is Wix# and nbsbuilder? Where can I get more information about
> them?
>
> Thanks,
> Ken
>
>
> -----Original Message-----
> From: s...@pacaccess.com [mailto:s...@pacaccess.com]
> Sent: Tuesday, March 23, 2010 9:55 AM
> To: nor...@acm.org; General discussion for Windows Installer XML
> toolset.
> Subject: Re: [WiX-users] Using Microsoft CRT 8.0 and 9.0 merge modules
> in
> thesame MSI
>
> This is a timely thread for me as I have been recently going through
> this
> myself. In my research I found there are two ways to bundle the VC++
> runtime:
>
> * With a merge module. This approach is documented
> (http://wix.sourceforge.net/manual-wix3/install_vcredist.htm) but has
> the
> disadvantage of taking A LONG time when uninstalled. On my machine, it
> takes 3-4 minutes for them to be uninstalled and unmerged when my
> product
> is uninstalled. This is not good as it appears to the user as if the
> uninstaler has locked up, and can be canceled at any time. A 'fix' I
> made
> for this approach was to modify the default UI strings and change the
> text
> which appears in the wizard page to say:
> <String Id="ProgressDlgTextRemoving">Please wait while the Setup
> Wizard
> removes [ProductName]. PLEASE
> NOTE:
> This process takes several minutes - please be patient.</String>
>
> * With a bootstrapper. If I understand the term correctly, a
> bootstrapper
> merges two installers into one and runs them sequentially. Along with
> WiX
> I have been playing with WiX#. Within the WiX# package is an
> application
> called nbsbuilder.exe which I'm using to bootstrap the vc++ runtime
> along
> with my installer. For the moment I'm not using WiX# - just
> nbsbuilder.exe, and my post-build script is:
>
> nbsbuilder.exe /out:MyProductSetup.exe /first:vcredist_x86.exe
> "/second:MyProductSetup.msi"
> /reg:HKLM:SOFTWARE\Classes\Installer\Products\3e43b73803c7c394f8a6b2f04
> 02e19
> c2:DeploymentFlags
> /verify:yes
>
> With the registry key that's there, that's going to be specific to the
> version of vcredist_x86 you are installing. I used a registry diff
> tool
> to see what changes were made to the registry when vcredist_x86 was
> installed.
>
>
> For the moment, it looks like the bootstapping approach is better for
> me
> so I'm going with it.
>
> Jeff
>
>
>
>
> >
> > I would be interested in whether you are able to *remove* your
> application
> > after having installed the VC libs via Merge Modules.
> > I am seeing the UNinstallation take approximately 5 minutes (while
> the VC
> > libs are being removed), with the dialog appearing to be 'hung'.
> > Most users will give up and cancel the uninstallation before it
> completes.
> > This of course is unacceptable.
> >
> > -Clift
> >
> >
> > -----Original Message-----
> > From: Pally Sandher [mailto:pally.sand...@iesve.com]
> > Sent: Tuesday, March 23, 2010 5:54 AM
> > To: ma...@thejunkroom.co.uk; General discussion for Windows Installer
> XML
> > toolset.
> > Subject: Re: [WiX-users] Using Microsoft CRT 8.0 and 9.0 merge
> modules in
> > thesame MSI
> >
> > You can safely ignore them. They're caused by having either of the
> VC++
> > runtime merge modules consumed by your MSI. It's not an artifact of
> > having both v8.0 & v9.0.
> >
> > Palbinder Sandher
> > Software Deployment & IT Administrator
> >
> >
> > -----Original Message-----
> > From: Mark Simonetti [mailto:ma...@thejunkroom.co.uk]
> > Sent: 23 March 2010 09:20
> > To: wix-users@lists.sourceforge.net
> > Subject: [WiX-users] Using Microsoft CRT 8.0 and 9.0 merge modules in
> > thesame MSI
> >
> > Hi all,
> > I am currently writing an installer that needs to install both Visual
> > Studio 2005 AND 2008 C Runtime Libraries. The reason is that some of
> > the binaries I have to install (PostgreSQL) are built with Visual
> Studio
> > 2005, and my own binaries are built with Visual Studio 2008.
> Everything
> > must be installed easily with one installer, hence why I am handling
> the
> > PostgreSQL install in my own installer.
> >
> > The problem is when I try and use the merge modules for both runtime
> > libraries, I get the warnings listed at the bottom of this post.
> >
> > When I run the installer, all seems to go okay so maybe there isn't a
> > problem, though the test machine is not currently clean so it might
> just
> > seem okay. I'm going to wipe the test machine and give it another
> try,
> > but either way I thought it prudent to check with others if there
> could
> > be any potential issues, and to see if there is perhaps a better way
> of
> > doing all of this.
> >
> > I did try just running the setup for the redistributable installs
> from
> > my installer, but then I got errors about not being able to run
> multiple
> > msi installs, etc....
> >
> > Warnings listed below .. thanks!
> >
> >
> >
> >
> -----------------------------------------------------------------------
> -----
> --
> > Download Intel® Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > _______________________________________________
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> >
>
>
>
> -----------------------------------------------------------------------
> -----
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> -----------------------------------------------------------------------
> -------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
