> From: Bob Arnson [mailto:[EMAIL PROTECTED]
>
> J. J. Farrell wrote:
> > At the moment I'm setting these SetupAPI parameters to
> > NULL. I'm guessing from Bob's message that I can solve
> > this problem by passing a handle to the Installer UI
> > window instead of NULL. Does this sound right?
I have dialog pushboxes that are suppose to be disabled until someone scrolls
to the end of my End User License Agreement. Is there a way in Wix to
condition such an event?
--
View this message in context:
http://www.nabble.com/Text-Field-scrolling-to-end-tf3043718.html#a8460898
Sent from the
When I added DIFxApp to my installer, I can no longer use that installer
to install my app on Windows 98. I know why this is happening. That is,
DIFxApp only supports Win2K and newer. However, I have the components
that have the Driver* attributes made conditional, but this doesn't keep
the actions
You are correct sir...that should do it. In version 3 of WiX however you
would use heat.exe
On 1/19/07, Dhaval Patel <[EMAIL PROTECTED]> wrote:
Use tallow.exe, I believe. It should be able to create a fragment for all
those files that you can use within WIX (I have never used it for files, but
Use tallow.exe, I believe. It should be able to create a fragment for all
those files that you can use within WIX (I have never used it for files, but
it worked like a charm for a huge registry entry I had to do on one of my
projects recently).
Again, just follow the tutorial for using tallow.exe,
The code does not require VS2003. The .vcproj projects are totally out of
date. Everything is built from NAnt.
From: Shaun Wilde [mailto:[EMAIL PROTECTED]
Sent: Friday, January 19, 2007 12:44 PM
To: Rob Mensching; Matthew Janulewicz; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] xmlf
I see - an easy fix would be to choose the DOM based on an attribute that we
can set (defaults to current name) and then if necessary one can add a
prerequisite to the installer.
I'd look at it myself but the code seems(?) to require VS2003 and I just don't
have that anymore.
From: [EMAIL PR
Hi All,
One way of solving this is to invoke Taskkill passing in the exe name via a
custom action. This CA can be invoked before remove files.
Here's more on TaskKill
http://commandwindows.com/taskkill.htm
It is better to check if the status of the exe is running, while calling
taskkill to kill
Actually sending to the appropriate list.
Hi there,
I was wondering if any of you could share some insight into this problem
we just came across ...
We have a custom action (MsiProcessDrivers) that processes driver
packages to install them onto the system. It is defined to run after the
Our dll's are strongly typed (I think that's what its called). So we
can't have dll's of different versions talking to each other. What is
the best way to apply a hotfix for when you only need to replace a
couple files. We can rebuild the new dll's to be the same version as
the old ones, but how
Well, the ICEs are failing. Those come with the MSI SDK. So it is possible
the ICEs would work better if we upgraded them to the latest... assuming we're
not already running the latest. Do you want to try to track down the latest
*.cub files and see if they work better?
-Original Message
Hello everyone,
I want to install both the x64 and the x86 version of an executable on the
harddisk, no matter if the machine is x86 or x64. But I only want to create
one start menu shortcut for the app, the one that is appropriate for the
target OS where the msi gets installed. How Do I go about
Yeah, there is a bug open I think , that notes the XmlFile uses the old MSXML.
K chose that old MSXML because it is distributed widely and makes for a
relatively safe dependency. It'd be nice to use a newer XML Parser but we
wouldn't be able to guarantee it would always be available.
I guess
It's ResolveSource that initializes the SourceDir (cased correctly)
property. An alternative is to use the OriginalDatabase property, the
full path to the MSI file, and parse the directory name from it. Is
SOURCEDIR a Wix thing?
Phil Wilson
From: [EMAIL PROTEC
Don't worry about it, I figured it out. I was trying to make sure that
the installer did not add any registry entries. This MSI is not for a
complete program, simply to update certain files in the web source of an
existing project; therefore the registry entries are useless and
actually make my lif
Even if it completely covered the buttons, the dialog would still receive a
refresh for the control...it doesn't make sense that it would disappear.
On 1/19/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
Patrick Steele wrote:
Thanks anyway Bob, I did end up splitting the one dialog into two dialog
Patrick Steele wrote:
Thanks anyway Bob, I did end up splitting the one dialog into two
dialogs and that worked. I don't know why the radio buttons kept
disappearing, except that possibly closing the balloon popup does not
cause a dialog refresh?
If the balloon completely covered up the butto
Now that I've got the MSI set to not create an ARP entry, any ideas on
how to make sure no registry entries are created on install?
Thanks again, Ian.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.
No conditions in the radio group:
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 18 January 2007 16:46
To: Patrick Steele
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Refresh on next button
Patrick Steele wrote:
If the
Thanks anyway Bob, I did end up splitting the one dialog into two
dialogs and that worked. I don't know why the radio buttons kept
disappearing, except that possibly closing the balloon popup does not
cause a dialog refresh?
From: Bob Arnson [mailto:[EMAIL PROTECT
Patrick Steele wrote:
No conditions in the radio group:
Hmmm. Sorry, no ideas coming to mind...
--
sig://boB
http://bobs.org
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and y
Dhaval,
Thanks for your help.
My ASP.NET app has 150+ ASPX files. Is there a way to use wildcards in
WiX to include all files as one line (*.aspx) or do I have to list all
files separately as elements?
-Oleg.
From: Dhaval Patel [mailto:[EMAIL PROTECT
Just a follow up to that... it didn't work, seemed to, but after a
closer look it didn't.
From: Levi Wilson [mailto:[EMAIL PROTECTED]
Sent: Friday, January 19, 2007 10:25 AM
To: Ian Couper
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Have anoth
Yes, you're right. It works now.
Remove on both was just a desperate attempt to make it work. I've put
it back to remove on uninstall now.
On 19/01/07, Levi Wilson <[EMAIL PROTECTED]> wrote:
> I think the @Name attributes need to match up. Also, why are you removing
> on "both"? Don't you want
I'm not sure what you mean...which registry entries?
On 1/19/07, Ian Couper <[EMAIL PROTECTED]> wrote:
Now that I've got the MSI set to not create an ARP entry, any ideas on
how to make sure no registry entries are created on install?
Thanks again, Ian.
K, Thanks.
From: Levi Wilson [mailto:[EMAIL PROTECTED]
Sent: Friday, January 19, 2007 9:45 AM
To: Ian Couper
Subject: Re: [WiX-users] MSIs without Add/Remove entry, Possible?
Btw, don't forget to add a CC to the wix-users email address too so
everyone sees
Would be in your .wxs file.
On 1/19/07, Ian Couper <[EMAIL PROTECTED]> wrote:
Sorry, I am a n00b, Does this go in the XML file? Or in the command
prompt when running the MSI? Sample would be helpful…
--
*From:* Levi Wilson [mailto:[EMAIL PROTECTED]
*Sent:* Fri
Set ARPSYSTEMCOMPONENT to 1?
http://msdn2.microsoft.com/en-us/library/aa367750.aspx
On 1/19/07, Ian Couper <[EMAIL PROTECTED]> wrote:
Just wondering if there is an easy way to create an MSI that will not add
an entry into Add/Remove Programs. Currently I have all the components
listed as "Per
Just wondering if there is an easy way to create an MSI that will not
add an entry into Add/Remove Programs. Currently I have all the
components listed as "Permanent" then I can run an uninstall after the
MSI runs, which will keep all the files/directories, but will remove the
registry entry and th
Hi Rob
That tool helps a lot it seems that local-name() is an unknown method - I
assume it is using an old flavour of the XML DOM.
Shaun
From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL
PROTECTED]: Fri, 19 Jan 2007 01:45:35 -0800Subject: RE: [WiX-users] xmlfile and
nam
I think the @Name attributes need to match up. Also, why are you removing
on "both"? Don't you want it to be @Remove="uninstall"?
On 1/19/07, Antony Walmsley <[EMAIL PROTECTED]> wrote:
I'm using the following code to configure a service :
That works, Rob. Thanks.
If others get the same problem and use Visual Studio for building, you can
find the setting under Advanced... for Linker: Suppressions>"Suppress
MSI/MSM validation".
It bothers me, though, to suppress validation of the msi. So now I'm looking
forward to Vista Service Pac
I'm using the following code to configure a service :
The installation is fine but when I uninstall I can still see the
entry in the list of services. The executable has been uninstalled.
I'm using 2.0.4611.0.
--
I have serious issues with suggesting that developers should write
VBScript/Jscript CustomActions. Script CustomActions are only viable in highly
controlled environments. I would never recommend that an ISV release a product
that contains a Script CustomAction for distribution.
I've had many
I've had lots of issues with the XML Pattern stuff with namespaces. I
eventually wrote a little jscript that let me test my pattern until I finally
got it right. Then I dropped it in with variables and boom:
if (2 > WScript.Arguments.length)
{
WScript.Echo("Must specify both the file and t
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike Dimmick
Sent: Thursday, January 18, 2007 5:32 PM
To: 'Ben Sion'; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WiX and PocketPC installations
...
>
> I imagine that you should use a Registry
Sorry I should have said I am using WIX V2 (not 3) and
I have the correct escaping as you can see in my example.
Unfortunately web.config don't tend to have any namespaces
defined in them and I don't have issue with those files - its an xml
file that has namespaces defined within it that is ca
It looks like the ICE validators are having a problem on your Vista box. What
happens if you add "-sval" to the light.exe command line?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Morten
Klostergaard
Sent: Friday, January 19, 2007 1:05 AM
To: wix-us
Sorted, Thanks Bob.
On 19/01/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
> Antony Walmsley wrote:
> > Is the browse button meant to work using WixUI_FeatureTree?
>
> Yes but the feature must have the ConfigurableDirectory attribute set to
> a public (all uppercase) directory.
>
> --
> sig://boB
> ht
I've just installed Vista, Visual Studio 2005 and latest WiX (version
3.0.2512.0). When building a WiX-project I get the error:
An unexpected external UI message was received: The installer has
encountered an unexpected error installing this package. This may indicate a
problem with this package.
40 matches
Mail list logo
