Alright, done. Thank you!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Number-of-files-in-download-tp7579138p7579170.html
Sent from the wix-users mailing list archive at Nabble.com.
---
Hi,
I need to change the DisplayInternalUI at run time in BA. Unable to find the
DisplayInternalUI property in BA. Please, how to set the DisplayInternalUI
property in BA?
Thanks,
Kannan
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-MsiPacka
ok, thanks Rob!
On Wed, Jun 27, 2012 at 1:44 PM, Rob Mensching wrote:
> AppSearch is a perfectly valid thing to use for that.
> On Wed, Jun 27, 2012 at 1:21 PM, Bob Uva wrote:
>
> > I'm trying to use a modified version of Wix_FeatureTree dialog set. I
> want
> > to determine if my application i
Rob Mensching-7 wrote
>
> The wixstdba isn't designed to show the internal MSI UI. You'll probably
> want to make a custom BA that is designed to show the internal MSI UI.
>
Could you provide more detail about this? My simple test case sets
DisplayInternalUI="yes" for my MSI package that is bas
It seems that a Bundle Id is generated for every new build and that's why to
end up with multiple entries in ARP. We couldn't find any mechanism to set this
BundleId to a well-known GUID, is there any way to do this at build-time?
run-time?
> Date: Tue, 26 Jun 2012 14:07:32 -0500
> From: benben
Rob,
I have gotten a little further now. Using Model.Command.CommandLine, I now
get my command line arguments great, except that on Windows 7, when I start the
Bootstrap application, I always get "ignored" as an argument, even when none
are passed?!? XP works fine, but Windows 7 (x64 or x32)
Rob Mensching-7 wrote
>
> IIRC, there were bugs in WinSxS on Windows XP that did not handle
> replacing
> files in use well causing more reboots than necessary. Yay, Fusion!
>
I've replaced the VC90CRTx86 merge module with a bundle that runs the C++
redistributable. This works on XP without any
AppSearch is a perfectly valid thing to use for that.
On Wed, Jun 27, 2012 at 1:21 PM, Bob Uva wrote:
> I'm trying to use a modified version of Wix_FeatureTree dialog set. I want
> to determine if my application is already installed, and if it is, to read
> an xml file to retrieve a value from it
I'm trying to use a modified version of Wix_FeatureTree dialog set. I want
to determine if my application is already installed, and if it is, to read
an xml file to retrieve a value from it. If the app is not installed, I
want to bring up a different dialog on a Next button press.
Is there a stand
The WiX setup installs that stuff under C:\Program Files\MSBuild.
For example, I found the following in one of my .wixproj:
$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targets
$(MSBuildExtensionsPath)\Microsoft\WiX\v3.x\Wix.targets
The MSBuild documentation at
http://msdn.microsoft.com/en
Yes. The WiX toolset (wix36.exe or the old WiX v3.5 MSI) installs the
wix.targets and WixTasks.dll and other things appropriately so they "just
work". Or you could use the binaries.zip file like someone pointed out with
a link to the documentation how.
On Wed, Jun 27, 2012 at 12:43 PM, Dan Muller
Before reading this post i did do a search for msbuild and found it in my
.NET folders, and i have a copy of wix.target and wixtasks.dll, however they
are not actually from the wix installation but my sharpdevelop install. So
my question is, is there a wix.target and wixtasks.dll that is distribute
You'll have to proxy out to a 64-bit process.
On Wed, Jun 27, 2012 at 7:17 AM, Henning Krause wrote:
> Since I'm in the context of Burn, I can't call CAQuietExec. I'm not
> running in any MSI context. That comes later...
>
> Henning
>
> > -Original Message-
> > From: John Cooper [mailto:j
Hmm, doesn't look like that is possible. That's a bummer. Feel free to open
a bug. It's something we should support. Might do it by adding payload
information to the BootstrapperApplicationData.xml.
On Wed, Jun 27, 2012 at 5:36 AM, Miss Parker wrote:
> Hi,
>
> I need to display in my GUI the exac
Save the values you need in a persisted Variable *before* calling Apply().
When you come back after reboot, the values will still be there.
Basically, in Burn we fixed the "problem" that MSI does not store Property
values by allowing Variables to be persisted.
On Wed, Jun 27, 2012 at 6:57 AM, jh
You set DisplayInternalUI at build time.
On Tue, Jun 26, 2012 at 10:00 PM, Kannan24 wrote:
> Hi,
>
> I need to set the DisplayInternalUI value to "No" using BA.dll.
>
>
> SourceFile="D:\Work\Build\syncfusionessentialstudiosetup\EssentialStudioSetup\bin\Debug\EssentialStudioSetup.msi"
> Compress
MSbuild is installed with the dotnet framework so you won't need to
install SharpDevelop or VS. What you are getting is that msbuild can't
find the Wix targets and binaries.
For all my wix projects I redirect the wixproj files to point to a
directory that is checked into source control. That way t
If you have WiX installed on the computer, then you have everything you need,
even if Visual Studio is not installed. Give it a try. Let us know if you run
into any problems. Try to provide as much information as possible about your
configuration.
Edwin G. Castro
Software Developer - Staff
Dig
I don't know what I was doing but I had tried msbuild but must have supplied
the wrong argument. My problem now is that there is no w.target in my
C:\Program Files\Windows Installer XML v3.6\bin directory. It exists in my
sharp develop directory and I am sure I can find it in the visual studios
dir
Why don't you just use the msbuild commandline if you already have the
wixproj? Just call msbuild in the same directory to the sln or wixproj
and it will find it.
Richard Mayes
Blog: http://blog.slinkysoftware.com
Twitter: http://twitter.com/caveman_dick
On 27 June 2012 15:24, Dan Muller wrote
A wixproj is an msbuild file, so it should build directly from the command
line (msbuild blob.wixproj).
http://wix.sourceforge.net/manual-wix3/msbuild.htm
We check the whole solution into TFS and use TFS build to automate. Just add
the solution into the tfsbuild.proj
e.g.
If you use nant there
Is there a way to build an installer directly from a wixproj? The normal
method is to call candle on a wxs, then light on a wixobj, but in a project
with multiple source files and therefore multiple wixobjs, is there a way to
create the installer through the command line? What would be the process
Since I'm in the context of Burn, I can't call CAQuietExec. I'm not running in
any MSI context. That comes later...
Henning
> -Original Message-
> From: John Cooper [mailto:jocoo...@jackhenry.com]
> Sent: Wednesday, June 27, 2012 3:56 PM
> To: General discussion for Windows Installer XML
A property and a directory ID are both kinds of properties. You use NEWLOC1
as a directory ID and you write your directory structure so that the default
locations for the 2 properties are the IDs of their corresponding directories
in the tree:
-- default directory structure for INSTALLDIR
In my BA I have several packages and features. I decide which of these to
install by showing a UI that allows the user to select them individually.
If one of the packages requires an immediate reboot what is the recommended
way of persisting the plan for after reboot (I don't want to have the user
Hmmm. Generally, when I call applets I wrap them in C# or call them with
CAQuietExec[64] because of this issue. The trick is that there are two
powershell.exe's on a 64-bit system, and you get the 32-bit one by default.
You're probably going to have to find a way to force the 64-bit powershe
Maybe my question was poorly phrased.
I'm not running a custom action. My call to Get-WindowsFeature resides in a
Managed Bootstrapper application (aka Burn). I haven't found a way to start the
Bundle process as x64.
Kind regards,
Henning
> -Original Message-
> From: John Cooper [mailt
Thank you, I don't why but I was sure it should be 450.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/msi-execution-with-Windows-Installer-4-5-on-Windows-XP-fail-tp7579140p7579143.html
Sent from the wix-users mailing list archive at Nabble.com.
You have to call with a 64-bit entry point. If you're using CAQuietExec, you
need to be using CAQuietExec64 to execute in a 64-bit process.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.(r)
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo..
On 27/06/2012 13:59, beatman wrote:
> Now, the problem: I have created a few .msi packages with
> InstallerVersion="450" and tried to run them on a Windows XP SP2 machine
> with Windows Installer 4.5 correctly installed; unfortunately, the packages
> fail to execute, reporting the following error
>
Hi all,
this is my first post here, I'm a new (since a few months) WiX user from
Italy
Now, the problem: I have created a few .msi packages with
InstallerVersion="450" and tried to run them on a Windows XP SP2 machine
with Windows Installer 4.5 correctly installed; unfortunately, the packages
fai
Hi,
In my setup, I want to install 2 files say 'abc.txt' and 'efg.txt' in a
separate location other than the default install location (INSTALLDIR). This
separate location is also user-specified and I am storing the path in a
property called 'NEWLOC1'. I also need to do a 'FileShare' of this
Hi,
I need to display in my GUI the exact number of files that are being
downloaded. I can't seem to get the number of files, just the number of
packages so when an exe or msi has one or more payload file(s) I get the
incorrect number of files.
Is there any way to access number of files after pla
Hi,
Could you please give the more details about the rollback, ie which property
or method to call the rollback?
I tried to uninstall the installed setup. When i debug the source, the
LauchAction does not make uninstall action. I used the below code to
uninstall the setup.
SyncBA.Model.Engine.D
The documentation for CAQuietExec says you have to pass the command line in a
property called "QtExecCmdLine". I can't see any property with that name in
your source files. Have a look in the Wix help file and check that you're
following the instructions correctly.
-Original Message-
From:
I tried and reproduce the problem.I was follow the below steps.
1. I was installed new MSi version 1.0.0
2. I was implemented minor upgrade and MSI version is 1.1.0
3. Then I tried for major upgrade (version 4.1.0).
First 2 steps are working fine, but when i tried for 3 step its throw the
error.A
I tried and reproduce the problem.I was follow the below steps.
1. I was installed new MSi version 1.0.0
2. I was implemented minor upgrade and MSI version is 1.1.0
3. Then I tried for major upgrade (version 4.1.0).
First 2 steps are working fine, but when i tried for 3 step its throw the
error.A
I tried and reproduce the problem.I was follow the below steps.
1. I was installed new MSi version 1.0.0
2. I was implemented minor upgrade and MSI version is 1.1.0
3. Then I tried for major upgrade (version 4.1.0).
First 2 steps are working fine, but when i tried for 3 step its throw the
error.A
Any help will be appreciated.
Thanks,
Maksim
-Original Message-
From: maksim.vazhe...@emc.com [mailto:maksim.vazhe...@emc.com]
Sent: Monday, June 25, 2012 3:00 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] x86 & x64 vc runtime merge modules installation problem
Hi All,
Re
That isn't an error. It is telling you that the component won't be removed
because a different MSI on the computer has also installed that component, so
the component is still needed.
It may be from a previous failed upgrade. Can you reproduce this error on a
clean virtual machine ?
-Original
Hi,
I tried to install the major upgrade for my application. When its try
to uninstall the existing application its throw the error message like
"isallowing uninstallation of component:
{AA67D22F-62E9-4034-BD7D-7210A43050BD} since another client exists".
Then its try to install the changes, but t
http://wix.sourceforge.net/manual-wix3/run_program_after_install.htm
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland N
Hi,
as part of my managed bundle, I may need to activate certain Windows Features.
Since I'm targeting Windows 2008 R2 or later, I can safely use the
Add-WindowsFeature and Get-WindowsFeature cmdlets.
The Add-WindowsFeature would be called from a custom action. However, I want to
display a lis
I want to implement launch application on successful install only (and not
on repair or uninstall). Its an external application (say VLC media player).
How can write my custom action to do this?
--
Thanks and Regards,
Ravi Raj
--
44 matches
Mail list logo
