>From memory so this may not be 100% - Windows Installer evaluates
properties as true if they are set, and false if they are not. i.e.
setting MYFLAG=true on the command line will result in boolean condition
tests on MYFLAG returning true, but so will setting MYFLAG=false, as the
MYFLAG property wi
Hi,
I am using C# in VS2008 to access an MSI and delete some rows. I am
using the latest weekly WIX build, 3.5.0626. When I try to use the
View.Delete method I receive the InstallerException "Cursor in invalid
state". I've simplified the code and replicated the error with the
sample below:
and server? I'm not sure how
this would help me and what it has to do with not being able to get the
refreshed value of a property.
Buddell, James wrote:
>
> Have you added the property name to the SecureCustomProperties
Property?
>
> -Original Message-
> From: Saeed,
It could also be that you're setting the property to the string "1" and
testing for the numeric value 1. Try testing for "1" in your condition
instead.
Cheers,
James
-Original Message-
From: Richard [mailto:[EMAIL PROTECTED]
Sent: 06 November 2008 18:22
To: General discussion for Windows
Have you added the property name to the SecureCustomProperties Property?
-Original Message-
From: Saeed, Rehan [mailto:[EMAIL PROTECTED]
Sent: 06 November 2008 15:48
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] DTF Property updated by RadioButton not correctly
retrieved by Cus
The max value of the MSI ProductVersion would be 255.255.65535. In hex
255 would be FF, and 65535 would be . The Version field is probably
just hex conversions of the three relevant ProductVersion fields
appended together.
Seems to hold true for a sample app I have installed: DisplayVersion
3.
Take a look at the duplicate file table, MSI.chm covers it well.
Cheers,
James
-Original Message-
From: Pally Sandher [mailto:[EMAIL PROTECTED]
Sent: 03 November 2008 12:27
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Installing the same files in 2 direc
remove all
per-user installations?
Any hints will be much appreciated.
Thanks,
Hyung
Buddell, James wrote:
>
> Tidying up per-user installs is almost impossible, especially when
> some users might have left your business so their accounts are no
> longer accessible. I try not t
Tidying up per-user installs is almost impossible, especially when some
users might have left your business so their accounts are no longer
accessible. I try not to use it, but there's always MSIZap...
-Original Message-
From: Ian Elliott (Excell Data Corporation)
[mailto:[EMAIL PROTECTED
The samples are in the WIX source download, but not in the compiled one.
Cheers,
James
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of DEÃK JAHN, Gábor
Sent: 14 September 2008 15:03
To: General discussion for Windows Installer XML toolset.
Subject: [Wi
The shortcut points to the keypath of the component.
Just use the component of your main shortcut, that is always either
installed or uninstalled and that the app won't function without, or if
you like you can set multiple RemoveFile entries for each shortcut
Component. So long as the FileName col
Take a look at the SecureCustomProperties Property too.
Cheers,
James
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian
Simoneau
Sent: 05 September 2008 16:22
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Property
Can you populate your Upgrade Table and check the property value
specified there and populated by FindRelatedProducts? i.e. UPGRADEFOUND
from "Preventing an Old Package from Installing Over a Newer Version" in
MSI.CHM.
Cheers,
James
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMA
During an installation the RemoveExistingProducts action would handle
these uninstalls for you, but (from the RemoveExistingProducts
documentation)...
"The installer only runs the RemoveExistingProducts action the first
time it installs a product. It does not run the action during a
maintenance in
s I would like, which forced me to go down a different
> path.
>
> I do appreciate the suggestion about the type 35 CA, I will check that
> out and look into a CA for the group membership.
>
> Thanks
>
> David Aragon
>
>
>
> On Aug 26, 2008, at Aug 26 @ 9:35 AM, B
Can you put the date and time in the log file name? Or use /l*v+ on the command
line to append to the old log file?
Cheers,
James
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: 29 August 2008 14:07
To: wix-users@lists.sourceforg
Have you applied the policy to both HKLM and HKCU? I *think* that one
needs to go in both.
Cheers,
James
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jon Seanor
Sent: 28 August 2008 16:45
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Strang
You could try messing around with the order of the actions in your
installexecute sequence, but you'll just cause yourself validation
problems, as well as uninstall and rollback issues so that's not a good
course of action.
You have a CA anyway to use the files so why not just delete them in
that
If you're moving the files somewhere else you could use the move files
table, or just install them straight to their final location. The remove
files action is run before install files, so you can't use that.
You could also do it in your CA if you really have to.
Cheers,
James
-Original Mess
Not an answer to your whole question, but if you don't set the files as
keypaths of their components then the MSI won't heal when they're
missing.
Cheers,
James
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Krzysztof
Kozmic
Sent: 28 August 2008 10:50
To
How about doing an administrative installation? Then clients can do an
install that will run from source. Or do you not have clients for this
app?
A type 35 CA will let you set INSTALLDIR as required.
For the group membership check, an early CA (about the same time in the
sequence as AppSearch) t
Yes, take a look at the ISScript MSIs, they don't have a RegisterProduct
action which allows them to achieve the behaviour that you're after.
Cheers,
James
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jay Thaler
Sent: 20 August 2008 02:57
To: wix-user
Yes, you can do this using the ServiceControl Table. Set the
msidbServiceControlEventUninstallDelete flag. You may also need to use
msidbServiceControlEventUninstallStop.
See http://msdn.microsoft.com/en-us/library/aa371634(VS.85).aspx.
Cheers,
James
-Original Message-
From: [EMAIL PROTE
Hi Chris,
I just wanted to give a different perspective here too. I am an
application repackager rather than a software developer, and so I see
this from the point of view of large corporates who may want to deploy
your software automatically, i.e. your customers!
It's fine to have a requirement
process for managed code and the communication with it.
-Jason-
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Buddell,
James
Sent: Friday, August 08, 2008 5:43 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] DTF and .NET
You could also use Active Setup to run a tidy-up script for each user.
Take a look at http://www.appdeploy.com/articles/activesetup.asp, the
structure you'd use is the same though you won't be able to use an MSI
command line as the MSI is already uninstalled.
Cheers,
James
-Original Message--
http://robmensching.com/blog/archive/2007/04/19.aspx
The above blog tells us that one of the reasons not to use managed code
for DLL CAs is because .NET Framework version 1.1 is always loaded on
Windows Server 2003 regardless of the code's required .NET version. I
know that DTF addresses the stick
You have to use the CustomActionData Property, see
http://msdn.microsoft.com/en-us/library/2w2fhwzz(VS.80).aspx. Have a
search online for the property name to find more detail and examples.
Cheers,
James
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Be
ject in DTF?
Regards
Simon Powell
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: 31 July 2008 16:49
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] DTF FeatureParent
Buddell, James wrote:
> I'm
I've struggled with this recently as well (on XP and in Orca rather than
Light) as we were piloting running without admin rights. It turned out
to be caused not by the rights themselves but by the MSI policies. Since
validating involves launching a session object, and since we had
DisableMSI set to
Hi all,
I'm using DTF but cannot find an implementation of the
Installer.FeatureParent property. I can work around this by opening a
session on the product and querying the Feature table, but would rather
not as starting the session is very slow and I am enumerating a number
of apps.
I can see th
31 matches
Mail list logo
