Winterop.dll is a 32-bit so your calling assemblies need to stay 32-bit not get
JIT'd to 64-bit.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: keith.doug...@stat
I also removed:
And it seems to work without running NetFx on a system that has Fx support.
But I need to test this more next week.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Passing-Variables-from-C-custom-BA-to-WIX-tp7596113p7596194.htm
When I say that it 'worked' I mean on a Windows 8 x64, with build in netfx4x
support, the mba runs and NetFx40 setup is not launched. On Windows 7 x6x
with no NetFx support installed, the mba prereq dialog prompts the user to
allow NetFx to be installed, then it is installed and my mba is then
lau
In regard to the above discussion about your mba code, I was recently looking
at similar code in the wix src\Setup\WixBA\InstallViewModel.cs which has the
following code:
private void PlanPackageBegin(object sender,
PlanPackageBeginEventArgs e)
{
if
(WixBA.Model.Engine.
Update: this seems to happen because I was suddenly running a x64 version of
things - I had the project set to build as "AnyCPU".
This is very strange - I understand the library is 32 bit, but why should it
fail with the exception mentioned? That's pretty obscure.
(If it is clearer in > WiX 3.7
In the Bundle element, or a referenced fragment, use a Variable element and
use Override='yes'
or
For control logic in InstallCondition I prefer numeric, but if the variable
is to be passed to MsiProperty use a string.
In the mba, in OnDetectComplete (or wherever you want after Burn ini
Yeah. I have two cab files. Majority of the components are common so the
first cab file is a big one (48mb) where as the unique components are all
in cab 2. This is the reason why when the cabs are not signed the bundled
package correctly detects and treats it as a common cab between two MSIs.
I wi
A while ago I built some stuff to investigate properties of a burn bundle (EXE)
just in case they got lost when we built them, and also to harvest from others
(in case we have some bundles not built by us). As per the list's
recommendations, I added a reference to wix.dll and kept winterop.dll n
A search of the wix source gives this example:
.
InstallCondition='VS2013InstallFolder OR
VS2013WDExpressInstalled'
If for some reason the above approach is not useful,then:
In the Bindle declare a variable: (also from the wix source, but make it
'Overrideable='yes
Ok, I ran the debugger and to my surprise, this executes after U click the
InstallA button. I was thought this would run before any buttons were
clicked.
So, in trying to better understand how passing parameters work, what command
can I use to pass variables from my wpf application to my WIX scri
Did you try to use util:RegistrySearch for that issue?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-bundle-EXE-setting-property-tp7595178p7596182.html
Sent from the wix-users mailing list archive at Nabble.com.
---
Thanx Jacob for the hint about multiple msi's with only one cab.
I tried this approach today and it works fine.
After a few days of googling the solution I understand that it wasn't good idea
to use transformations :(
31.07.2014, 22:43, "Hoover, Jacob" :
> Instances are ugly... And to do the
1. The packages a bundle manages must be listed in the Chain of the Bundle
element. A bundle is an identity that manages a collection of packages. It's
not an arbitrary scripting engine to add and remove packages it doesn't know
anything about from the machine.
But if you are asking if bundle c
Are you including different files between the two builds? I would ensure the
common files are in one CAB and anything that is unique to x86 vs x64 in their
own CABS.
-Original Message-
From: Ashish Agarwal [mailto:ash...@mangoapps.com]
Sent: Friday, August 01, 2014 10:58 AM
To: General
I use the following in the setup project (this ofcourse happens once for
x64 and after that for x86)
http://timestamp.digicert.com"; "%(SignMsi.FullPath)""
/>
and the following in the bootstrapper project
http://timestamp.digicert.com"; "@(SignBundleEngine)""
/>
Are you building a solution? Solution variables are only available when
building a .sln.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: ferdi.oeztu...@accenture.c
Yes, and because of this burn is including the appropriate CABS. Are you using
the existing WiX build events to sign the MSI and CABS? I do believe the
events are timed such that MSBuild isn't going to trigger a rebuild if CAB
caching is enabled for the project.
-Original Message-
From
The checksum of the cabs before signing are the same but after signing they
become different.
Could this be because we are including the timestamps in the signature
using a timestamp server and as they get signed at slightly different
times(in the build process) the timestamps and as a result signa
Hi Phil,
I am trying to set a variable from a registry key within burn to be used in
a exepackage but can't seem to be able to do it, will what you mentioned
work for me? and if possible could you explain exactly on how to do that?
thank you
--
View this message in context:
http://windows
Hi Please remove me from the list
--
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the
I am experimenting with doing incremental minor patches followed by a "rollup"
minor patch. I am seeing an interesting behavior that I have a feeling is
expected but I would like to confirm.
So for example given the following patch sequence:
1.0.0
--1.0.1
1.0.2
---1.0.3
--1.0.4
Patch 1
Hi *
My build does not find the preprocessor variable var.SolutionName
Mobility.Platform.Windows.msm\Common\Module.wxi (4): Undefined preprocessor
variable '$(var.SolutionName)'.
Is it obsolete? Which solution-based variables are working?
Thank you very much and regards
Ferdi
1 Probably not only for transforms but also for other cases in general.
For example, run bundle with multiple(with different product codes) msi's more
than once to remove selected msi's from machine.
Can we do it now and keep a link in P&F?
2 Yeah. I just wanted to ask, why we don't have this m
23 matches
Mail list logo
