As you said, I downloaded the WiX v3.6 RC0 (Released: Apr 3 2012) and tried
to uninstall the already installed version ( Wix Toolset V3.6.2221.0 ) of
Wix. But that version is not getting uninstalled!!!
Currently Wix Toolset V3.6.2221.0 is installed in my computer. But I failed
to uninstall the
Still not able to get FilesInUse dialog to come up. Any advice would be
much appreciated.
http://stackoverflow.com/questions/10327273/wix-how-to-use-fileinuse-dialog
--
Live Security Virtual Conference
Exclusive live
As previously stated in my previous thread (but not clearly as I had actually
two different issues) when I try to use a customized theme for the
bootstrapper some events are not processed at least for the failure
dialog. I haven't checked with the other ones.
This is what I used:
FilesInUse automatically detects files in use during InstallValidate and
displays the dialog if one of those files are changed.
Restart manager is a newer feature of Windows Installer and works with
filesinuse. The applications that are shut down because they have files in
use must have
Dear Peter,
Thanks for writing back. util:CloseApplication will close the application
if CloseMessage=yes, but when CloseMessage=no it seems that this should
trigger the FilesInUse dialog. At least, that was my expectation.
In Wix tutorials (e.g.,
Here's another possible clue:
http://sourceforge.net/tracker/?func=detailatid=642717aid=1989218group_id=105970
-
CloseApplication element doesn't cause the FilesInUseDialog.
Indeed, the latest CloseApps.cpp still has:
//
// Do the UI dance now.
//
/*
TODO: Do this eventually
I've removed the InstallCondition for the patch it's now working as intended.
Thanks for the input on this however I would point out the documentation
mentions nothing about patch applicability the InstallCondition description
says A condition to evaluate before installing the package. The
I am sorry to Bump, but can anyone help me?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX3-6-Uninstall-Failed-Installing-Votive-tp7500775p7502620.html
Sent from the wix-users mailing list archive at Nabble.com.
Can you provide the log?
On Thu, Apr 26, 2012 at 4:59 AM, Dmuller720 dmuller...@comcast.net wrote:
I am sorry to Bump, but can anyone help me?
--
View this message in context:
Please provide the log file.
On Wed, Apr 25, 2012 at 11:00 PM, Anirban Paul ani.banti.24...@gmail.comwrote:
As you said, I downloaded the WiX v3.6 RC0 (Released: Apr 3 2012) and tried
to uninstall the already installed version ( Wix Toolset V3.6.2221.0 ) of
Wix. But that version is not
1. Agree about the InstallCondition doc. Want to file a bug?
2. DisplayInternalUI on MSP might be broken. Want to file a bug?
3. Burn calculates size of installed packages + their cache size if they
are cached. I'd need more details about the size being wrong to be more
helpful.
4. The log file
MsiPackage Id=ve
SourceFile=..\..\..\install\ve2012.msi
After=SharedContentPatch
Compressed=yes
DisplayInternalUI=yes
ForcePerMachine=yes
Visible=no
Vital=yes /
Not too bothered about 3 so I'll ignore it for now. Just mentioned it as one
our QA guys noticed it today.
Regarding 4, I do have the same product code higher version however my
Upgrade Table code looks like the following:
Upgrade Id=removed
!--Original Shared Content UpgradeCode
I'm trying to build a patch using purely WiX method and I'm getting the
following error:
pyro.exe
: error PYRO0306 : An error (E_FAIL) was returned while finalizing a
CAB file. This most commonly happens when creating a CAB file with more
than 65535 files in it. Either reduce the number of
With chrome in the mix, nothing at all (not even IE or Firefox) gets
terminated.
Action 9:04:37: WixRegisterRestartResources.
Action start 9:04:37: WixRegisterRestartResources.
WixRegisterRestartResources: Entering WixRegisterRestartResources in
C:\Windows\Installer\MSI7074.tmp, version
Are you maybe misunderstanding the FilesInUse dialogs? Windows decides to show
this or nor based on what files need replacing, whether they are in use, their
versions etc. CloseApplication is not the same thing at all - it's a WiX
feature that closes applications.
Phil W
-Original
The log is in the OP
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX3-6-Uninstall-Failed-Installing-Votive-tp7500775p7503666.html
Sent from the wix-users mailing list archive at Nabble.com.
Hi all,
My installer doesn't seem to be installing anything properly. Any chance I
could get some help with it?
Here's the .wxs file:
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Product Id=MyGuid
Name=MyProg
Language=1033
Version=$(var.ProductVersion)
That HRESULT is FUSION_E_UNEXPECTED_MODULE_FOUND.
http://blogs.msdn.com/b/astebner/archive/2004/11/10/255346.aspx
Is there a config file associated with the assembly (maybe because it's a
policy assembly)?
Is it actually a Dll?
Phil W
-Original Message-
From: Sam Youtsey
What is the recommended way of writing a msi installer that will ask for a
serial number before installation? Any pointers, code example is greatly
appreciated.
Thanks.
-Helali
--
Live Security Virtual Conference
Yeah, it's a DLL. There don't seem to be any config files associated, just
the TLB file. Anything else to look for?
That HRESULT is FUSION_E_UNEXPECTED_MODULE_FOUND.
http://blogs.msdn.com/b/astebner/archive/2004/11/10/255346.aspx
Is there a config file associated with the assembly (maybe
And the TLB file is in the same component as the assembly or is somehow being
installed to the GAC? That could explain an error
FUSION_E_UNEXPECTED_MODULE_FOUND.
Phil W
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Thursday, April 26, 2012 12:35 PM
To:
Ah, I wasn't aware COM DLLs couldn't be installed into the GAC. What's an
appropriate course of action for using them on the client system if I still
wanted to use WiX?
And the TLB file is in the same component as the assembly or is somehow
being installed to the GAC? That could explain an
Well you can install assemblies (that supply COM interfaces) into the GAC. But
you are trying to install a Win32 COM DLL into the GAC? That won't work, and
it's not a WiX issue - it doesn't matter what you use to build your MSI file
because it's MSI that's doing the install.
If it's Win32
Weird, log is only visible in nabble.
Anyway, it looks like you were the victim of an intermittent bug in that
build. You need to get the core.msi off your machine. To do that try:
msiexec /x {0C317C74-81FB-4140-BE3C-33C074D511DE}
After that is removed, the bundle will hopefully uninstall
I don't see the Reinstall in the log file. It looks like the ve2012.msi is
being uninstalled and there was a user cancel.
On Thu, Apr 26, 2012 at 7:56 AM, Pally Sandher pally.sand...@iesve.comwrote:
MsiPackage Id=ve
SourceFile=..\..\..\install\ve2012.msi
Uhh, you can't Major Upgrade if the ProductCode is the same. I'm confused.
People (maybe not you) have been asking for support for support for Minor
Updates for a long time. Burn automatically handles it when an MSI doesn't
change it's ProductCode but has a higher version. Burn also notifies the
PS: Thank you for dogfooding.
Based on your comment below, I take it you were not around in the days of
WiX v2.0. Back then things were still pretty raw, there was basically no
documentation, error messages were near uselss and we were still figuring
out the best way to solve some key problems.
Once I've installed it into the CommonFiles directory how can I register
and access it through the system? This is typically done with RegAsm.exe on
the dev machine but this isn't available on the client machine. Eventually,
I want to be able to see this DLL's classes through Excel.
Well you
You really have to say if it's a Win32 COM Dll or not. I can't see a definitive
statement one way or another. However if it is Win32 COM, just use Heat.exe to
generate the WiX source for the registration.
Phil W
-Original Message-
From: Sam Youtsey [mailto:sam.yout...@gmail.com]
Sent:
I've built the DLL with an interface for interacting with other COM
components, how does this differ from being a Win32 COM DLL? Thanks for the
assistance with this!
On Thu, Apr 26, 2012 at 3:16 PM, Wilson, Phil phil.wil...@invensys.comwrote:
You really have to say if it's a Win32 COM Dll or
Not sure it's what you want, but what I typically do in this case is run
REGASM /Regfile to generate a .REG file and then use Heat to convert
that .REG file into a .WXS fragment that I can then include in my
project.
-Original Message-
From: Sam Youtsey [mailto:sam.yout...@gmail.com]
I've opened
https://sourceforge.net/tracker/?func=detailaid=3521813group_id=105970atid=642714
to
track this.
On Wed, Apr 25, 2012 at 9:30 AM, Bob Arnson b...@joyofsetup.com wrote:
On 25-Apr-12 11:45, Pally Sandher wrote:
Microsoft (R) Windows Installer Xml Linker version
I downloaded wix36.exe and installed Wix Toolset V3.6.2221.0. The
uninstallation UI does not specify anything about the log file when the
uninstall operation fails. Please let me know how to generate the log file
in this scenario.
Anirban
On Thu, Apr 26, 2012 at 8:00 PM, Rob Mensching
This should be fixed in the next build of WiX out Monday evening. Please
verify and let me know.
Thanks,
On Thu, Apr 26, 2012 at 7:10 PM, Heath Stewart clubs...@gmail.com wrote:
I've opened
https://sourceforge.net/tracker/?func=detailaid=3521813group_id=105970atid=642714
to
track this.
Log file is created in %TEMP% by default.
On Thu, Apr 26, 2012 at 9:56 PM, Anirban Paul ani.banti.24...@gmail.comwrote:
I downloaded wix36.exe and installed Wix Toolset V3.6.2221.0. The
uninstallation UI does not specify anything about the log file when the
uninstall operation fails. Please
I have attached the log file. Please find the attachment.
On Fri, Apr 27, 2012 at 11:03 AM, Rob Mensching r...@robmensching.comwrote:
Log file is created in %TEMP% by default.
On Thu, Apr 26, 2012 at 9:56 PM, Anirban Paul ani.banti.24...@gmail.com
wrote:
I downloaded wix36.exe and
37 matches
Mail list logo
