We'd like to provide a support phone number in our WiX-generated .msi in
a way that this phone number is visible to the end user when looking at
Support Details in the Software Control Panel of Windows. How to do
that?
Put a greater than '' before the equals in your condition?
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 Virtual Environment**
Integrated Environmental Solutions Limited.
Set the ARPHELPTELEPHONE property:
http://msdn.microsoft.com/en-us/library/aa367588(v=VS.85).aspx
-- Yan
-Original Message-
From: Markus Karg [mailto:k...@quipsy.de]
Sent: Thursday, April 08, 2010 11:49
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users]
http://msdn.microsoft.com/en-us/library/aa367588.aspx
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 Virtual Environment**
Integrated Environmental Solutions Limited.
Properties should be set after msiexec parameters. Move the /lv*!
install.log to before you declare your properties.
If that doesn't work try without the # in your properties or try
changing the Feature Level to something arbitrarily high like which
will be above your standard INSTALLLEVEL.
Hi all,
I would like to run a CA only on the first install. The CA shouldn't be
run on an upgrade. The condition i used is:
(NOT Installed) AND (NOT UPGRADINGPRODUCTCODE)
but it's not working, as the CA is still run on upgrade also.
I found the nice and detailed answer from Blair here:
Easy way to do it would be to condition the WelcomeDlg in the
InstallUISequence with NOT Installed AND NOT PREVFOUND.
Then you could make a new dialog (make the buttons a copy of the
VerifyReadyDlg ones so you get UAC shields where appropriate)
condition it with Installed AND PREVFOUND so it will
Hi,
I need some help in launching our Application correctly once the WiX MSI
installer has completed.
Currently I have the following setup:
(a) An IExpress Self Extracter executable. This has a manifest set to
RunAsAdministrator for UAC compatibility.
(b) The self-extracter then runs a
Hi,
Sorry to clarify - in my previous post, when I mentioned
RunAsAdministrator I meant manifested as requiresAdministrator .
Thanks,
Simon
On Thu, Apr 8, 2010 at 11:52 AM, Simon xmu...@gmail.com wrote:
Hi,
I need some help in launching our Application correctly once the WiX MSI
installer
Hi,
Sorry to clarify - in my previous post, when I mentioned
RunAsAdministrator I meant manifested as requiresAdministrator .
Thanks,
Simon
--
View this message in context:
http://n2.nabble.com/Problems-launching-application-after-install-as-non-elevated-tp4870137p4870177.html
Sent from the
Your temporary workaround sounds like the proper solution. Allow
Windows Installer to request elevation if/when required rather than
forcing it everywhere from the start. If you're using a stock WiX UI
your user will be prompted with a UAC shield on the VerifyReadyDlg
before the elevation request
Thanks! It works pretty well! :-)
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Donnerstag, 8. April 2010 11:27
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Support Phone Number
Hi,
Does anyone know if there any issues or even if its possible to run Wix 3.0
integrated with VS2010? We have a bunch of VS2008 projects with installers
written in wix 3.0. I now have to write an installer for a VS2010 project. I'd
rather just use one (stable) version than try and use v3 and
I have a strange problem. Following the directions in the WiX manual, I
added a ShortCut which is working well. Now I added a icon, but the
shortcut is not using it - it still uses the icon of the EXE! The
installation is per machine.
Icon Id=my.ico SourceFile=..\foo\my.ico /
Component
Publish Dialog=MyDlg Control=Next Event=NewDialog
Value=MyIIS6DlgIISMAJORVERSION = #6/Publish should work. If not,
(IISMAJORVERSION=#6 OR IISMAJORVERSION=#7) definitely works.
--
View this message in context:
On 4/7/2010 9:55 PM, Jeff Perrigo wrote:
I am trying to do an admin install of an MSI with a conditional feature and I
need the feature to be installed regardless of the condition.
As documented, admin installs install all features except those with
level 0.
--
sig://boB
On 4/6/2010 6:31 PM, Alex Ivanoff wrote:
3.5.1602 still no project/item templates in VS 2008 SP1.
There's no bug on that issue. Please file one with details.
--
sig://boB
http://joyofsetup.com/
--
Download
On 4/8/2010 6:58 AM, Rhodes, John wrote:
Does anyone know if there any issues or even if its possible to run Wix 3.0
integrated with VS2010?
No, WiX v3.0 doesn't support it. There are no breaking changes in the
core toolset, so I'd recommend v3.5 over trying to hack bits of it into
v3.0.
--
On 4/6/2010 5:23 PM, Neil Sleightholm wrote:
I have checked this again and using heat with the options -pog:Binaries
-pog:Satellites -pog:Content the referenced assemblies are not
included.
I thought they'd end up as Content.
--
sig://boB
http://joyofsetup.com/
On 4/7/2010 7:49 AM, Andy Clugston wrote:
WixIIsExtension.dll version: 3.0.5217.0
Try upgrading to WiX v3.0 RTM.
--
sig://boB
http://joyofsetup.com/
--
Download Intel#174; Parallel Studio Eval
Try the new
On 4/6/2010 1:04 PM, Michael Schlitt wrote:
I believe you have make something in the Component section point to a KeyPath
and if there is not something in the Component Section that points to KeyPath
then create a Registy Key that does this for you.
This occurs when the package doesn't
On 4/7/2010 1:16 PM, Andrew Ziem wrote:
My MSI installs an application called SideCIC.EXE. It needs to
initialize a Windows Event Viewer container which can be done if I run
'SideCIC.EXE /initialize'.
WiX includes the EventSource element to create event sources without the
need for fragile
We need to upgrade a preinstalled software. That software is very old
and knows nothing of MSI, Registry etc. We actually have to search all
local drives for the old EXE file and remove the surrounding folder. As
this is a time consuming task, this shall only happen if this is really
an update of
Look at the InstallUISequence of your built MSI (sort by sequence).
You'll see only MaintenanceWelcomeDlg, ResumeDlg WelcomeDlg sequenced
before ProgressDlg so conditioning the WelcomeDlg appropriately will
also skip all the dialogs it calls if it is skipped since the user never
clicks on the
Upgrading to the RTM (5419) did not help. Same issues.
Thank you.
On Thu, Apr 8, 2010 at 8:44 AM, Bob Arnson b...@joyofsetup.com wrote:
On 4/7/2010 7:49 AM, Andy Clugston wrote:
WixIIsExtension.dll version: 3.0.5217.0
Try upgrading to WiX v3.0 RTM.
--
sig://boB
Hi Pally,
Thank you for your reply. I have been testing this temporary solution and
it is working well. Do you know whether this is the recommended /
standard way of doing this?
I want to make sure that we don't get any surprises after we deploy the
software.
Thanks,
Simon
--
View this
Hi,
After a successful installation we currently launch our application using
the following custom action:
Property Id=WixShellExecTarget Value=[#MyApp.exe] /
CustomAction Id=LaunchFile BinaryKey=WixCA DllEntry=WixShellExec
Impersonate=yes Execute=immediate/
Is there a way to launch
Hi,
i have to install my application if another application found else i want to
give error message like ' Application is not found. Please install
Application'. I am using registrysearch to find whether the application is
installed or not but i do not know how to give error message is
I know this is not specifically WiX 3.5, but I have a custom action that
will run on XP 32bit, Windows7 32 and 64bit, but will not run on Windows
Server 2008 R2. I am using Msi.Lib - 7/14/2009 6:54 - ms sdk 7.0 when I
build the Dll. Which seemed to be the most recent version. If anyone
has
Hi Markus,
The Source (http://msdn.microsoft.com/en-us/library/aa369210) is saying:
Icon files that are associated strictly with file name extensions or CLSIDs
can have any extension, such as .ico. However, Icon files that are associated
with shortcuts must be in the EXE binary format and must
what i'd do is
1 - have a property APPFOUND with a default value false
2 - use Appsearch to set the property to something (anything) different from
false
3 - use a LaunchCondition that tests APPFOUND=false, with a suitable message
shown when the test is true
Condition Message=App is not
Afraid not, Content just includes icons, images etc (mainly useful for
web apps). I have checked this with 3.0 and 3.5. I feel this is quite a
big hole in the project harvester, is it worth a bug report?
Neil
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: 08
On 4/8/2010 4:54 PM, Neil Sleightholm wrote:
Afraid not, Content just includes icons, images etc (mainly useful for
web apps). I have checked this with 3.0 and 3.5. I feel this is quite a
big hole in the project harvester, is it worth a bug report?
You can try.g I don't think it's a bug
On 4/8/2010 11:08 AM, Xmun wrote:
Is there a way to launch two applications?
WiX provides the custom actions to launch one; if you want two, you need
to author those additional custom actions yourself.
--
sig://boB
http://joyofsetup.com/
On 4/8/2010 1:14 PM, Sam Domonkos wrote:
I know this is not specifically WiX 3.5, but I have a custom action that
will run on XP 32bit, Windows7 32 and 64bit, but will not run on Windows
Server 2008 R2.
Use Dependency Walker to see if the DLL has dependencies you're not
accounting for.
But there wouldn't be any project references as they are external
assemblies.
Neil
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: 08 April 2010 22:08
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] how to use heat to harvest VS projects
On 4/8/2010
Hi ,
I am getting an issue while uninstallation. There are some folders which are
copied onto user machine while installation, but its not getting deleted while
uninstallation of the package.
It is working on some user machine. I dig into the log files but couldn't get
any fruitful
On 4/8/2010 9:55 AM, Andy Clugston wrote:
Upgrading to the RTM (5419) did not help. Same issues.
I reopened the old bug. Please attach sample authoring and a verbose log
showing the problem.
--
sig://boB
http://joyofsetup.com/
Hi Everyone,
I've a specific requirement of checking whether a particular port is occupied
by a web application through Wix 3.0. I've written a custom action dll in C#
for this purpose and it returns ActionResult.Success and ActionResult.Failure
depending on Port Occupied or Not.
When
Code Snippet Updated :
Publish Property=IdentifierRegExPattern
Value=[IdentifierPortNumberPattern]1/Publish
Publish Property=Identifier
Value=[MTK_SHAREPOINT_WEBAPP_PORT]1/Publish
Publish Event=DoAction Value=ValidatePortNumber1/Publish
Publish
UPGRADINGPRODUCTCODE is set when you're being uninstalled during an
upgrade, so it sounds like the wrong condition. For example to force a
CA to run on a full uninstall only, but not when it's being
uninstalled because an upgrade is happening I use
REMOVE ~= ALL AND NOT UPGRADINGPRODUCTCODE]
I
Hi all,
I create a DLL Custom Action using C++, and It write log using WcaLog function.
But I seem it doesn't work.
This custom action is called, when the button is pushed as follows.
Publish Event=DoAction Value=ConfigureFeature1/Publish
When I scheduled the custom action in
Hi All
I've noticed that the MSI files created by WiX have some of their file
properties (e.g. Authors, Revision number etc.) set to values that
must be produced by WiX. However I'm uncertain how to go about
setting those values. For instance the Authors value is correctly set
to the name of our
Hi Xmun,
Check out the series of blog posts at
http://blogs.msdn.com/rflaming/archive/tags/UAC+in+MSI/default.aspx on
understanding UAC and MSI. There's a lot to take in (27 posts?), but
it's a worthwhile read :)
Sascha
On Fri, Apr 9, 2010 at 12:38 AM, Xmun xmu...@gmail.com wrote:
Hi
What's the proper way to set the custom action data to the value of the
checkbox control for a deferred custom action? Currently, it seems the value is
being set after the ExitDialog Action and after the custom action has executed.
thank you
--
View this message in context:
http://n2.nabble.com/conditional-installation-if-application-path-found-tp4872360p4875451.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Download
46 matches
Mail list logo
