Hi All,
I am trying to fix a bug in an existing Wix MSI code, the MSI fails on Windows
2008 with UAC Enabled, if we disable the UAC the MSI runs fine.
During investigation I found, the Wix is calling C++ custom actions those using
method GetMsiProperty to retrieve the properties from MSI.
Hi,
You can use "Quiet Execution Custom Action" to finish register files. I don't
whether you can read Chinses or not, but there are some notes in my blog in
Chinses.
http://blog.csdn.net/salever/archive/2009/11/02/4758313.aspx
I hope it's useful.
For example, execute a cmd line during
Thank you so much. I think it helped. Below is the code I have modified from
your sample but I need to register 4 files with regasm like I am doing in the
batch file:
%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe
"%SYSTEMROOT%\system32\Hyland\SigDef\SDEpicAnalysis.dll" /codebase
%
Check out the REINSTALLMODE Property in the MSI SDK.
On Mon, Nov 16, 2009 at 8:06 PM, Igor Lemsky wrote:
> As I know in Windows Installer there are rules about components upgrade for
> files. If it has version than it will be upgrade if in file the version is
> newer. And for other files if date
Interesting, I don't know much about patching but I've never heard anyone
say they prefer the .pcp file to pyro.exe. I'm very curious why you say that
pyro.exe isn't useful in an automated build approach.
On Mon, Nov 16, 2009 at 8:32 AM, Schmitz, John wrote:
> The way I understand a previous com
As I know in Windows Installer there are rules about components upgrade for
files. If it has version than it will be upgrade if in file the version is
newer. And for other files if date is newer.
But is any chance to change this logic for some components? For example,
third party dll version is the
Hmm, ok. Only the bootstrapers do then I suppose.
Are there plans to update Votive to include the attribute based on whether a
boot strapper is going to be used?
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Monday, November 16, 2009 7:16 PM
To: General discu
Bob, is there any way to verify the contents of the wixobj file?
It seems to me, though I'm just guessing at the functionality inside a black
box, that the file comparison is done by compilation of the PatchCreation block
by candle, and it's the file comparison that is broken.
I'm definitely
Hi,
I wrote a simple demo for your requriement. You can modify it according to
your needs.
http://schemas.microsoft.com/wix/2006/wi";>
Privileged
Kalev Lember wrote:
> Am I trying to do something that's not supposed to work that way?
Actions can be scheduled only once in any sequence.
--
sig://boB
http://joyofsetup.com/
--
Let Crystal Reports handle the report
Schmitz, John wrote:
> With some experimentation, I was able to get my patch to build with the 3.5
> release of WIX. The current release shows the same bug, at the same point in
> the patch log. I'm willing to enter a bug on it,
If you're using .pcp files, the bug is in msimsp/patchwiz, not WiX
Keep coming back, we'll make more. (And I know which book I'd like on
my Kindle and it's none of mine.)
John Robbins wrote:
> Bob,
>
>
>> WixUI_Advanced was something Rob and I designed and implemented in one
>> night when figuring out what a good UX for the WiX installer would be.
>> It succe
Matt Ryan wrote:
> Is this a known issue, or am I doing something wrong?
>
Works for me. Might have been a transient error on SF.net.
--
sig://boB
http://joyofsetup.com/
--
Let Crystal Reports handle the reporting
John H. Bergman (XPedient Technologies) wrote:
> I am curious why WiX does not add this attribute by default?
>
WiX doesn't require MSBuild 3.5.
--
sig://boB
http://joyofsetup.com/
--
Let Crystal Reports handle the
tvks wrote:
> * I want these two buttons to be one as "Change/Repair" like in other
> applications
> * When I select this button I want my bootstrap program (setup.exe) to run
> and not the msi
>
That's up to whatever bootstrapper you're using, not WiX.
--
sig://boB
http://joyofsetup.com
JKLists wrote:
> I'm porting a .NET product from and older InstallShield to WiX. My
> ignorance of details of MSI and .NET's interactions with the registry
> are showing through here.
>
Compare the .msis with Orca or decompile the old one with dark.exe to
see what's different.
--
sig://boB
With some experimentation, I was able to get my patch to build with the 3.5
release of WIX. The current release shows the same bug, at the same point in
the patch log. I'm willing to enter a bug on it, but I'm not sure anyone will
be able to reproduce it without the entire 1+GB of files in the t
I'm porting a .NET product from and older InstallShield to WiX. My
ignorance of details of MSI and .NET's interactions with the registry
are showing through here.
I used heat to do the heavy lifting, and all files are in the correct
place after install.
However, I can't get the WiX-installed a
This will tell you if 3.5 is installed
Installed OR NETFRAMEWORK35
Privileged
You will need a bootstrapper if you want to install 3.5 when it is missing.
-Original Message-
From: Wendell Joost [mailto:wende...@gmail.com]
Sent: Monday, November
This one worked for me:
REINSTALL or Not
Installed
Thanks
Lian
-Original Message-
From: Lian Jiang [mailto:lji...@microsoft.com]
Sent: Monday, November 16, 2009 11:59 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] how to prevent uninstalling MSI using
I've had a little experience with it... the automatically generated
WiX code was a bit "messy" for my liking, however it's just as
powerful as WiX is, so yes it can tackle the most complex of installs.
But I wouldn't want to.
I love the bootstrapper with MSI Factory (it's worth the license cost
al
I don't have time to write you a sample, but I can point you at some
reference material for getting started.
Start with the sample WiX code in the WiX CHM file.
.Net 3.5 detection - start here:
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg14255.html
regsvr32 is evil, you reall
I just started working with WiX and it seems like an amazing piece of software.
I am hoping that someone could write an example wsx file for me that does the
tasks below. I urgently need to replace a batch file with an installer because
of the unreliability of a batch file. If someone could writ
I had had to hunt down how to correct the 'No HomeSite attribute has been
provided' errors when creating a bootstrapper.
(the solution was to add ToolsVersion="3.5" to the project definition line so
you end up with a line like this in the WixProj:
http://schemas.microsoft.com/developer/msbuild/
I don't think this is correct, as of WiX version 3.0.5027.0 the default
is for FindRelatedProducts to run before LaunchConditions.
Neil
-Original Message-
From: Alexander Shevchuk (Volt) [mailto:a-ale...@microsoft.com]
Sent: 16 November 2009 21:25
To: General discussion for Windows Insta
element under is a LaunchConditions action and usually
LaunchConditions action is scheduled way before FindRelatedProducts action.
What you need is appropriately conditioned Custom Action Type 19 scheduled
right after FindRelatedProducts in both InstallUISequence and
InstallExecuteSequence.
Hi wix users,
Does anyone know how to stop an installation if a previous version does
not exist? I have followed the following links, but just can't seem to
get this to work properly. I would like the install to stop if a
specified version does not exist, forcing the user to be a the correct
Hi,
If necessary, is it possible to prevent users from uninstalling an installed
MSI by using guid in command line (e.g. msiexec /x {Guid})?
Appreciate any advice.
Thanks
Lian
--
Let Crystal Reports handle the reportin
I don't think it is ugly, I have documented the approach I use here:
http://neilsleightholm.blogspot.com/2008/08/executing-sqlcmd-from-wix.ht
ml.
Neil
-Original Message-
From: Simon Topley [mailto:simon.top...@wallingfordsoftware.com]
Sent: 16 November 2009 13:26
To: wix-users@lists.sour
I finally got this to work. The only thing missing after my last setup was
to have a PatchFamily element for each language's ProductCode in MSP.wxs.
Thanks again for all your help!
On Thu, Nov 12, 2009 at 11:19 PM, Blair wrote:
> You have different MSIs for the different languages. Any chance
Hi,
I found the MSP build log, and discovered I've run into a bug in 2.0. The
process goes along as expected until it hits some VS 2005 files installed be an
MS merge module to support some 3rd party software (our product uses VS 2008).
After the process decides that some of these files are ad
Hi,
I'm just learning about WiX and am learning about the dialog sets. When I
click on the WixUI_FeatureTree or WixUI_InstallDir links on
http://wix.sourceforge.net/manual-wix3/WixUI_dialog_library.htm, I get this
response:
An error has been encountered in accessing this page.
1. Server: wix
Not easily, no, and not from the MSI uninstall dialog. It's a standard
FilesInUse dialog, and I think that Windows will show its own even if you don't
have one in your MSI file. Why is this an issue anyway? Do you want it done
automatically? The alternative might be a reboot to clean up the sys
Never mind - I just added the other product's upgrade code into Application1
and it was removed during the upgrade.
-Original Message-
From: Tom Crozier [mailto:tcroz...@rackwise.com]
Sent: Monday, November 16, 2009 11:02 AM
To: General discussion for Windows Installer XML toolset.
Subje
Pally,
Thanks for clarifying. This example in the 3.0 documentation is so completely
unlike the documentation for 2.0 that I assumed that they were entirely
different processes! I don't know from this documentation what the "sample.txt"
files have to do with anything - I want to compare two ADM
I think you misunderstand me. Look at the v2.0 guide for making patches
then look at the *equivalent* v3.0 guide (as in the one I linked on my
first reply to this thread which deals with using PCP files). You will
see there are some differences. The differences are small but they
exist. I use the P
The way I understand a previous comment from Blair, there was no intention to
deprecate the 2.0 approach to patches. Unless I am misunderstanding something,
the 2.0 approach is much, much more useful for an automated build than the 3.0
approach.
From: Pa
Sure, entered as Bugs item #2898554
John
From: Rob Mensching [...@robmensching.com]
Sent: Monday, November 16, 2009 10:32 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Help with building patch
Yes, please open a bug
I need to uninstall an application (that was installed via its own installer
package) if it is detected during the major upgrade of another application.
E.g.
Application1 Ver 1.1 is installed on a machine and is about to have a major
upgrade performed on it to bring it to Ver 2.0.
Application 2
Rob he's trying to use v2.0 how-to guide with the v3.5 toolset. I'd wait
for someone else to verify this is an actual bug as it works completely
fine in v3.0.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design
Using WiX 2.0 I built plenty of MSP's using those instructions in the past.
They're not completely clear in places but they work fine once you understand
what you're actually trying to do. The (old v2.0) WiX tutorial also helped in
this regard but I don't think it's available any more since the
Yes, please open a bug on v3.5. That is under development and bugs help us
quickly find what was recently broken.
On Mon, Nov 16, 2009 at 7:12 AM, Schmitz, John wrote:
> I installed and switched to using WIX 2.0 (stable). This clarified two
> things:
>
> 1) SOME of the changes that I specify in
OK, sorry, I spoke too soon. The result of the patch building process with WIX
2.0 is a .MSP file that is very nearly the size of the original MSI file. I saw
a second command prompt window processing a large number of files that DID NOT
CHANGE between the two versions, some of which were versio
I installed and switched to using WIX 2.0 (stable). This clarified two things:
1) SOME of the changes that I specify in my bug are indeed only needed to adapt
the WSX file to version 3.5. The original code in the page works with 2.0 IF
you know to save it as a WSX file and use it as the source f
OK, I see that Indigo Rose's MSI Factory (formerly Setup Factory, I
believe) is based on the WiX toolset.
Does anyone have any experience with this product? If so, does it have
all the ability needed to tackle even the most complex of install?
Web/IIS stuff?
-Original Message-
From: Rob
I found another solution, a bit ugly but it seems to work. I'm using
QtExecCmdLine to run sqlcmd.exe with all of the relevant info. Might be
useful to others.
Simon
-Original Message-
From: Simon Topley
Sent: 16 November 2009 09:25
To: wix-users@lists.sourceforge.net
Subject: Re: SQLScri
On 11/16/2009 12:31 PM, Selvakumar B wrote:
> I don't want to allow the installation to proceed, if any of the
> filters fail to register. Users just click ignore and proceed with
> the installation only to find out that they have a broken
> installation.
>
> Can we restrict the error message witho
Hi,
When I uninstall a product, the folders are not removed.
I checked the log, and found following info:
MSI (s) (E4:60) [23:48:41:812]: Executing op:
FolderRemove(Folder=C:\ProgramData\Microsoft\Windows\Start
Menu\Programs\MyCompany\Prod3\,Foreign=0)
MSI (s) (34:80) [04:03:38:633]: Executing
Hi,
I have created a Wix installer and have packed it in a bootstrap program.
When I execute the bootstrap program it creates the following entries in the
registry :
http://n2.nabble.com/file/n4011693/Up.jpg
When I run the bootstrap program it installs well and when I run the
Add/Remove progr
2 ways you could achieve this off the top of my head.
1 - Use WiXUI_InstallDir (or whatever the WiXAware equivalent is)
instead of WiXUI_Mondo/WiXUI_FeatureTree or whichever UI is using the
SelectionTree control. You can then author a second dialog page after
the InstallDirDlg to configure the LOG
Hi,
Msi needs Windows Installer Service to finish installation, and two
installation programs can not run at the same time.
I guess there is something relative to your issue.
2009-11-16
salever.lee
发件人： Sunkesula, Srivardhan
发送时间： 2009-11-16 12:48:33
收件人： General discussion for Wind
I'm assuming you mean you've upgraded to v3.5.0925.0 not v3.0.5925 as
the last v3.0 release was v3.0.5419.0.
Firstly that's quite a massive jump to go from v3.0.2925 to v3.5.0925.
v3.0.2925 is at least 2 years out of date & you've skipped all the other
v3.0 releases & jumped straight to a v3.5 rel
Hi,
I guess you can use tags to stop installation.
2009-11-16
salever.lee
发件人： Pally Sandher
发送时间： 2009-11-16 19:48:19
收件人： General discussion for Windows Installer XML toolset.
抄送：
主题： Re: [WiX-users] While installation,Restrict the error message without
'Ignore' button and st
I ran into this same issue before the ATL security fix updates were
released. We had to get a hot-fix from Microsoft for the Visual Studio
2005 C++ redistributable controls as installations of MS SQL 2005 would
break our application due to being shipped with a post-SP1 version of
the controls which
What are your "filters" exactly & how are they being registered?
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
Hi,
I am using WIX 3.0,
I don't want to allow the installation to proceed, if any of the filters fail
to register. Users just click ignore and proceed with the installation only to
find out that they have a broken installation.
Can we restrict the error message without 'Ignore' button and stop
This thread has been really enlightening. Thanks everyone for the information.
I had this issue a
little while ago, with VS building against one version of the runtime and the
merge modules
delivering another. After a lot of searching online I finally found the code
snippets to get VS to
b
Cheers Rob,
I may fix it for you if I can't find another solution. MDF files are out
as there are issues between versions of SQL server apparently.
Simon
Disclaimer: This electronic communication and its attachments may contain
confidential, proprietary and/or legally privileged information whic
58 matches
Mail list logo
