Unfortunately, I think you will have to resort to a Custom Action to get the
behavior you want. However, rather than delete files, just add temporary
records to RemoveFie table for the appropriate Component to do the removal when
you want it done. Using temporary records lets the windows insta
Sure. Its pretty simple - just create your dialog, copy WixUI_Mondo (or one of
the other UI sequences if you want), and insert your button publications...
Compare my XML below with WixUI_Mondo.wxs and you'll see what I've changed (and
inserted)...
Adam Langley
Senior Developer
http://schemas.m
I second this question. I am in the same boat.
Adam,
Do you use the WixUI or some custom UI?/Would you be able to post your code for
the UI on uninstall?
> Date: Fri, 27 Jun 2008 16:10:48 +1200
> From: [EMAIL PROTECTED]
> To: WiX-users@lists.sourceforge.
May be Votive could also support WiXCop:
http://sourceforge.net/tracker/index.php?func=detail&aid=1992209&group_i
d=105970&atid=642717
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Menschi
Hi guys,
I have been battling with this problem for a while.
I have a .Net application which saves temporary data into
AppData\Roaming\Bookmarks.
This folder should not HAVE to be installed by the MSI as the app will
create it when needed (but I've gotten to the stage of experimentation
where
Correct, .wixlibs won't help you there. Unfrotunately, that means you're stuck
fighting with the Modularization of identities to get things to all line up.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Karper
Sent: Thursday, June 26, 2008
Hey Ben,
Unfortunately the amount of components in your installation might not fix
the problem. That isn't really want my article said to do.
Here is the scenario where that will break. Another per-user package has
been installed on the machine with hundreds of components. The Component
registry
Brian,
Thanks for that, it fixed the problem. I reduced the number of components by
increasing the number of files per component (that was a tedious job :)).
It's now installing and uninstalling fine.
The help was much appreciated - I've been bashing my head on the wall for weeks
trying differ
I'm not sure how that would help me with any of my issues. I'm willing to
use whatever structure I need, and we will be hopefully migrating everything
to WiX across the board one day (Being able to automate the build is the big
seller there, BTW)...But it won't be for at least a year. so, loo
Yes, re-using project files across certain builds seems to be problematic
lately. We could hide behind a statement like "it's still in beta, so expect
breaking changes". But at this point that probably isn't valid because WiX 3.0
is entering stabilization and we're generally encouraging people t
On Thu, 26 Jun 2008 11:14:12 -0400, Tony Juricic wrote:
Tony,
> 20 MB is a pretty large difference! Am I missing something obvious
> or is InstallShield compression really that superior?
The first question always is whether you reference your main executable for the
icon. If you do, you'll get
You could create a bunch of wixlib's and a merge module to consume them and
then consume the merge module with InstallShield. This allows you to interop
with other tools while leaving the door open for pure WiX down the road.
But yes, I like wixlibs better. When you get into building installs
I need to add a virtual directory to an existing website during my application
install. I would like to use the WIX WebVirtualDir custom action in order to
do this. Unfortunately in order to reference an existing website I need to
know the name of the website. I don't have this information, w
But the other installations are built with InstallShield. They won't work
with .wixlibs, will they?
On Thu, Jun 26, 2008 at 6:01 PM, Rob Mensching <[EMAIL PROTECTED]>
wrote:
> I would recommend .wixlibs instead of .msm files (unless you have share
> your Merge Modules with people that don't use
I don't think there are MSBuild tasks for torch/pyro yet. The build sequence
is involved and Peter is still thinking about it... I think.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pete Maroun
Sent: Thursday, June 26, 2008 13:02
To: wix-users@lists.
Sounds like a bug in there somewhere. Can you log it?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Rerick
Sent: Wednesday, June 25, 2008 16:15
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Bug in dark.exe?
I am de
Also, you can be a bit more robust in your File reference by doing
"[#AutoPilotFileId]" instead of "[AUTOPILOT]AutoPilot.exe"
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of bryan rasmussen
Sent: Thursday, June 26, 2008 01:12
To: wix-users@lists.sourcefor
The PUBLIC Properites passed across the client to server for a particular
install should be logged. The problem is if you take the shortcut you are
allowing *any* PUBLIC property through. Now you have to think about what every
single PUBLIC property can do on the server side. Or you can just
Jason, it sounds like there is some really strange behavior in build to build
upgrades of the project. I think when people start clean it works fine but if
they have an old VS project (2005 or 2008) then moving to a new project doesn't
work. Is that possible? Do we need to teach WixCop to upg
Compressing an MSI in a bootstrapper can often get you impressive wins if you
have a lot of data in your MSI like Jason suggests. I have a 120K MSI and my
compressed bootstrapper ends up 90K total.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony Ju
I would recommend .wixlibs instead of .msm files (unless you have share your
Merge Modules with people that don't use WiX). .wixlibs are far more flexible
than Merge Modules.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Karper
Sent: Thur
http://wix.sourceforge.net/releases
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Ratcliff
Sent: Thursday, June 26, 2008 14:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installing votive on Visual Studio Team
I didn't figure it would, but thought it was worth asking. :-) Thanks.
Chris
On Thu, Jun 26, 2008 at 5:18 PM, Jason Ginchereau <[EMAIL PROTECTED]>
wrote:
> The change applies only to WiX projects, and could not possibly affect
> escaping behavior in non-WiX projects.
>
> Most of the WiX projec
The change applies only to WiX projects, and could not possibly affect escaping
behavior in non-WiX projects.
Most of the WiX project code is shared between VS2005 and VS2008, including
this part.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christop
Thanks, Simon
I guess sourceforge isn't the place to get the current release. I didn't
notice the 2007 date on V3 after seeing the 2008 date on V2.
Jeff
On Thu, Jun 26, 2008 at 2:02 PM, Simon Dahlbacka <[EMAIL PROTECTED]>
wrote:
> >
> >
> > Yet I have Visual Studio Team System 2008 installed. A
>
>
> Yet I have Visual Studio Team System 2008 installed. Am I missing
> something?
>
Yes, you are using an old version that is pre VS 2008, get a newer one
instead from http://wix.sf.net/releases
-
Check out the new SourceFo
OK, I am redoing some of my installations to be in merge modules. Now, I
have no idea what I'm doing, so it's kind of learn as I go. I'm stuck in a
few spots, and was hoping someone out here would be kind enough to help me.
:-)
I am installing a .NET web application, which is why this gets compl
When I try to install wix-3.0.2925.0.msi I get the error message:
"Votive, the WiX project and editor package for Visual Studio, cannot be
installed because Visual Studio Standard Edition or higher is not installed"
Yet I have Visual Studio Team System 2008 installed. Am I missing something?
Tha
Thanks Christopher,
That is what I expected too (for install package to be smaller) but,
apparently, InstallShield is still running a tight ship and/or I am
still missing something important since my MSI is still slightly larger
than IS exe package and (I believe that) I did almost everything tha
Hello all.
I'm new to this list and new to Wix.
We have successfully integrated Wix3 into MSBUILD for two new development
projects.
We have an existing project that used Wix2 and has a few patches. We would
like to upgrade this to Wix3 and want to be able to generate new patches off of
our p
My memory is that a Basic MSI project with a bunch of exported InstallScript
functions will compile and get linked into a single DLL with a bunch of
exported functions like f1, f2, f3,f4 ectera. So the IScript runtime
penalty should only be once. If you used merge modules and had installs
Yep, that was it, thanks Jason!
High compression shaved of 10 Mb and I accounted for the remaining 10
MB. My billboard bitmaps took only 3MB but Custom Action Dlls, while
each smaller than half a megabyte, turned out to be numerous enough to
take up to 7 MBs.
I assume that a bunch of small DLLs t
This may seem like a silly question, but is this change global? Now my
output paths are exhibiting the same escaping behavior, for non WiX
projects.
Was this a change in 2008, or did your change have other effects?
Chris
On Wed, Jun 25, 2008 at 1:42 PM, Jason Ginchereau <[EMAIL PROTECTED]>
wrote
I also need a sleep command during setup. What is the WiX custom
action to sleep, i.e. delay operations for a certain period of time?
Thanks very much!
On Thu, Jun 26, 2008 at 9:46 AM, John Hall
<[EMAIL PROTECTED]> wrote:
>> Is there a way to do this?
>
> I think you'd have to write a custom actio
Custom Action scheduled after InstallFinalize do work. I have one that
invokes DLL exported function and, using __asm { int 3 } in my CA C++
code I get JIT debugger started.
I think your problem may be that you are expecting the action to start
the executable, while your action is just assigning o
The downfalls of receiving emails batched, and a batch coming in
before people start responding. Sorry everyone.
Cheers,
Bryan Rasmussen
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell serv
Here is the code:
"
I tried putting in a custom action that used the cmd.exe sleep command to fix a
problem with a service that needed to restart only to discover that not all my
deployment targets had the sleep command!
I later was able to abandon the sleep as we fixed the fact the service needed
to be restarte
Hi Bryan,
I don't know details how you get the value of AUTOPILOT property. If that's
you installation path - use custom action type 18, if you are getting it using
AppSearch - custom action type 50. Here is the sample of type 18 (Write.exe is
from [SystemFolder] on my Vista machine):
http
> Is there a way to do this?
I think you'd have to write a custom action. As custom actions go, this
would be a very simple one.
Just out of interest, why do you want to sleep during installation?
Regards,
John
-
Check out
I closed VS 2008 before installing new WiX version. The problem appeared
as I restarted VS, loaded solution containing the existing WiX project
(among other Custom Action C++ DLL projects) and then clicked on
project's Properties context menu.
I recreated the project from scratch and the problem i
Bryan,
I have a new how-to topic out for review that covers launching an application
based on a checkbox at the end of setup. I've included the text of it below.
Assuming your installer has UI, you can wire up the action in the same way (to
the Finish button), but simply omit the piece that tur
Would you be able to list some of the PUBLIC properties that would be
propagated and not needed/wanted? It would be nice to know what may
cause issues, and why. If the properties aren't used and don't affect
the certain installers, then setting EnableUserControl=1 may work well
for some developer
Bob Arnson a écrit :
Frédéric Viollet wrote:
Could someone please tell me which condition I should use to trigger a
custom action only on installations (initial installation and minor
upgrades).
This custom action must not be run on uninstall.
See http://msdn.microsoft.com/en-us/libr
You can try passing the high compression (-dcl:hi) switch to light, or setting
CompressionLevel="high" on your element. WiX by default uses a moderate
compression level which provides much faster builds but is slightly less
optimal. However, I doubt that increasing the compression level will ma
I have ported InstallShield (version 12) project to Wix 3. InstallShield
has msi embedded in exe and the whole setup.exe is 50 MB large. Wix
creates MSI with embedded compressed CAB which takes 70 MB.
20 MB is a pretty large difference! Am I missing something obvious or is
InstallShield compressio
I haven't been able to reproduce the problem with source control, though
several people have reported it. It's tracked as sourceforge bug 1977311. Any
further details you can provide will be helpful.
Do you notice the problem after just installing WiX, or do you need to open a
WiX project for i
Well i mean wait for a defined time.. sleep(milliseconds)
I have written a c# exe that gives a sleep of 30 seconds.But when i call it
from the installer using a CA,i see that the exe in the process list of task
manager for just 4 seconds and it doesn't hold/delay the installation
sequence for 30
Use a custom action to play some soothing music? Maybe turn down the LCD
backlight?
Or did you mean one of the following?
1. Wait for a defined time -- i.e. ::Sleep(milliseconds) or
Thread.Sleep(whatever)
2. Put the computer into standby.
I'm joking around, but you'll need to be more specific
Is there a way to do this?
--
View this message in context:
http://www.nabble.com/Induce-Sleep-in-the-MSI-script-tp18132204p18132204.html
Sent from the wix-users mailing list archive at Nabble.com.
-
Check out the new Sour
Hi,
I am new to Wix. I am trying to see some sample for GAC an assembly.
AssemblyApplication
String
Specifies the file identifier of the application file. This assembly will
be isolated to the same directory as the application file. If this attribute
is absent, the assembly will be installed
Hi All,
There is a CustomizeDlg in which i have a browse button linked to BrowseDlg.
The directory chosen for installation is in a property called
[_BrowseProperty]
What is to be done is
1. Check whether a folder,say "Folder1" exists in the chosen path. The
Installation should proceed only if "Fo
Just thought I'd shared this with you as I'm not
sure if it's expected behaviour or not.
I've been setting up a RadioButton on a UI...
So far so good however if I try to use Indirect="yes" for
the I always get the error trying to display
the UI...
The radio button group
Specifically I am trying to do this:
How should that be restructured to work?
Thanks,
Bryan Rasmussen
On Thu, Jun 26, 2008 at 9:47 AM, bryan rasmussen
<[EMAIL PROTECTED]> wrote:
> As per the subject line, it's just supposed to install and run. The
> user doesn't have to c
As per the subject line, it's just supposed to install and run. The
user doesn't have to click on the dialog to say that they want it to
run.
Thanks,
Bryan Rasmussen
-
Check out the new SourceForge.net Marketplace.
It's the b
55 matches
Mail list logo