UPGRADINGPRODUCTCODE is set when you're being uninstalled during an
upgrade, so it sounds like the wrong condition.
Now I get it!!! the UPGRADINGPRODUCTCODE is NOT set when the product is
installed during an upgrade, only when uninstalled during an upgrade. THX!
I think you probably want
I have listbox in dialog:
Control Type=ListBox Property=SELECTEDGUICONFIG
Id=GUIConfigsList Width=280 Height=91 X=25 Y=70
ListBox Property=SELECTEDGUICONFIG
ListItem Text=Ничего не делать Value=0/
/ListBox
/Control
Custom action:
AFAIK for a small update (not minor upgrade) the version number of a
product must not change. The problem is: How to identify which version
(the original or the patched one) is installed now?
Maybe I misunderstood the contraint about version numbers, so I *may*
change the ProductVersion, but I
Rather weird, but I'll have to accept it -- Microsoft makes the rules.
;-)
Strange but true, it still is not working: I have now used NOTEPAD.exe
as source file (which obviously is in the right format and contains only
a single icon) and named the icon as .exe by using Icon id=my.exe
Hi,
I have a small setup that uses Embedded UI.
During uninstall the RMFilesInUse (I just start an executable that was
installed) message type gets to the embedded UI and I return
DialogResult.Retry . I would expect the unistall to try again and check if
the file is still in use. If it is
Hi,
Some of our customers are receiving the following error when trying to
upgrade our product. We are using WiX 3.0, and the upgrade is a major
upgrade.
the file: c:\users\[USER]\AppData\Local\Temp\IXP000.tmp\ is not a valid
installation package for the product
Does anyone have an idea what
Hi Bob,
Thank you for the advice - I will do that.
Thanks,
Simon
On Thu, Apr 8, 2010 at 11:11 PM, Bob Arnson b...@joyofsetup.com wrote:
On 4/8/2010 11:08 AM, Xmun wrote:
Is there a way to launch two applications?
WiX provides the custom actions to launch one; if you want two, you need
I think you should still list all the columns in brackets:
INSERT INTO `ListBox` (`Property`,`Order`,`Value`,`Text`)
VALUES ('SELECTEDGUICONFIG',2,'2','1.brf')
And, BTW, get a habit to wrap table and column names in `...`
For more information, see the MSI SQL syntax definition:
Hi all,
I am interested in doing only major upgrades in my installer, this is
why I have in the code for Product and Package the Id=*:
[code]
Product Id=* Name=$(var.ProductName)
Version=$(var.CurrentVersion) Language=1033
Manufacturer=$(var.CompanyName) UpgradeCode=$(var.UpgradeCode)
Package
Hi,
I did exactly as what you said but the message is not displayed. here is my
wxs file.
Property Id='APPFOUND' Value='false'
RegistrySearch Id=AppFound Root=HKLM
Key=SOFTWARE\Product\SETUP
Name=INSTALLPATH Type=raw/
/Property
Windows Installer only removes empty directories during install. If your
application dirties those directories during execution doesn't clean
up after itself, you'll need to do it yourself in your MSI or fix your
application to write to somewhere under CommonAppData or LocalAppData
(or some other
I forgot to say remove Value='false' from your Property, it's totally
unnecessary.
Palbinder Sandher
Software Deployment IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated
Windows Installer only uses the first 3 fields of version numbers so you
can change the 4th one as much as you'd like. See -
http://msdn.microsoft.com/en-us/library/aa370859.aspx
Personally I stay away from Small Updates for this reason. Minor
upgrades work just as well with no ambiguity.
Something like the following should work:
Property Id=OLDAPPLICATION
DirectorySearch Id=FindOldAppDir AssignToProperty=yes Depth=64
Path=[ProgramFilesFolder]
FileSearch Id=FindOldAppExe Name=oldapp.exe /
/DirectorySearch
/Property
DirectoryRef Id=ProgramFilesFolder
Directory
I did as you said and build msi but on installing i am getting the standard
error message like the below
Another version of this product is installed and installation of this
version cannot contnue etc.,
Is there a way to install. I am selecting install option on right click on
the msi.
Hello,
Does change of Package/@InstallPrivileges attribute to perMachine do
anything else than sets ALLUSERS to 1?
We have several deferred CustomActions with Impersonate attribute set to
no for elevated privileges and they seem to stop working on systems
with UAC.
Regards,
Jan
You're trying to install on a system which already has that product
installed.
Stop using the same product code for all your products if they are
different products.
Palbinder Sandher
Software Deployment IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
You sure? Still looks closed.
Thanks.
On Thu, Apr 8, 2010 at 5:13 PM, Bob Arnson b...@joyofsetup.com wrote:
On 4/8/2010 9:55 AM, Andy Clugston wrote:
Upgrading to the RTM (5419) did not help. Same issues.
I reopened the old bug. Please attach sample authoring and a verbose log
showing
Well like I said, it won't (the searching for the old application will
always happen). You can't do that without writing a Custom Action
Conditioning it appropriately as far as I know.
Replace the function of the DirectorySearch with a Custom Action which
returns the path to the directory
InstallPrivileges can only be set to either limited or elevated. I'm
assuming you mean InstallScope in which case yes that's all it does
according to the documentation -
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm
How are you elevating the MSI on UAC systems? Are you elevating
Any chance you might start thinking for yourself sometime soon?
Actually I do not understand why writing this. We are beginners with MSI
and WiX and have no clue what is there for free out of the box, and what
must be done with special tasks. Possibly there would be something that
can prevent
The question is, whether this holds true for Small Updates, since
Microsoft writes that ProductVersion must not be modified. So is it a
valid assumption (that holds true forever and not just by incident is at
the moment so) that the ignoring described in the link you posted also
is in place for
Thanks. MsiDatabaseOpenView() worked with
swprintf_s(lPath, LINSERT INTO `ListBox`
(`Property`,`Order`,`Value`,`Text`) VALUES ('SELECTEDGUICONFIG', %d, '%d',
'%s'), i++, i, sr.cFileName);
But now there is another problem with MsiViewExecute(). I call it after
MsiDatabaseOpenView():
Problem solving with this query:
swprintf_s(lPath, LINSERT INTO `ListBox`
(`Property`,`Order`,`Value`,`Text`) VALUES ('SELECTEDGUICONFIG', %d, '%d',
'%s') TEMPORARY, i++, i, sr.cFileName);
I added TEMPORARY at the end of the query and it work's
--
View this message in context:
Thank you for this information, it was very helpful.
-Original Message-
From: Rohit Sharma (SIDC) [mailto:rohit.sha...@symyx.com]
Sent: Donnerstag, 25. März 2010 14:02
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Beginner's Question: 32 Bit MSI
Right, that's because you can only add temporary records from inside the
custom action.
-- Yan
-Original Message-
From: vunder [mailto:vun...@bk.ru]
Sent: Friday, April 09, 2010 15:52
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Problems with adding items to ListBox
General discussion for Windows Installer XML toolset doesn't mean
e-mail here to ask for help on every little issue you get stuck on
without trying to figure it out for yourself. Maybe I'm being too
harsh
on yourself but there's a lot of people posting questions on here
which
can be answered
Thanks for your reply.
My concern here is to remove the application folder after uninstallation.
I am little worried because it is working fine on some machines. The folders
gets deleted after uninstallation.
Can some one have any idea how I can dig the issue ?
Thanks
- Jass
Hi all,
I would like to run a custom action that runs if the install fails. Has anyone
successfully done that? I f so, any suggestions would be great.
Thx, Craig
--
Download Intel#174; Parallel Studio Eval
Try the new
Hello,
When I try to harvest registration information from a 64 bit dll Heat
v3.0.5419 is returning that the file does not support SelfReg and an
error code 193 for the file (invalid Win32 app). The file does support
SelfReg. How do I harvest registration information from 64 bit dlls?
Windows Installer knows nothing about .NET, so the real question is whether you
are returning one of the documented results according to the INSTALL_UIHANDLER
documentation, and which one Dialogresult.Retry (4) maps to.
Phil
From: CristianG
MsiProcessMessage can't be called from a DoAction custom action. It's
documented somewhere I can't find, and mentioned in the MSDN community content.
You'd need to call it outside the DoAction.
Phil
From: akihiro.shib...@jp.yokogawa.com
I'm going to add my two cents at the risk of adding more fuel to the fire...
*sigh* Here goes...
I'm a firm believer of RTFM. On my first technical job during my first summer
break during college I was given old HP hardware, 6 CDs, and told Today you
will learn how to install HPUX from
Thanks for the tip on the Dependency Walker tool. Running depends.exe.
My verbose log states in the relevant lines.
...
MSI (c) (78:44) [13:18:52:817]: Doing action: PIDKEYValidation
Action 13:18:52: PIDKEYValidation.
Action start 13:18:52: PIDKEYValidation.
MSI (c) (78:D4) [13:18:52:823]:
Sorry for the wrong attribute name - i really meant InstallScope.
We've got own boostrapper application which executes msiexec.
We are executing one application (as a deferred CA with Impersonate
attribute set to 'No') during the installation process to create a
registry key with permissions for
Hi,
I am trying to build a merge module.
And here is the error I see:
light.exe : error LGHT0204 : ICE03: Invalid identifier; Table:
ModuleComponents, Column: ModuleID, Key(s):
mod_ticket.so.FCD893BA_6892_46F6_9A13_037CB5C0AE89.XT
E Ticketing.FCD893BA_6892_46F6_9A13_037CB5C0AE89.0
light.exe :
36 matches
Mail list logo