I ran into the same issue. Everytime the msi is built its check sum is
indeed different and the bundle stores this information. What you can do
is skip the msi build step unless it has actually changed and copy it the
desired location so that when the bundle builds it picks the same msi
everytime
You can easily use a HeatDirectory task to achieve what you want. Basically
it will walk the directory tree and create a wix file that you can use in
your project.
On Wed, Apr 10, 2013 at 2:44 AM, Gareth Williams
gar...@trinitydigital.co.uk wrote:
Hello All.
Considering using WiX to build
the same guid in the face of the
same file for 'upgrades' etc.?
Seems I have a lot more learning to do.
Thanks
Best regards
Mr. Gareth Williams
Trinity Digital
-Original Message-
From: ptr [mailto:ptrajku...@gmail.com]
Sent: 10 April 2013 13:09
To: General discussion for Windows
hey all
I have a custom managed boostrapper that installs .NET4 framework as a
prereq. Let's call this OurProductWix.exe.
Now we have old installshied based installers , let's call it
OurProductSheild.exe
Now consider this workflow
1) User has OurProductShield.exe already installed.
2) User
is complete to cause rollback.
On Wed, Apr 10, 2013 at 2:41 PM, ptr ptrajku...@gmail.com wrote:
hey all
I have a custom managed boostrapper that installs .NET4 framework as a
prereq. Let's call this OurProductWix.exe.
Now we have old installshied based installers , let's call
hey all
In my managed bootstrapper I can get access to command line parameters via
Command.GetCommandLineArgs().
ParseCommandLine@src\burn\engine\core.cpp seems to parse lot of burn
standard command line parameters and pass the rest to my BA. Is this a
supported scenario ?
hey all
We upgraded all our installers to use WIX boostrapper instead of
InstallShield generated boostrappers. Can the wix relatedbundle feature be
used to detect and uninstall our old installsheild products ? If not, Can
somebody recommend how to achieve the same?
Thanks in advance
Raj
hey all
When you include a Msipackage in boostrapper you can specify cache and
cacheid. The documenation is sparse on what these attribtues do ? What is
the recommended value for these attributes ?
Thanks
Raj
--
In my investigation I have found that if you have seldom changing
thirdparty components... give them their own msi's and tie down there
version/product code. The boostrapper that the thirdparty msi of the
required version is already installed and doesn't seem to download or
install it.
-Raj
I had the same issue. The cause seem to be that for a regular WPF
application there is always an Application.Current
The boostrapper kinda fakes it so there is no application.Current and as a
consequence you cannot have any application level resources for a managed
boostrapper. What I ended up
Just a wild guess but is it possible that custom action is not being run as
user who is doing an install.
On Mon, Apr 8, 2013 at 12:01 PM, Miller, Nick (GE Intelligent Platforms)
nick.mil...@ge.com wrote:
Hi,
I have a Wix file where I'm using the SqlDatabase element to create a
database.
Thanks Rob, But what does these variables do ?
thanks
Raj
On Mon, Apr 8, 2013 at 1:28 PM, Rob Mensching r...@robmensching.com wrote:
Recommended to leave them blank and let the toolset pick them for you.
On Mon, Apr 8, 2013 at 6:17 AM, ptr ptrajku...@gmail.com wrote:
hey all
When
I think if you call Bootstrapper.Engine.FormatString() it seems to evaluate
the variable
So if you have something like
Variable Name='MyInstallFolder'
Type='string'
Persisted='yes'
Value='[ProgramFiles6432Folder]Company\$(var.Current.ProductShortName)' /
and you pass
Website: www.LiveTechnology.com
-Original Message-
From: ptr [mailto:ptrajku...@gmail.com]
Sent: Monday, April 08, 2013 2:59 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Visual Styles in Wix BA
I had the same issue
: www.LiveTechnology.com
-Original Message-
From: ptr [mailto:ptrajku...@gmail.com]
Sent: Monday, April 08, 2013 5:02 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Visual Styles in Wix BA
If I understand your problem correctly this has nothing to external
payload
I have my MsiPackage as
MsiPackage
SourceFile=$(var.Anark.MsiOutputFolder)\FLS$(var.Platform).msi
Id=CoreFloatingLicenseServerPackageId$(var.Platform)
Cache=yes
Visible=no
Vital=yes
MsiProperty
Util RegistrySearch has an attribute Winb64 that seems to be no by default.
If this is set to Yes, Would it mean it would look in the 32bit registry
on 32bit OS and 64bit registry on 64bit OS ?
The reason I am seeking some clarification is become some other attributes
like these seem to be have
Hi
I just tried this simple project. Basically I just manually edited the
wixproj and simply added OutputName override in the debug configuration.
Now when I open this project and build the debug configuration the output
is simplemsidebug.msi and in release the output is simplemsi.msi
-Raj
is completely separate and is not affected by the MSI build.
On Fri, Apr 5, 2013 at 5:09 AM, ptr ptrajku...@gmail.com wrote:
Util RegistrySearch has an attribute Winb64 that seems to be no by
default.
If this is set to Yes, Would it mean it would look in the 32bit registry
on 32bit OS and 64bit
is explicit. If you say Win64='yes' then the
search is 64-bit and vice versa. You can ignore the fact that the Burn
engine is 32-bit. It matters none.
On Fri, Apr 5, 2013 at 6:59 AM, ptr ptrajku...@gmail.com wrote:
Thanks Rob.. I just wanted to clarify it because the documentation seems
out
hey all
I have a computer on which a msi installs and uninstall correctly. But
when done through the bootstrapper it complains that a higher version is
already installed.
The only thing is the bootstrapper is marked as version 4.1.95.8879 and the
msi is marked as version 4.1.8421. I am not
Please ignore this email. I somehow cut pasted the same upgrade code to two
different msi's in the bootstrapper
Thanks
Raj
On Fri, Apr 5, 2013 at 5:29 PM, ptr ptrajku...@gmail.com wrote:
hey all
I have a computer on which a msi installs and uninstall correctly. But
when done through
I had to do something similar in our build because the MSI names needed the
version number. The way I accomplished this is
In the wixproj I changed the OutputName to
OutputNameMyMsi$(OutputSuffix)/OutputName
And when I build the msi using msbuild I just pass and OutputSuffix like so
hey all
The ProductVersion
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370859(v=vs.85).aspx
msi documentation talks
about a 3 digit version number. I have been assigning Wix XML elment
Version@Product a four digit .net Version. We are currently supporting
only major upgrades so
if
write
Upgrade when the version is lower but I don't know that anyone does that.
On Wed, Apr 3, 2013 at 9:39 AM, ptr ptrajku...@gmail.com wrote:
hey all
The ProductVersion
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370859(v=vs.85).aspx
msi documentation talks
about
hey all
I have a bundle B.exe that installs NET4.exe , VS2010CRT.msi ,
OurProduct.msi. The bundle is compressed and embeds all the packages.
NET4.msi being the .NET 4 full framework
VS2010CRT.msi being VS2010 CRT runtimes
OurProduct.msi being all the assemblies that we develop inhouse.
We
hey all
I modelled my custom bootstrapper based on a example found on the web.
Namely
http://bryanpjohnston.com/2012/09/28/custom-wix-managed-bootstrapper-application/
The example uses Microsoft.Deployment.WindowsInstaller.dll as a PayLoad. Is
this really needed for a managed boostrapper ?
hey all
I am trying to add a condition to my bundle and it doesn't seem to work
I have something like this in my bundle
Bundle Name=XXX
Version=XXX
Manufacturer=XXX
IconSourceFile=XXX
SplashScreenSourceFile=XXX
UpgradeCode=XXX
, Mar 29, 2013 at 8:51 AM, Rob Mensching r...@robmensching.com wrote:
Yes, a custom BA would need to evaluate the conditions. wixstdba has a
function called EvaluateConditions() that does that.
On Fri, Mar 29, 2013 at 7:35 AM, ptr ptrajku...@gmail.com wrote:
hey all
I am trying to add
hey all
I have successfully built a custom managed boostrapper. My bootstrapper
chains the following packages
1) Embedded .NET 4 framework as EXEPackage
2) A microsoft prereq msi ( VS2005,2008,2010 runtimes) around 8MB
3) Some third party binaries we depend on another msi around 200 MB
4) An
You can use the [ComputerName] property
On Tue, Mar 26, 2013 at 7:09 AM, Pally Sandher pally.sand...@iesve.comwrote:
http://msdn.microsoft.com/en-gb/library/windows/desktop/aa368009.aspx
Found under Operating System Properties in the Property Reference at
Hey all
Does anybody know when is Display.Embedded and Display.Passive used for
bootstrapper ? Is this documented somewhere ?
Thanks
raj
--
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before
hey all
I am trying to handle all possible error scenarios for my custom
bootstrapper. Even if main executable I have installed is running,
Bootstrapper.ExecuteFilesInUse is never invoked. How can one test this
scenario ?
Thanks
raj
hey all
I just thought I would share with everyone something I that I wrote that I
find saves me lot of time. If you are developing a customer .NET
bootstrapper you periodically need to attach and debug your
BootstrapperApplication.
One can easily solve this by having a line
hey all
I am using heat to harvest a directory like so
HeatDirectory
Directory=..\..\..\Solution\bin\Connectors
OutputFile=Generated\ConnectorComponents.wxs
PreprocessorVariable=var.BuildOutputConnectorFolder
ComponentGroupName=Components.Connectors
hey all
Is making a 64bit boot strapper supported by wix 3.7. I am trying to make
a 64bit custom bootstrapper and i get the following error in the
installation log
[1120:17E8][2013-01-11T14:27:10]i000: Loading managed bootstrapper
application.
[1120:17E8][2013-01-11T14:27:10]e000: Error
conditions to decide which subset of
installers to run.
Jacob
-Original Message-
From: ptr [mailto:ptrajku...@gmail.com]
Sent: Friday, January 11, 2013 3:47 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] 64bit bootstrapper using wix
hey all
Is making a 64bit boot
37 matches
Mail list logo
