Hello,
I have a bootstrapper in Wix Burn with managed UI. Bootstrapper requires
.NET 4 but I also need to install .NET 4.5.1 as part of installation. I
added .NET 4.5.1 to install chain and it installs just fine, but because
bootstrapper itself is using .NET it always requires reboot after
I think we cannot use the DLLWRAP.dll. Because it has been developed by
Flexera. So License infringement.
Sampat
--
View this message in context:
Windows Installer only ignores the 4th digit of the MSI version. It'll evaluate
all four places of a file version.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Lukas
I thought it treated files like MSIs and only compared the first three
digits, so I glanced over the version number. Comparing them again, OLD
NEW.
File Table |File| Component_
| FileName| FileSize | Version
I opened up both MSIs in Orca and compared their version numbers.
The missing files are different, but their version only differs in the
forth place (which is ignored by MSI). The fourth place of the upgrading
files is actually higher, so there are no higher version components on
disk.
Files
The pre-req bootstrapper only kicks in if the managed bootstrapper application
can't be loaded. If it can, it doesn't evaluate pre-req packages.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
IBootstrapperEngine.FormatString
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: Friday, 24 April, 2015 17:46
To:
Hi Jiri,
I just managed the task you describe (albeit wit .Net 4.5.2.) with the
follwing setup.
--- BootstrapperCore.config
-
?xml version=1.0 encoding=utf-8 ?
configuration
configSections
sectionGroup
Is this really a Restart Manager thing? As far as I know it's just
Window Explorer=Tools=Folder Options=View and set Restore previous
folder windows at logon.
---
Phil Wilson
On Thu, Apr 23, 2015 at 10:43 PM, Kashif Md. mdkashi...@gmail.com wrote:
No one using Restart Manager to
No problem. This is what we do for our customers every day at FireGiant
(although FireGiant answers are far more detailed than the 1-2 sentences I have
time to write here).
_
Short replies here. Complete answers over there:
Then including the Binary dllwrap.dll and sequencing the CA Setlimited same
as in IS MSI should be half way to use the same DLL(s). Maybe porting the
c++ CA to DTF C++ might be a possibility...
--
One dashboard for servers
The version attribute complements the registry key where 'Install' value will
be tested.
Meaning that this registry value will be checked to exist:
Key: HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\version
Name: Install
-
Nir Bar
Freelance Developer
Mail: nir@panel-sw.com
Web:
Is there Burn support to resolve an Engine Variable, which includes a Burn
Standard Variable, (which can be called from a C# mba prior to ApplyBegin)?
Example, given an InstallFolder variable set to a string like
[ProgramFiles6432Folder]\somefolder\ is there a way to resolve this so
that the full
13 matches
Mail list logo
