Hi,
permanent packages are excluded from rollback. You normally use permanent
packages for redistributable packages like .Net Framework which you do not want
to uninstall.
Regards,
Markus
www.xeam-solutions.com
> James McConville hat am 18. Juni 2014 um
> 13:27 geschrieben:
>
>
> Hi folks,
>
>
Hi,
to place a package on disk layout you can use attribute "name".
e.g. set name=redist\WindowsXP-KB942288-v3-x86.exe to get your expected result
Markus
www.xeam-solutions.com
> froggie hat am 18. Juni 2014 um 13:32
> geschrieben:
>
>
> Hi!
> I'm trying to create a bootstrapper which is also
Hi,
you can add a copy command in Post-Build Event to achieve this.
In project settings -> Build Events add "copy /Y !(TargetPath) C:\MSI" to post
build event command line
Or add
copy /Y !(TargetPath) C:\MSI
to you wixproj.
Markus Wehrle<http://www.xeam-solutions.com>
dle v1.1 is an upgrade of Bundle v1.0 then
> v1.0 will be removed after v1.1 is installed. Reference counting should mean
> the 20 packages are not removed if Bundle v1.1 lists them (as I noted below).
>
> -Original Message-
> From: Markus Wehrle [mailto:mar...@laika42.com]
Installation of 1.1 will work with a minimum download of the 5 changed
packages if you create a web installer in burn including all 25 packages.
But what will happen with your installed version 1.0 in ARP? The entry will
stay there. If your 1.0 package gets uninstalled it does not care about the
de
Hi,
Is there a reason why you cannot use major or minor updates for your product?
Using MSP files to patch your product will show the correct product size and
there is no need to delete control panel entries.
Regards,
Markus
> Chaitanya hat am 11. Oktober 2013 um 10:00
> geschrieben:
>
>
> H
Please have a look into bundle.wxs of WixBa. There you find
Having this tag defined in your bundle, the DetectUpdateBegin event is fired.
> dirt hat am 8. Oktober 2013 um 23:58 geschrieben:
>
>
> I am using the WiX Source\Setup\WixBA as a starting point for a custom
> managed bootstrapper appl
Hi,
The best way to install multiple setups as chain is to use a bootstrapper. In
WiX this bootstrapper is called burn.
Burn also handles uninstall and repair for all setups in the chain.
Regards,
Markus
> dileep s hat am 9. Oktober 2013 um 08:02
> geschrieben:
>
>
> Dear All,
>
> Its my req
Hi,
Did you set an UninstallCommand and RepairCommand for your ExePackage. You also
should provide a DetectCondition, so that burn can detect if your exe is
installed or not.
Markus
> Adam Roper hat am 7. Oktober 2013 um 10:43
> geschrieben:
>
>
> (Apologies for the faked 'reply' on this one,
Hi,
You can update the individual msi files using minor updates (MSP). This does
not have impact on the bundles uninstall/repair behavior.
For major updates you should update the bundle. (Although it is possible to
do a major update on the MSI directly) If you perform an major update on a
msi, th
Hi,
Wix Toolset uses Burn to install. The normal Parameters for burn should work.
See Robs answer of this post
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Running-Burn-driven-installer-in-quiet-mode-command-line-parameters-td5913001.html
Am 05.06.2013 um 23:00 schrieb Vinay ve
"yes"
> InstallSize="100"
> Name="Sauvegarde.exe"
> Compressed="no"
> DownloadUrl="$(var.UrlSauvegarde)">
> CertificatePublicKey="D2A6F974A08D42D7795C7AA5440E04E16DDCFD06"
>
Hi Benjamin,
we do not have this issue and can successul download exe package in out burn
configuration.
Can you provide more details, e.g. the complete ExePackage definition and the
content of $(var.UrlSauvegarde)?
> Benjamin Mayrargue hat am 31. Mai 2013 um 10:33
> geschrieben:
>
>
> Hi all,
Hi,
Are the registry keys filled with properties entered or modified by the user?
If so, are the registry keys set to default in your patch case?
Am 24.05.2013 um 11:32 schrieb Ravishankar
:
> Hi All,
> My main installer creates some registry entries(Database
> ServerName,Database Name etc)
Hi,
you have to add the additional files using payload
Data1.cab/>
. other files required.
> Pierre-Alain GALTIER hat am 23. Mai 2013 um
> 11:34 geschrieben:
>
>
> Hello,
>
>
>
> I've a third party software setup with multpile files:
>
> - setu
Just set Arpsystemcomponent propersty to 1 and the MSI will not be shown.
Am 21.05.2013 um 21:22 schrieb "Mamidi, Balasubrahmanyam"
:
> Hi, I am creating many MSI files using wix installer. when installed MSI file
> it will put the file in Add/Remove programs.
>
> My client asking, stop addi
I also would prefer to make a prerequisite bootstrapper without WPF UI to
install .net 4.5. If you install an update of .Net in a managed bootstrapper
you propably will ran into a system reboot, cause .Net assemlies are loaded
which might be replaced during .Net 4.5 Installation.
If you do not n
gt; I am building an application using tideSDK and now I am trying to custom
> the installation process by modify the source code of the tide SDK.
>
>
> On Wed, May 8, 2013 at 6:01 PM, Markus Wehrle wrote:
>
>> Hi, you can achieve this using burn.
>>
>> Am 08.05.2013 um
Hi, you can achieve this using burn.
Am 08.05.2013 um 11:12 schrieb Yuliang li :
> hi
> does anyone here know how to build a installer with download manager? So
> the user would download a lightweight installer, select the components they
> want to install and the installer would download the nec
Hi Nick,
Burn bootstrapper core is native Code, so it does not read .net configuration
files. You can add a configuration file for your managed assembly which runs
within the bootstrapper. You then habe to Olaf the configuration file by hand.
Don't forget to add the config file to the payload.
20 matches
Mail list logo
