Hello,
I have 7 custom actions, 5 of which run during Install, and 2 of which run
during uninstall, none of which should run during an upgrade.
I am adding the upgrade feature to the product and have run into a problem.
The 5 that run during install (after InstallFinalize) work fine (i.e. do
Last one. I hope.
I have my dialog working as expected now, and it appears in the dialog flow. I
now, finally, want to only make it appear if neither of two particular features
have never been installed, and either is being installed.
I thought I'd try to get one condition working first and the
Thank you Blair, that resolved it. I filed bug to document the issue (ID:
3035649).
On Tue, Jul 27, 2010 at 5:43 PM, Blair wrote:
> Looks to me like a bug. In your wcautil.h file, change the following:
>
> HRESULT QuietExec(
>__in_z LPWSTR wzCommand,
>__in DWORD dwTimeout
>);
>
> To
Yes, I have my 2.0 wxs files still. All the FragmentRef elements were in one
place all clumped together in the main Product.wxs file (not the actual name,
but it's at the root). I can't imagine using more ComponentRef elements since
they are all specified in the Features\*.wxs. BinaryRef doesn't
My team wants the capability to install multiple copies of an MSI on a given
host with different tags appended to the ProductName (so the configuration
specialist can identify different instances in the Control Panel.
Obviously, I'd have to turn off detection of older or newer MSI's.
How best t
Ah. *slaps head on desk*
So that works, however when I display the dialog the check box is ticked. It
must be un-ticked and re-ticked to continue; the dialog looks as follows
!(wix.WixUICostingPopupOptOut) OR CostingComplete =
1
Does the dialog named "SupplementalEulaDlg" have a
inside of it?
-Original Message-
From: Barry Dorrans [mailto:bdorr...@microsoft.com]
Sent: Tuesday, July 27, 2010 3:56 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Adding a feature specific EULA
You mentioned you had to take out all of the elements you had
(since 3.0 doesn't support them). Each of those caused the fragment
containing the FragmentRef to "target" the identified fragment so that the
linker would look for them (instead of ignore them).
Since there are no more elements, you
Arrghh.
So almost there, well, maybe. Light is throwing (but not appearing in the VS
Error List Window - I see them in output)
error LGHT0204: ICE03: Not a valid foreign key; Table: ControlEvent, Column:
Control_, Key(s):
SupplementalEulaDlg.Next.NewDialog.VerifyReadyDlg.SUPPLEMENTARYEULAACCEP
Can I get any additional information on this? I'm finding what you said
to be a bit vague. I'll provide any code I can to give an idea of how
it's structured. Here's how the folders are layed out.
Product.wxs
Components\*.wxs
Features\*.wxs
UI\*.wxs
I can see Candle finds all the WXS files, and i
Looks to me like a bug. In your wcautil.h file, change the following:
HRESULT QuietExec(
__in_z LPWSTR wzCommand,
__in DWORD dwTimeout
);
To:
HRESULT WIXAPI QuietExec(
__in_z LPWSTR wzCommand,
__in DWORD dwTimeout
);
If that works, please file a bug against 3.0 (this issu
You probably need to replace each with a different <...Ref/>
element to link everything in. WixCop isn't going to know what other element
to use for the reference.
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Tuesday, July 27, 2010 3:22 PM
To: General
Using WiX build 3.0.5419.0 and whatever wcautil.lib is included with that
package.
On Tue, Jul 27, 2010 at 11:45 AM, Blair wrote:
> Which build of WiX are you using? Which wcautil lib are you linking with?
>
> -Original Message-
> From: James Kessler [mailto:kessl...@gmail.com]
> Sent:
This is blowing my mind. The MSI seems to get created, but it's way
smaller than it should be. In looking at it using Orca there is no
Component table and the File table is there, but completely empty. No
Feature table, either.
What's the situation with 3.0? Does WixCop not do everything needed to
http://msdn.microsoft.com/library/aa371173.aspx
"A RegPath may not begin or end with a backslash (\)."
Remove the '\' char after the "2.0".
(I found it by looking in MSDN for the ICE03 topic, found the "Invalid
registry path" entry in the table, and clicked on the link in the other
column of the
Usually WXL files are known only to light.exe, not to candle.exe, so culture
can only be known long after the preprocessor is done.
I didn't test this, but if I recall correctly, you can do something like
this:
C:\French\foo.txt
Etc.
Then:
-Original Message-
From: D8xter [m
Is the Culture attribute value different between those localization files?
-Original Message-
From: D8xter [mailto:d8x...@hotmail.com]
Sent: Tuesday, July 27, 2010 12:32 PM
To: Wix-Users
Subject: [WiX-users] Error using common Localization String IDs
Should I be able to create common st
Oops never mind I see where my fat fingers went astray :)
-Original Message-
From: Barry Dorrans [mailto:bdorr...@microsoft.com]
Sent: Tuesday, July 27, 2010 13:41
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Adding a feature specific EULA
So I'm bum
Put a next to your elements
(inside of the same fragment).
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Tuesday, July 27, 2010 12:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrade from WiX 2.0 to Wix 3.0
I'm getting this error after converting to WiX 3.0.
[exec] C:\Installation\Packages\E3_3_0\UI\uiUpdate_standard.wxs(90) :
error
LGHT0204 : ICE03: Invalid registry path; Table: RegLocator, Column:
Key, Key(s): Wse20Search
Here's the code snippet
This was working fine in WiX 2.0, but I d
Thank you, Blair, for a quick response!
I would also thankful for your recommendations about DTF. I've already made
some digging inside Installer class (and with the help of Reflector, nice
tool btw).
If it is possible, can you write down a bunch of lines of code (you were
speaking about), I would
So I'm bumbling along, just trying to get the secondary EULA displaying, not
evening worrying about making it dependant on a selected feature yet
I've taken the EULA dialog and created a new dialog from it, and the
FeatureTree UI and slotted in the SupplementalEulaDlg into the sequence but ...
I don't appear to be able to utilize localization strings in order to define
variables or conditional statements. Is there another way to determine, at
compile time, what language I am building? I would like to remove the
additional overhead associated with changing environmental or system
variable
Should I be able to create common string ids in multiple localization files?
For example, I change Product Name based upon culture so I create a
localized string 'ProductName' and change the value in each of my *.wxl
files. The error when building is "The localization identifier 'ProductName'
has b
I can see Candle load the comFlowMan.wxs file, but in my OBJ folder
there is no resulting comFlowMan.wixobj. No message from Candle
indicating a problem. This is very strange.
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Tuesday, July 27, 2010 11:50 AM
Updated WiX. Ran WiXCop against all my WXS source files. They look good.
I can compile, but when I go to link it is saying this for nearly ever
file.
[exec] C:\Installation\Packages\E3_3_0\Components\comFlowMan.wxs(21) :
erro
r LGHT0215 : The merge module 'merge_policy_VC80_MFC' is not assigned to
DTF does support (quite well, in fact) what you are asking, and yes, samples
are lacking. In fact, DTF was started as a wrapper/framework around the MSI
APIs, and support to "safely" enable custom actions was the key to add it to
the WiX toolset.
If no one else chimes in soon, I have some code I c
> 1) First part. I need to run an installation (*.msi file(s)) via .NET
> (C#) code. What is the best framework (if any exist) or maybe some wrapper
> classes (above MSI API) you could advise?
I haven't (yet) run into problems launching the MSI using the plain old Process
class, e.g.
usin
OK, I found the problem, and am replying in case anybody else runs into this
snafu.
The element needs the attribute Platform="x64"
*dope slap*
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In D
First stab: All the components that use that directory (or any directory
under that one) need to be marked as 64-bit (not reset to 32-bit).
-Original Message-
From: JK E-Lists [mailto:jkli...@ifm-services.com]
Sent: Tuesday, July 27, 2010 10:27 AM
To: wix-users@lists.sourceforge.net
Subje
I know 2010.2.0.0 is invalid. May be i was not clear enough in the earlier
question. Anyway,This is what i was looking for(Any method other than using
!(bind.FileVersion.fileId). Thanks.
On Tue, Jul 27, 2010 at 7:38 PM, Kim Gybels wrote:
> Hi,
>
> subrat agasti wrote:
> > I think u missed what
Hi, WiX community!
A question, the professional answer for I was unable to find through MSI and
installer forums.
1) First part. I need to run an installation (*.msi file(s)) via .NET
(C#) code. What is the best framework (if any exist) or maybe some wrapper
classes (above MSI API) you co
I have a 64-bit MSI that I build with WiX. There is a bootstrapper that
launches the MSI. It passes a couple of parameters along to control the
install.
I'm finding, running on 64-bit Windows 7, that MSI is changing the value of
INSTALLLOCATION unexpectedly.
I explicitly pass in
"C:\Prog
Which build of WiX are you using? Which wcautil lib are you linking with?
-Original Message-
From: James Kessler [mailto:kessl...@gmail.com]
Sent: Tuesday, July 27, 2010 7:47 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] QuietExec in CA
I mean the
I've seen this before and it's a weird one, maybe even a bug in MSI. If you
search for 2318 pagefile.sys you'll see a bunch of people asking what the heck
is going on. I haven't seen any answers though. When I've seen this it looks
like it's associated with costing and the directory table, but I
... and nobody should be doing things to CurrentControlSetnnn - they're
associated with the "last known good" configurations that Windows uses.
Phil Wilson
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Tuesday, July 27, 2010 5:19 AM
To:
Take a look at putting them all in one transaction using MsiBeginTransaction()
and MsiEndTransaction(). You'll need MSI 4.5 though. I've done this and it
seems to work well, although I haven't dealt with any exceptional issues like
reboots in the middle.
Phil Wilson
-Original Message
Sorry, wrong version in the title. It appears to be fixed in the June 11th
release.
-Original Message-
From: Kyle McClellan [mailto:kyl...@microsoft.com]
Sent: Tuesday, July 27, 2010 8:39 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Build error using v3.5.1923.0
I'm seein
I'm seeing the following error when trying to build my WiX project.
error MCB4057: The target "GetResolvedReferencePaths" does not exist in the
project.
I began seeing this error in my WiX project only recently after I linked in a
new VSPackage project (created in VS2010). My searches lead me
Heres a few random thoughts that might help.
Im assuming that your MSI requires SQL server express to be already on
the machine when it installs, in those cases where the SQL
express-dependent feature was selected. If this isnt the case, then just
conditionally run the sql server installer *after*
I mean the QuietExec() function which is part of wcautil.lib. If I create a
new C++ custom action with
hr = QuietExec(pwzCommand, dwTimeout);
The compiler returns "unresolved external symbol _QuietExec". QuietExec is
defined in wcautil.h and I'm successfully using other functions in the
wcautil
Ah that makes sense, insert the second EULA after the feature tree if the
feature that requires it is selected (well the two features). OK I'll have a
shot - and no doubt be back for more once the bruises from bashing my head
against the wall subside :)
Thanks all.
_
Hi,
subrat agasti wrote:
> I think u missed what i was asking. My assembly has a version 2010.2.0.0. I
> dont want to change that version. And because of this I can't use the
> !(bind.FileVersion.fileId), which will update the product version number
> based on the assembly version.
>
> Version="!
Hi there
There have been a number of references in this mail list on how to include
prerequisites. The recommendation is to handle prerequisites in the
product's bootstrapper. However I have a slightly more complicated
requirement: A prerequisite (SQL Server Express) is required only if a
p
Hi,
We update the MSI Major and minor version by hand and let the
build process update the build number.
So in the wix element we have...
Version="2.0.$(var.SdlBuildNumber)"
In the wixproj properties in the Build tab (assuming you use votive) we
add SdlBuildNumber=$(SdlBuildNumber); t
There are Properties you can use to unselect Features but I think an
easy way to achieve this is to use the normal WiX UI
LicenseAgreementDlg. If you've seen it already you'll have noticed the
Next button is disabled until the user clicks the "I accept" check box.
That should neatly sidestep any is
Hi everyone,
I'm looking for MSBuild scripts to create a bootstrapper file to deploy 3
custom MSI installers, if any of these installers failed, I have to rollback
all these changes.
For example:
I have to deploy App1.msi, App2.msi and App3.msi, the bootstrapper will check
for .Net 3.5 as
You're still missing the point.
"The first field is the major version and has a maximum value of 255."
Is 2010 greater or less than 255?
You can do something like
But you're still not going to get it to work as you can't have 2010 as
your major version field. Unless you bind it to a differe
With all due respect, I think you've missed what Pally was telling you.
2010.2.0.0 is an invalid version number for a product version. The
first number (Microsoft calls that the major version number) must be
less than 255. Since yours is 2010, its invalid and you can't use it.
This is also wh
Ah that looks like a good starting point. Forgive the stupid question, but how
do I then remove things from the feature tree due the responses on a dialog?
Ideally I'd also want it in maintenance mode - display it again if maintenance
mode is started if it's not already been accepted.
_
I think u missed what i was asking. My assembly has a version 2010.2.0.0. I
dont want to change that version. And because of this I can't use the
!(bind.FileVersion.fileId), which will update the product version number
based on the assembly version.
So i was asking if there is any other method t
OK you clearly missed the point on the page linked so I'll do you a
favour & copy & paste it in the hope that you spot the issue this time.
Consider this the WiX-users list version of "Where's Wally".
"The format of the string is as follows:
major.minor.build
The first field is the major versio
Thanks for the quick reply Pally. I can't use the !(bind.FileVersion.fileId)
, because I can't change my file version. Is there any other way to update
the version number of the MSI automatically? is it possible to read it from
a file ?
On Tue, Jul 27, 2010 at 6:10 PM, Pally Sandher wrote:
> http
http://msdn.microsoft.com/en-us/library/aa370859.aspx
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 **
Integrated Environmental Solutions Limited. Registered in Scotland No.
Hi,
I am updating the version number of my msi using
!(bind.FileVersion.fileId). But i am getting an error which says that the
version number 2010.2.0.0 is invalid.Why is that? This is the version number
of my .exe file. I can't change the version number of this file. Is there
any other way to up
Hello WiX Community,
I'm sure you know about StackOverflow.com. The authors of this fantastic
resource opened another service, called Area51. It allows building a
community around a certain topic and create an ad hoc site like
StackOverflow.com for free. Take a look here:
http://area51.stackexchan
Something doesn't sound right here. Both of those registry values are being
handled by the serviceinst...@displayname and serviceinst...@account
attributes. Have you tested your updated installer on a clean VM? I have a
hunch that your missing another variable and that this wasn't your fix.
Hi,
Thanks for reply. I really like your techniques :)
I solved this problem by following way.
I figured out the differences in registry after installing service manually. I
found following entries
I added these entries in my wix file followed by
You could add a second EULA dialog after the dialog with the FeatureTree
which only shows when the Feature or Features you need to show it for
are selected. The user guide page on Customizing the WiX UI should help
you get started ->
http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm
Y
It is possible to build one MSP that contains all four sets of transforms,
but it isn't exactly "obvious". However, you only need to build it once, and
some of us on this list could probably help you do it (the only thing really
needed are the four MSIs).
I've seen people use the INSERT INTO synta
What is the easiest way to write from a custom action into the Registry
table?
I'll try to avoid doing patches because of a few reasons:
1) I will need 4 of them - there are 2 bad versions in the wild, and
each has 32 and 64 bit variations
2) I will need to keep the patches around for a long tim
61 matches
Mail list logo
