No sorry. I meant the prerequisite is started by clicking on
setup.exe. Then a dialog appears if the launch condition for the
prerequisite is not satisfied and the user can confirm to install it.
As I remember the bootstrapper aborts if the user cancels the
prerequisite installation. So he is oblig
Ok that worked. I now am getting the new folder and the prerequisite .msi
file.
Based on my test and your comment the prereq will Not run via clicking on
the setup.exe so the user will be required to make that choice themselves.
Correct?
On Tue, Mar 29, 2011 at 2:32 PM, Tobias S wrote:
> Try
Try BootstrapperItems="@(BootstrapperFile)" instead of
BootstrapperItems="$(BootstrapperFile)" in project file:
Additionally an additional folder is created and the prerequisite is
not included into the setup.exe
Regards
Tobias
2011/3/28 Paul Brook :
> Thanks for the reply.
>
> I have tried
Thanks for the reply.
I have tried to implement the bootstrapper based on your suggestion and I am
not getting any more errors. However the setup.exe is not getting bigger so
I know the .msi file didn't make it into the setup.exe. I also ran the
setup.exe and the bootstrapper didn't run.
I can d
Hi,
At first glance for me the two files product and pacack.xml seem to
have the wrong content.
As you describe your requirements have a look at SQL Server Compact
Edition Prerequisite as it has a similar structure and the intention
to install MSI packages.
Pleaase therefore diff the whole folde
Hi all,
I am attempting to build a bootstrapper for my wix installer in order
install another program our customer wants deployed along with ours. I've
been given the .msi file.
Here's the error / warning I'm getting:
warning MSB3155: Item 'Network.Configurator' could not be located in
'C:\Progra
6 matches
Mail list logo
