On 3/17/2010 6:08 AM, Jacek Pospychała wrote:
> This time, it's WiX dialog. On attached screenshot you can see which exactly
> button is stuck.
>
Check a verbose log and you'll see what's taking the time.
--
sig://boB
http://joyofsetup.com/
-
On 3/16/2010 4:03 AM, Kristoffer Danielsson wrote:
> I noticed that using the same registry setting works, but I'm not sure what
> this implies. Is this a bad idea?
>
Yes, it violates component rules. See "Organizing Applications into
Components" in the MSI SDK.
--
sig://boB
http://joyofse
On 3/16/2010 6:08 AM, Yu, Brian wrote:
> How do I check if a registry directory exists or not using
> registrysearch?
>
AppSearch doesn't have that functionality.
--
sig://boB
http://joyofsetup.com/
--
Download Int
On 3/16/2010 7:05 PM, Jacques Eloff wrote:
> It sounds to me then that a type 2 CA is not the solution then.
>
> I guess that gives rise to some more questions:
> 1) Where should I schedule this to ensure that rollbacks can be handled,
> keeping in mind that the assemblies I installed are in the GA
On 3/16/2010 4:28 PM, Dan Covill wrote:
> I've been dropped into the deep end of Wix for the last couple of weeks and
> am trying to come up with a way to make this work. I've learned how to mostly
> make major upgrades work but for some reason I can't quite nail down this
> aspect of the instal
On 3/16/2010 8:15 AM, Sanjay Poria wrote:
>
>
> Will mean that all the File elements will be embedded into the cab. Basically
> I wish to have “special” file elements that are to be installed but are not
> taken from the embedded CAB file.
>
Don't use @Cabinet or @EmbedCab attributes. That
It would be a bootstrapper install, look at Burn.
Phil Wilson
-Original Message-
From: s...@pacaccess.com [mailto:s...@pacaccess.com]
Sent: Wednesday, March 17, 2010 3:06 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstalling with merge mod
Hi,
I generate 2 MSI files in my nightly build: a test installer for the
testers, which is basically a release installer just not officially to be
released and contains more log info, and a development installer which
developers can install. This last one is build with debug flags and contains
Thanks for the feedback Phil. Do you have any examples of adding
vc_redist.exe to a Wix install script?
Thanks,
Jeff
> The issue has to do with lots and lots of stuff going on when the C++
> runtime support merge modules are uninstalled. I am not aware of any way
> to stop them, other than by u
Ok, thanks.
So how can I detect the old version? All I want is to display a message box
advising the user to uninstall the previous version.
> From: phil.wil...@invensys.com
> To: wix-users@lists.sourceforge.net
> Date: Wed, 17 Mar 2010 17:34:44 -0400
> Subject: Re: [WiX-users] Detect older ve
You can't use the Upgrade mechanism at all here - it's not that the previous
install was elevated, it's that the FindRelatedProducts action running in one
context won't detect a product installed in the other. A per machine won't
upgrade a per-user either.
Phil Wilson
-Original Messag
On Wed, Mar 17, 2010 at 4:17 PM, Pally Sandher wrote:
> Set the default path for it to be AppData & add a Type 51 Custom Action
> to change the path to your .exe's directory when the main feature is
> selected for install.
>
Many thanks for your answer. I understand the logic behind this, but I c
I tried using $(OutDir) to correct my $(TargetDir) problem, but got the same
error (variable does not match actual path). So I believe it is indeed related.
> Date: Wed, 17 Mar 2010 11:14:25 -0700
> From: b...@bradcunningham.net
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users]
Note that my previous MSI was a per-machine installation made with VS 2008. The
product version was 1.0.0.
Now I'm creating a per-user installation with WIX 3.5. I want to detect this
older version. Correct me if I'm wrong, but the older version cannot be removed
since it was an elevated in
Sorry, meant to say that the the comment is referring to how there is no
condition against TargetDir's value when setting the TargetDir property -- not
TargetName.
-Original Message-
From: Tony Paloma
Sent: Wednesday, March 17, 2010 12:30 PM
To: 'General discussion for Windows Installer
I think the comment is referring to how there is no condition against
TargetName's value (notice how most others only set the property if it doesn't
yet exist, but this one doesn't do that).
I'm unsure of what you mean by "the code snippet in the condition" because all
of the GetFullPath and Co
Hi, what is the best practice or recommended approach for providing a
Test version of a product and a Production version on the same server?
One installer or two?
Thanks,
Sam
--
Download Intel® Parallel Studio Eval
Try
The issue has to do with lots and lots of stuff going on when the C++ runtime
support merge modules are uninstalled. I am not aware of any way to stop them,
other than by using the vc_redist.exe package as a prerequisite install up
front and forgetting about merge modules.
Phil Wilson
-
Hmmm, sounds somewhat related but not enough info in that post to fully
understand. Also, my issue appears to be related to OutDir not TargetDir
(though I suspect they are handled in a similar fashion.
Thanks for pointing me to the issue. If mine does indeed end up being
related I will make sure t
My installer is fairly simple and only installs two files. I just added
the VC8 runtime merge module to my installer. Installation time increased
a little, but the time to uninstall increased a lot. Towards the end of
the uninstall, the uninstaller appears to wait for 2:45 and gives the
appearan
I have successfully automated heat in situations where I don't have to register
COM component *and* was only going to support Major Upgrades. In these cases I
use my build tool, MSBuild, to stage the files correctly for me. I tell heat to
let the compiler determine GUIDs for me as candle does th
Yes, I've placed it in main wxs and have moved it to InstallExecuteSequence.
Now it looks like
PATCH
AND Installed
Also I've produced new msi with this change and have installed it. Then I
have produced new msi version, and have created msp.
But it
Do you think this could have something to do with this bug?
http://sourceforge.net/tracker/?func=detail&aid=2970793&group_id=105970&atid=642714
> Date: Wed, 17 Mar 2010 10:57:15 -0700
> From: b...@bradcunningham.net
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Strange MSI outp
Sandip Shahane would like to recall the message, "Where can I get the symbols
for WIX 3.0 RTM?".
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and
Hey internal site http://wix should have the details for binaries, sources and
symbols. I had enlisted wix 3.0 RTM tree some time back.
-Original Message-
From: Sharat Janapareddy [mailto:sharat.janapare...@microsoft.com]
Sent: Tuesday, March 16, 2010 3:53 PM
To: General discussion for W
I just installed WiX 3.5.1512.0 onto my build server and added a new project
that is using WiX to the build. I am getting strange behavior when compiling
my installer. I don't see any build errors, and the MSI does get built but
it is put in the wrong path. When building my release configuration th
I have a strange issue with creating and setting permissions on a new
directory. My goal is to have THE_USER_ACCOUNT user to have permission to
create, and rename files in this new directory. The following relevant
snippets create the dir and set permissions for all the other users
correctly. It ge
Is that code in your new Product or in the patch XML? It should be in
the new Product if it's not already.
Try putting your Custom Action in the InstallExecuteSequence not the
InstallUISequence. Since you're essentially trying to suppress running
of the InstallUISequence it may already be too late
I've tried to add following code
PATCH
AND Installed
But it does't work (((
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Tuesday, March 16, 2010 7:17 PM
To: General discussion for Windows Installer XML
Set the default path for it to be AppData & add a Type 51 Custom Action
to change the path to your .exe's directory when the main feature is
selected for install.
Simplest option would be to modify your app so it always loads the
config from AppData regardless & just put it there. Actually why doe
So how would you automatically include everything in a directory where the
filenames of those files can change from 1 build to the next?
WiX does have a way to handle this, it's called heat.exe. There are people
using it as part of an automated system to generate fragments, there's even
been cha
Jeff,
Several people including myself have reported seeing this during the
course of an installation. It appears to only happen once in a while so
its very difficult to catch. In fact, I had it happen yesterday when I
was trying to install either WiX or WixEdit (I don't remember which)
onto a
That's exactly how you solve it, according to the docs! :)
> From: alb...@de-notenbalk.nl
> To: wix-users@lists.sourceforge.net
> Date: Wed, 17 Mar 2010 14:34:45 +0100
> Subject: Re: [WiX-users] Adding multiple files to component
>
> I've been following this discussion and still I haven't seen
hi,
see topic "Changing the UI sequence of a built-in dialog set" at
http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm
Assuming that you're using Wix_InstallDir GUI mode, here you can see how it
is implemented:
http://wix.cvs.sourceforge.net/viewvc/wix/wix/src/ext/UIExtension/wixlib/
I've been following this discussion and still I haven't seen the solution
we've build;
When we create an installer set we harvest the files into the appropriate
folders, then we have create a tool which scans which files are there.
The files are stored into a database where they are assigned a GUI
Maybe, but it seems kind of silly. So if have a directory fill with a thousand
help files, I need to manually maintain this. Even if the tool that generates
the help files have a different name each time. This seems completely
ridiculous that WiX doesn't have a way to handle this!
-Origi
Hi,
I want to suuppress licenseagreement dialog and the dialog where it will
allow the change in the install path as mine is a simple installer.
How to do that?
Thanks, Subramanyeswari
--
View this message in context:
http://n2.nabble.com/suppressing-custom-dialogs-tp4750044p4750044.html
Sent
1) I believe I posted a detailed explanation on this. You should only use heat
manually!
> From: cameron.ker...@philips.com
> To: wix-users@lists.sourceforge.net
> Date: Wed, 17 Mar 2010 13:19:54 +0100
> Subject: Re: [WiX-users] Adding multiple files to component
>
> Thanks. I guess people hav
Vb6 com dlls include registration information for the vb6 runtime in
their selfreg code (this is why selfreg is evil). This option excludes
that information so that uninstalling the component does break the vb6
runtime.
Neil
Neil Sleightholm
n...@x2systems.com
On 16 Mar 2010, at 12:50, "Bi
Hi,
How to suppress licenseagreement dialog and and installdirdialog(option for the
user to select the installtion path) as i do not want show up these dialogs as
mine is a simple installer.
Thanks, Subramanyeswari
--
Thanks. I guess people have been giving me two different responses here and
I'm trying to figure out the right way to do this.
1) Should I use heat each time during a build, to harvest all the files in a
directory (directory contains a executable and all of its associated dlls and
dependencie
You can try this - simple GUI
http://flexsetup.codeplex.com/
WiXFileTool: generates WiX file definitions and component definitions for a
collection of files
From: "Kerber, Cameron"
To: General discussion for Windows Installer XML toolset.
Sent: Tue, March 16
Thank you very much for reply.
Sorry, but I'm not sure where I should specify this custom action.
Should I specify it in "mailto:pally.sand...@iesve.com]
Sent: Tuesday, March 16, 2010 7:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Disable UI in patch by
Thanks. I set Version attribute for Product element in format x.x.y.z and it
is displayed correctly in Show Info window, but the issue is - actual
application version is e.g. 1.260.1.25, but msi cannot be compiled due to
installer restriction (major and minor should be less than 256). So I
thought
Ok, thanks:)
Mvh
Vegard Sandberg
-Original Message-
From: Jacek Pospychała [mailto:jacek.pospych...@gmail.com]
Sent: 17. mars 2010 11:14
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Unsubscribe
Vegard,
to unsubscribe, go to https://lists.sourceforge
Vegard,
to unsubscribe, go to https://lists.sourceforge.net/lists/listinfo/wix-users
You only need to type your e-mail address to unsubscribe.
On Wed, Mar 17, 2010 at 8:09 AM, Vegard Sandberg
wrote:
> Hi!
>
> I want to unsubscribe from wix users list, but I seem to have lost my
> password.
>
>
>
This time, it's WiX dialog. On attached screenshot you can see which exactly
button is stuck.
thanks for the disk space information!
Jacek
2010/3/16 Wilson, Phil
> Is the repair a WiX dialog? These are typically standard Windows Installer
> dialogs.
>
> Disk space:
>
>
> http://blogs.msdn.com
Hi!
I want to unsubscribe from wix users list, but I seem to have lost my
password.
Kind Regards
Vegard Sandberg
Systemutvikler
Visma Unique AS, PB 246, Ranvik Brygge 5, 3201 Sandefjord
Sentralbord: +47 33 44 84 00
Mobil: +47 93 26 27 95
Hi all,
I have a feature that controls where the config file for our application is
located (either "locally" next to the exe in Program Files, or in
%APPDATA%). When this feature is selected, the config file is copied
correctly to the right place, and the indicator file (to let the .exe know
tha
49 matches
Mail list logo
