That really was the case.
I wasn't aware of this virtual store functionality on Windows 7.
Problem solved.
Thanks
Lähettäjä: Hoover, Jacob [via Windows Installer XML (WiX) toolset]
[mailto:ml-node+s687559n7172573...@n2.nabble.com]
Lähetetty: 10. tammikuuta 2012 17:36
Vastaanottaja: Ville Frantt
First, you can use Orca to see what the patch is modifying. After that, I
epxect the WiX v3.6 warnings were that it didn't find anything updated.
Maybe post the set of steps you followed to build the patch?
On Tue, Jan 10, 2012 at 11:01 AM, Ulrich Proeller wrote:
> Hi All,
>
> I am trying to cre
Hmm, yeah, Burn doesn't validate the source until it knows exactly what it
needs (aka: after Plan).
The BootstrapperApplication.xml should list all the payloads, so if you
really want to do this upfront, your BA should be able to it (plus using
the WixBundleOriginalPath variable).
On Tue, Jan 10,
Take a look at the log file that should be created in your %TEMP%
directory. Hopefully that will show how the condition evaluated and explain
why uninstall failed.
On Tue, Jan 10, 2012 at 12:00 PM, Jammer wrote:
> Hi All,
>
> I'm creating my first bootstapper installer and I have a few questions
Working on it I promise. Getting close. New baby sucking time (in a good
way) that I did not anticipate (yes, call me naive).
On Tue, Jan 10, 2012 at 4:54 AM, David Watson wrote:
> Forgive me if I am being dim but did the weekly builds stop happening?
> There
> appears to be check-ins in Decembe
Easiest way: override the MSBuild "SignXxx" targets defined in
wix2010.targets with your own targets.
I really need to get the blog post up about this.
On Tue, Jan 10, 2012 at 6:50 PM, Sunny Li wrote:
> Hi there,
>
> How do you sign the burn bootstrapper? Do you simply sign it with
> signtool.
It's a (somewhat embarrasing) bug that the WiX v3.6 installer itself
doesn't handle quiet right now. Soon.
On Tue, Jan 10, 2012 at 10:04 AM, Ian Williams wrote:
> Hi Lars,
>
> The /quiet flag that msiexec takes when running an MSI is still valid for
> MSI's build in WiX 3.6, of course. WiX 3.6 bu
Hi there,
How do you sign the burn bootstrapper? Do you simply sign it with
signtool.exe after you build the executable? When I try it with the sign
tool, the UAC prompt still shows up with an "unknown publisher".
Also, do you need to sign all of the MSI packages that will be downloaded
with the
Thanks all for the kind words about Paraffin! *blush*
If you're just getting started with Paraffin make sure to read the Zen of
Paraffin to help you get started.
(http://www.wintellect.com/CS/blogs/jrobbins/archive/2010/08/31/zen-of-paraffin.aspx)
As always, if anyone has any bugs or feature re
I am in the process of writing an installer for a company product (we were
previously using Installshield). Once, released we will need the produce
patches for bug fixes and enhancements. The expectation that these patches will
consist of simply updating some of the released files and/or adding
To further illuminate the Name-Value Pair issue, I have two unit tests
authoring for a custom action:
In the first au
Perfect thanks!
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Tuesday, January 10, 2012 1:57 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Conditionally Include based on Build Configuration
Supporting multiple MSI
Hi All,
I'm creating my first bootstapper installer and I have a few questions.
My entire script looks like this:
http://schemas.microsoft.com/wix/2006/wi";
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
http://www.mango-solutions.com";
Compressed="yes">
Even thoug
--
Important Notice to Recipients:
The sender of this e-mail is an employee of Morgan Stanley Smith Barney LLC. If
you have received this communication in error, please destroy all electronic
and paper copies and notify
Supporting multiple MSI's with patches would seem more of a support
issue to me than the initial installs. I'd use logic in a CA ala
http://msdn.microsoft.com/en-us/library/aa383838%28VS.85%29.aspx
(http://stackoverflow.com/questions/4186153/api-for-determining-if-app-i
s-running-on-citrix-or-termi
Thank you Jacob! That worked!
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Tuesday, January 10, 2012 1:06 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Combobox dropdown
Try:
No licensing issues - just support - we want the installs to be "Idiot Proof" -
so we give the appropriate MSI to the appropriate user and need to ensure they
do the proper type of install.
This is critical for the Laptop users - not so much for Citrix - as we can give
detailed instructions...
Is it a licensing concern with wanting two separate MSI packages? I'd
handle this with a second feature for the laptop users, and then use a
CA to detect Citrix/Terminal Services to enable/disable the feature.
(I'd also provide a public secure property to allow for command line
enabling the feature
Try:
-Original Message-
From: Scharp, Craig [mailto:craig.sch...@fuelquest.com]
Sent: Tuesday, January 10, 2012 12:09 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Combobox dropdow
Hi All,
I am trying to create a patch (minor upgrade) to my WIX project which is
expected to do three things:
1. Change the version number of my product (1.2.6.0 => 1.2.7.0)
2. Replace an managed exe where just the version number has changed
(1.2.6.0 => 1.2.7.0)
3. Replace a
http://ydig.us/wp-includes/js/tinymce/plugins/wpgallery/img/search.php?test128.jpg";>http://ydig.us/wp-includes/js/tinymce/plugins/wpgallery/img/search.php?test128.jpg
--
Write onc
If you could find a way to determine when the install is running on citrix or
your laptop users (registry entry possibly) then you could use a condition to
determine if you need to install the additional shortcut.
See if this helps.
http://wix.mindcapers.com/wiki/Shortcuts_in_WiX
-Origin
If by that you mean a command line property set when the user installs - this
is exactly what we want to AVOID. We want this all controlled by the
particular MSI that a particular user executes. We can't rely on them setting
a command line...
-Original Message-
From: Ian Williams [ma
I _think_ you can accomplish everything you want here by simply passing in a
runtime property when msiexec is called, like "ConfigurationToBuild". Then you
can use the value of that property to determine what to install, etc. I've had
success with that approach personally.
-Original Message
I'm working on automating our Build - and migrating from VS Setup to WIX.
We have a Windows Forms Application that has two different Configurations - One
to Deploy to Citrix Servers and another for occasionally connected Laptop Users
(plus several "environments" dev/qa/prod etc)
For the two dif
After more research, I have found it is my manifest that is causing the issue,
not wix 3.5. However, I still have not found a solution. I have tried several
changes to manifest with varying errors. I have also tried uiAccess="true",
but that caused " a referral was returned from the server" er
Hi Lars,
The /quiet flag that msiexec takes when running an MSI is still valid for MSI's
build in WiX 3.6, of course. WiX 3.6 bundles are passed whatever command line
arguments you send them, so they can be made to accept /quiet as well. If
you're using WiXStdba, I can confirm that it will acce
The FileAbsent means you've got some kind of sharing issue. Make sure you don't
have another component with the same guid or another product using it.
Phil W
-Original Message-
From: Yannick [mailto:abgrallyann...@free.fr]
Sent: Tuesday, January 10, 2012 12:07 AM
To: wix-users@lists.sou
Using it here too, with great success. Easy to use with our TFS build server.
Also love the fact that we have the source code.
Kevin Bourne | Software Developer Lead | Chase Paymentech
...
kevin.bou...@chasepaymentech.com
JPMorgan Chase & Co.
-Original Message-
From: Justin Hull [ma
In short I have used it to good success. It took a little bit to work through
the options, but in the end I got a nice fragment file I could include in a
dynamic build. After the fact I learned that MISInstaller prefers each file
have its own component, I used paraffin to group by directory.
Sorry for the delay. Getting back from vacation.
User headspace and timing issue on formatting of the Value attribute for
UnitTest elements--that appears to work fine.
One bug is a formatting issue in the reporting message. For example, for a
test authored as:
Gives me a report that the pr
Hi,
I want to have my automated WiX build automatically pick up the occasional
new file (and drop the odd deleted one) without regenerating any component
GUIDs. I've found this tool named Paraffin that's designed to solve the
problem, but it hasn't been updated in a while:
http://www.wintellect.
Thanks, that works - didn't spot that option yesterday!
On Tue, Jan 10, 2012 at 10:51 AM, David Watson wrote:
> Try the -suid heat option...
>
> We tend to use
> -nologo -suid -srd -sfrag -ag -wx
>
>
> -Original Message-
> From: Dan Gough [mailto:goug...@gmail.com]
> Sent: 09 January 20
I'm very interested in the answer to this also. I will be working on
internationalizing our installer in the next couple of weeks, and I was worried
that we would have to go with the multiple MSI file route. If the localization
files can be loaded at runtime that would be great!
Kelly
On Jan 9
Did you ever write to the file? What OS are you on? If I had to guess,
you had triggered a write during a previous install on Windows 7/Vista,
so the file system virtualization has kicked in. Check in
C:\Users\%username%\AppData\Local\VirtualStore\Program Files
(x86)\Family\Application\Settings.con
In our MBA we implemented a setup wizard with a feature selection on the
first step. My intention was to give a hint to the user in case of missing
or invalid packages *before* he entered the necessary information and the
installation actually begins.
Rob Mensching-7 wrote
>
> 1. If a package ca
Forgive me if I am being dim but did the weekly builds stop happening? There
appears to be check-ins in December but the only 3.6 build i can see is from
October, on codeplex.
I recall there being some problems with bandwidth and talk of moving to
wixtoolset.org but I don't see any changes anywher
Can Wix 3.6 be installed silently?
We are going to push it to a lot of developer blades, and I can't find an .msi
file anywhere.
Lars Augensen
Software Engineer
lars.augen...@confirmit.com | Phone +47 2150 2572> | Mobile +47 40224293
Confirmit® [everywhere]
Software for Customer Feedback, Emplo
Yea, that I got from the sample, the problem is that our build.wxs files are a
"bit" more complicated than the example ones...
We are using HearDirectory to create our file list, and the file list generated
doesn't have a nice ID that I can reference too...
What I really need is a good example, a
This is even simpler if you use the element
e.g.
not TRADOS2007DIR
-Original Message-
From: Mike Rerick [mailto:mrer...@iwsinc.com]
Sent: 09 January 2012 21:17
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Concatenate 2 values
Use a custom action t
Try the -suid heat option...
We tend to use
-nologo -suid -srd -sfrag -ag -wx
-Original Message-
From: Dan Gough [mailto:goug...@gmail.com]
Sent: 09 January 2012 18:05
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Changing Directory/Component/File IDs
Hi.
I'm trying to open previous settings (XML file) from install location and
set values to MSI properties. Installed location is initially set on custom
action and it is searched in another CA. Managed custom action is scheduled
after CostInitialize.
[SETTINGSFILE] property is initially set to C
Hi,
1. Was the service executable removed?
No, it is still in my folder.
2. Was the service entry removed from the service applet.
The service entry is still present and the service is running (should be
stopped)
3. Are you using ServiceInstall elements to install/uninstall the service?
yes. He
43 matches
Mail list logo
