Hi Alex,
Short answer: Yes, maybe, no. :-)
Detailed answer:
http://blogs.technet.com/alexshev/archive/2009/05/11/is-it-possible-to-use-r
egistrysearch-result-in-registryvalue.aspx
Regards,
Alex
-Original Message-
From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com]
Sent: Monday,
I use DTF to build a custom action Dll in C# (Wix Build 3.0.5217.0).
When I add the custom action named SQLiteValidation I encounter the
following installation error :
Error 1723. There is a problem with this Windows Installer package.
A DLL required for this install to complete could
Hi,
is it just me - or did the manuals really disappear from
http://wix.sourceforge.net/manual-wix3/main.htm?
Thanks,
Stephan.
__
Stephan O'Farrill
Weyringergasse 37/3/11a
1040 Vienna / Austria
+43 680 1268 751
Bob Arnson-6 wrote:
barry wrote:
Tried that other forum but they said to try WIX newsgroups!
If your WiX-built MSI works, then it's not WiX and it's not Windows
Installer. Sorry, I know it's not much help, but what you're describing
doesn't make sense unless the bootstrapper
I'd like to check that Crystal Reports Basic for Visual Studio 2008 is
installed as a condition for my own installation package.
I found this in the bootstrapper description for this product
(C:\Program Files\Microsoft
SDKs\Windows\v6.0A\Bootstrapper\Packages\CrystalReports10_5\product.xml) :
When I run a major upgrade install on Windows Vista or later the files
in use (or restart manager) dialog is displayed for the two services I
am installing, this doesn't happen on Windows XP (Windows Installer
v4.5). The services are controlled by the ServiceControl element and
listed in the
Assuming you mean the VC++ compiler - it puts all .obj files into a single
directory but automatically appends numbers to file names if they would
collide.
Like this:
main.cpp - main.obj
subdir\main.cpp - main1.obj
I could live with this scheme in WiX too.
Rob Mensching-6 wrote:
What does
On 10 May 2009, at 19:37, Chuck wrote:
Chris Ridd wrote:
Yes, the higher compression levels make building the msi much slower.
If you've got the concept of a debug vs release build, I'd
suggest
using no compression when debugging, and high when doing a release.
In the interest of
Something wrong with last Friday's build (SF had a hiccup and not sure
our build recovered well). The WiX.chm is available and the online
manual should be back this week.
stephan o'farrill wrote:
Hi,
is it just me - or did the manuals really disappear from
I personally always recommend reading the MSI SDK. It is dense but after
reading it so many little things will start making sense.
MYFLEX wrote:
Hi,
i want some information about how the installer will treat a feature. and
what is install level?
Please send some links where i can get some
Sounds like a very good feature request. Can you open it?
zett42 wrote:
Assuming you mean the VC++ compiler - it puts all .obj files into a single
directory but automatically appends numbers to file names if they would
collide.
Like this:
main.cpp - main.obj
subdir\main.cpp - main1.obj
I
The difference between Vista and XP is the RestartManager. IIRC, there
are a few things you can do to suppress the RestartManager usage via
MSIRM type properties... that might get you closer.
Neil Sleightholm wrote:
When I run a major upgrade install on Windows Vista or later the files
in use
Bob raises a good point. Actually, this is an even better reason to split your
files up close-to-evenly into a few cabs.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Monday, May 11, 2009 6:57 PM
To: General discussion for Windows Installer XML toolset.
Subject:
You can set MSIRESTARTMANAGERCONTROL to Disable.
-Brian Simoneau
-Original Message-
From: Rob Mensching [mailto:r...@wixtoolset.org]
Sent: Tuesday, May 12, 2009 11:11 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Files in use
The difference
I disabled restart manager in 2 ways, with the property
MSIRESTARTMANAGERCONTROL set to Disable and by removing the
MsiRMFilesInUse dialog but I still get the FileInUse dialog. I think
that means it is not directly attributable to restart manager. I did
find a KB article that said that WI 4.5
I was checking out the new version of WIX due in July and was wondering
if the issues with the MSMQ Extension and the Office Extension would be
resolved.
Specifically:
MSMQ Extension; On a repair, it fails with an error when the queue
already exists. It appears a check for the existing queue
Even with it disabled I still think it is used. From the log:
MSI (s) (AC:38) [16:52:55:648]: RESTART MANAGER: Disabled by
MSIRESTARTMANAGERCONTROL property; Windows Installer will use the
built-in FilesInUse functionality.
Then a bit later:
MSI (s) (AC:D4) [16:53:05:170]: RESTART MANAGER:
Mahmoud,
You could look into doing some work with heat.exe. If you harvest your
source into individual output files you could then use XSLT to add disk Ids.
There are general risks with this, many around patching.
Thanks,
Brian Rogers
Intelligence removes complexity. - Me
Neil, we run into the same issue with our product, but normally restart manager
catches it:
MSI (s) (6C:2C) [17:29:11:221]: RESTART MANAGER: Detected that the service
FooService will be stopped due to a service control action authored in the
package before the files are updated. So, we will
That doesn't work because those are product code guids, not component guids.
Try a registry search under
HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\{productcode}.
Also consider a search under HKCU if both your product and the dependency are
per-user products.
-Eric
To:
Some settings of MSIRESTARTMANAGERCONTROL disable the MsiRMFilesInUse dialog,
the docs are clear on that, and don't turn off the entire files-in-use
detection. Did you use Disable or DisableShutdown?
What's the Wait value in your ServiceControl element? I'd expect to see a log
entry saying
Thanks, that was definitely it.
Amy
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Monday, May 11, 2009 7:57 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] property value passed to CA through ExecXmlFile
property is not
If the UpgradeCode for Crystal is reliable you could make an Upgrade table
entry for it with only search for the range of versions you expect - that'll
set a property you can use in a type 19 custom action.
Phil Wilson
-Original Message-
From: Eric St.John
I have a simple related question. I am trying to test the execution of my
rollback custom action. I had thought that returning ERROR_INSTALL_FAILURE
from a type 1 CA with return=Check would do the trick. What I see though
is that further actions are skipped, the msi returns code 1603, and the
Thanks for your comments, it is good to know it should work.
StopServices is before RemoveFiles. Interestingly it also happens on a
normal uninstall so a least it is consistent.
Neil
-Original Message-
From: Eric St.John [mailto:eric.st.j...@hotmail.com]
Sent: 12 May 2009 17:33
To:
I am using MSIRESTARTMANAGERCONTROL=Disable which according to the docs
Disables interaction of the package with the Restart Manager. Windows
Installer uses the FilesInUse Dialog. - I am suspecting that it might
mean that is disable use of MsiRMFilesInUse not the Restart Manager.
The Wait value
In article 1242101191107-2867127.p...@n2.nabble.com,
achandrapano achan...@panologic.com writes:
Yes I see your point, but is there no way to do everything from the new MSI?
Nope. All you have access to in the new MSI is the new version.
Everything that happens in the old version is
In article 54eeb3a30905120956p79b48ea7ka564c640e57be...@mail.gmail.com,
Tim Haloun thal...@google.com writes:
I have a simple related question. I am trying to test the execution of my
rollback custom action. I had thought that returning ERROR_INSTALL_FAILURE
from a type 1 CA with
But from the new msi you do have access to the REP action which should call
the old msi's uninstaller. Why can't I put a rollback CA right before this?
I know I can if REP is after InstallFinalize, but then the remove/install
order gets screwed up. If REP happens in the beginning, why can't I
I'm using Votive now to develop my installer and have moved my code over
from WixAware. In addition I clean the code up to a point but now I'm
getting about 131 lines of errors and I'm not sure how to fix it at this
point. My apologies in advance for posting all this mess, but I figured
hello all.
my question regards sorted shortcuts in the startmenu. suppose i have an
install and it sets up a few shortcuts under a newly created folder under
the startmenu. then in a patch i want to add a new shortcut to the same
working directory, but i want that new shortcut to appear at the
Ok.. I think I figured this one out. I didn't realize till now that I
had a reference to the WixUIExtention.dll in my project.
-Original Message-
From: MacDiarmid, James D [mailto:james.macdiar...@eds.com]
Sent: Tuesday, May 12, 2009 4:16 PM
To: General discussion for Windows
In article 1242150015129-2870660.p...@n2.nabble.com,
achandrapano achan...@panologic.com writes:
But from the new msi you do have access to the REP action which should call
the old msi's uninstaller. Why can't I put a rollback CA right before this?
See the documentation on
Yeah I saw that, but was hoping there was some kind of hack. I read somewhere
that it is possible to access the old msi's actions in the new msi, but
maybe that was not true.
Thanks though Richard for the help.
Richard-45 wrote:
In article 1242150015129-2870660.p...@n2.nabble.com,
I've got the en-US parameter set in the cultures box in votive. Is
there something else I'm missing? I'm getting a lot of errors now that
seem to indicate that my project isn't loading my localization file.
Jim
--
In article 1242164147122-2873091.p...@n2.nabble.com,
achandrapano achan...@panologic.com writes:
Yeah I saw that, but was hoping there was some kind of hack.
Trust me, the *LAST* thing you want to be doing in your software
installations, upgrades and rollback handling is some kind of
So I added a rollback action to the old msi to reinstall my drivers right
before RemoveFiles. When I launched the new msi to upgrade, the rollback
action never executed but the log file tells me it did. I am sort of
confused by MSI log files. There are so many different calls to my rollback
In article 1242169753994-2875388.p...@n2.nabble.com,
achandrapano achan...@panologic.com writes:
So I added a rollback action to the old msi to reinstall my drivers right
before RemoveFiles. When I launched the new msi to upgrade, the rollback
action never executed but the log file tells
The rollback CA appears in #3 (during the rollback execution of the script)
since I see the following in the log file:
Rollback: RollbackDriverManagerReinstall
MSI (s) (F0:18) [17:03:27:438]: Executing op:
ActionStart(Name=RollbackDriverManagerReinstall,,)
MSI (s) (F0:18) [17:03:27:438]:
Have you set wixlocalizati...@culture to en-US for the localization files you
expect to be used when specifying Cultures=en-US?
-Eric
Date: Tue, 12 May 2009 18:44:46 -0400
From: james.macdiar...@eds.com
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Localization file
No, according to
http://blogs.msdn.com/oldnewthing/archive/2006/06/19/636823.aspx
Phil Wilson
-Original Message-
From: cemiles [mailto:chad.mi...@gmail.com]
Sent: Tuesday, May 12, 2009 1:34 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] shortcut ordering in startmenu
I have been testing the major upgrade procedure under WiX Version 3.0.5217.0
and Windows XP. I install version 1.0 of my application successfully. (It
has the required Upgrade element.) To prepare for the next version of my
application I increment the FILEVERSION, PRODUCTVERSION and FileVersion
In article 1242174267154-2877231.p...@n2.nabble.com,
achandrapano achan...@panologic.com writes:
So it looks like all the 3 conditions are evaluating to true, but nothing
happens. Is there any way to debug what the error really is? The Msi log
shows nothing to help me besides those two
Well the MsgBox works for the first rollback action that occurs in the new
msi. For the old msi, the message box doesnt show AND I also log driver info
to a file and that file wasn't updated either, meaning the binary action
isn't really happening even though the MSI log says it did. Any
1. MSMQ: I believe so. If the bug isn't opened it was either fixed or
punted.
2. Office: today the Office Extension is only used by ClickThrough.
Since development on ClickThrough has been postponed until WiX v4 the
Office Extension can be basically ignored.
Chris Snider wrote:
I was
In article 1242189374607-2878976.p...@n2.nabble.com,
achandrapano achan...@panologic.com writes:
Well the MsgBox works for the first rollback action that occurs in the new
msi. For the old msi, the message box doesnt show AND I also log driver info
to a file and that file wasn't updated
What should I look for in the log file? From what I pasted above, I do see
that my rollback CA is getting called, so that would mean my patch is in
effect. Is there any way to test a rollback CA execution? Like maybe instead
of calling a binary file or DLL file, to just pop up a box?
Richard-45
47 matches
Mail list logo
