Hi,
I want to do that the component "X0" is installed when I select both "F0" and
"F1" on UI or command-line parameters.
When is it evaluated a condition of component ? Something wrong ?
wix code:
Thanks,
Hello,
thanks for the advice, but the messagebox was just an example for a more
complex dialog that would be displayed at this moment.
For example:
- LoadLibrary to get a handle
- Call ShowMyC++dialog with the handle.
The main idea is to show a dialog during installation that is also used later
Thanks.
On Wed, Dec 16, 2009 at 12:33 AM, Sebastian Brand (Instyler Software)
wrote:
> There is a wixui_zh-cn.wxl for Wix2, but not for Wix3.
> You could use a converter like
> http://www.khngai.com/chinese/tools/convert.php
>
>
> Best regards,
> Sebastian Brand
>
> Deployment consultant
> E-Mail
Hi,
I have generated a bootstrap for VSTO runtime 3.0 pre-requisite using
GenerateBootstrapper in my after build and it is working fine. However it is
generating:
1. A VSTOR30 folder containing vstor30.exe runtime.
2. The MSI file.
3. The setup.exe.
Clicking on setup.exe installs VSTO runtime (if
Hello WiX community,
I have a simple question, just to make sure.
When creating a patch, should I always change Patch/Media/@Id attribute
between patches?
For instance, I have Patch1.wxs, which is to be applied to RTM
(baseline), and Patch2.wxs, which is to be applied to RTM+Patch1. In
Patch1.wxs
nandini sa wrote:
> I have generated a bootstrap for VSTO runtime 3.0 pre-requisite using
> GenerateBootstrapper in my after build and it is working fine. However it is
> generating:
>
That's the .NET Framework bootstrapper, not WiX. You might check out a
.NET Framework newsgroups/mailing list
Markus Gaugusch wrote:
> So, since I can't read out the old value, I thought about skipping the
> component (see below) during upgrade. The entries would not be written and
> everything would be fine.
>
Try a component condition of NOT UPGRADINGPRODUCTCODE.
--
sig://boB
http://joyofsetup.co
Genius! Thank you :)
Now, is this behaviour a bug in WiX which I ought to report? It seems
really odd that it doesn't "know" that CommonFilesFolder is
intrinsically 32 bit.
--
Cheers,
John
On 16/12/2009 00:59, Sascha Beaumont wrote:
> I think I've found a solution... wrapping the 32-bit Commo
akihiro.shib...@jp.yokogawa.com wrote:
> I want to do that the component "X0" is installed when I select both "F0"
> and "F1" on UI or command-line parameters.
> When is it evaluated a condition of component ? Something wrong ?
>
http://www.joyofsetup.com/2007/05/30/feature-conditions-and
That's an interesting idea, I assumed that the windows installer more or less
kept track of an original install for repairs, uninstalls, patches, and
upgrades which may have been the error in my approach. My installer does
not contain a registry key for an installation path. Although I can easil
Theres an answer in Peter Marcu's blog at
http://blogs.msdn.com/pmarcu/archive/2007/06/28/sample-patch.aspx#879001
6
which says the ID has to be above the last sequence number of the
*baseline* you are targetting, so it sounds like you are doing it right.
-Original Message-
From: Yan Skly
I'm trying to add a control to a custom dialog in my WIX UI to collect
various UNC paths the user wishes our software to monitor. Based on the
documentation it looked like a standard control of type="Edit" and
multiline="yes" would work.
However, when I implemented this dialog I discove
Our installer needs Admin right to run. So a "Standard user" has to run the
installer "run as Admin". On the final page of the installer, we have a "Launch
application" option. So the user can check that option and launch the
application. Our application will ask a license key. The user inputs t
Has anyone any knowledge on what a component state of -7 actually is or how
it gets set to that value?
MSI (s) (F8:DC) [13:01:44:431]: Executing op:
ComponentRegister(ComponentId={12345678-1234-1234-1234-123456789012},,State=-7,,Disk=1,SharedDllRefCount=0,BinaryType=0)
Thanks.
--
View this mess
Looks like it's more of a bug with the .cub files that contain the ICE
tests to run - so you'd want to report it to the Windows Installer
team, rather than the WiX team. Someone else on this list might be
able to point you in the right direction to contact them...
On Thu, Dec 17, 2009 at 1:52 AM,
If anything, it's a limitation of Windows Installer - not WiX.
WiX just writes control/dialog entries in the MSI database, Windows
Installer implements the actual UI. See
http://msdn.microsoft.com/en-us/library/aa368342(VS.85).aspx for
documentation on the control itself.
Sascha
On Thu, Dec 17,
Check out http://blogs.msdn.com/rflaming/archive/2006/09/21/765665.aspx
You can probably use MSIREALADMINDETECTION to make the AdminUser
property behave as you require.
Sascha
On Thu, Dec 17, 2009 at 6:08 AM, little.forest wrote:
> Our installer needs Admin right to run. So a "Standard user"
Hi All,
What is the correct syntax for checking to see if a component is
currently installed on a system during an uninstall. I want to execute
a custom action if the component in question is not installed.
I thought it was something like:
&ComponentName=2
That doesn't seem to be c
Hi
& is for features not components
I think you want
?component=2
or possiblye NOT ?component=3 (which would cover all of the different not
installed situations).
Regards
Michael
From: Amy Rosewater [arosewa...@spectrumhr.com]
Sent: Thursday, 17 De
That seems to be INSTALLSTATE_NOTUSED, commented in msi.h as "component
disabled", but that just begs the question of what "not used" or "disabled"
means, but maybe it makes sense if you know more about that component. Is the
component marked as transitive?
Phil Wilson
-Original Message
I've got a property that a custom action will expect to exist if a
specific directory is supposed to be deleted upon uninstall.
I'd like this property (call it UNINSTALL_SITE) to be set under either
of two conditions: a) I'm uninstalling, not upgrading, or b) I'm
upgrading, but the version number
..and a couple of things that don't make sense to me:
1. There are always likely to be cases (admin install, over the shoulder, group
policy) where somebody else is doing the install on behalf of a user. So what
seems odd to me is Brian's comment that the key is in the wrong place because
it's
Thanks Sascha.
I'll look into it.
From: Sascha Beaumont
To: General discussion for Windows Installer XML toolset.
Sent: Wed, December 16, 2009 1:33:35 PM
Subject: Re: [WiX-users] How to launch application as Standard User while the
installer ran as Admin
C
Thanks Phil.
For #1, in the old version of our software, the license key was kept in a
common place. In this new version, it's changed. I agree with you for this
point. I'll talk to our team to put license key in a common place. It'll make
sense to put it in a common place as we support per-ma
GPO is Group Policy Object. I think that's the right acronym, but anyway larger
enterprises don't (for example) install Office on every system by going to each
one and installing it. They assign it via group policy and have it install in
admin mode even if users are not administrators. This kind
I agree with Phil here,
If your customer base is in the corporate world, having an "Enterprise
ready" installation is a must. One that can run with no user
interaction, be configured pre-install and pushed out via GPO/AD
(Group Policy Objects/Active Directory) so that the end user
(non-Admin) can
26 matches
Mail list logo
