Ping...
Appreciate all suggestions and pointers.
On Wed, Feb 8, 2012 at 11:08 AM, Sameer Arora wrote:
> Hi,
>
> I have a WiX 3.5 project that installs and starts a windows service and
> thereafter executes a custom action to configure the service using command
> line utility sc
I had a similar requirement, but not exactly. In my case
- config file was getting generated instead of being installed (it's more
like "data" file rather than config file)
- we needed to keep the file mandatorily during an upgrade/repair, but
remove it on uninstall.
Since it was a generated file,
Hi,
I have a WiX 3.5 project that installs and starts a windows service and
thereafter executes a custom action to configure the service using command
line utility sc.exe that ships with the OS.
This MSI can be used both for fresh install or major upgrade.
It uses custom dialogs to capture user i
If the requirement was to invoke elevation prompt for both install and
uninstall (be it in from Program and Features or through the Maintenance
mode) will this work?:
add this condition somewhere in the scope
Privileged
I understand "Admin privileges" may mean different from "Elevation" that
you
I need to ACL the installation folder so that only the user who is
installing or admins have access to the folder and its sub-hierarchy.
I have tried the following:
I came across a forum thread (
http://www.mail-archive.com/wix-us
did use
InstallUtilLib.dll to install the windows service.
But now we have switched to using ServiceControl and ServiceInstall WiX
elements.
On Sun, Aug 28, 2011 at 7:30 PM, Bob Arnson wrote:
> On 28-Aug-11 17:31, Sameer Arora wrote:
> > Why is UI sequence table missing/empty when
My scenario is that target for an advertised shortcut is absent.
If clicks the shortcut, Windows MSI triggers a repair with
parameters REINSTALL=DefaultFeature REINSTALLMODE=pocmus. As part of this
repair, the installation sequence seems to skip UI Execute sequence as I see
from the log:
Action s
Hi,
I have defined a component to cleanup a generated (not part of msi) file on
uninstall but leave intact on a major upgrade after reading this post
http://stackoverflow.com/questions/488620/wix-major-upgrade
REMOVE="ALL" AND NOT UPGRADINGPRODUCTCODE
With condition above, the file is le
nd
> then reinstall it. The service will then have the default credentials and
> will need to be reconfigured with the account, but you will at least get a
> successful repair. That's assuming you changed the service logon credentials
> after install.
>
> Phil Wilson
>
Suppressing the ICE worked.
Thanks much!
On Mon, Aug 8, 2011 at 8:53 PM, Bob Arnson wrote:
> On 08-Aug-11 20:47, Sameer Arora wrote:
> > If however, I change AllowSameVersionUpgrades to "yes" I am faced with
> > compilation error below:
>
> The ICE error is tryin
Thanks much.
Suppressing works great.
On Mon, Aug 8, 2011 at 8:53 PM, Bob Arnson wrote:
> On 08-Aug-11 20:47, Sameer Arora wrote:
> > If however, I change AllowSameVersionUpgrades to "yes" I am faced with
> > compilation error below:
>
> The ICE error is tryin
With the code below, if the product code changes but version does not change
at all (including the 4th element), I endup with multiple installations of
the same product since product code is different in each new MSI.
If however, I change AllowSameVersionUpgrades to "yes" I am faced with
compilat
k.
> Repairing the MSI before trying to uninstall would restore the missing
> files,
> if you have access to the original MSI.
>
> If you have customers that are deleting files in the Windows directory, it
> would be best to discourage them :)
>
> -Original Message-
&g
If one loses one or more installed files post a successful installation, the
uninstallation fails citing missing the missing file.
Also, if the original MSI that gets cached under
%SystemDrive%\Windows\System32 is lost, the uninstallation still fails
citing missing MSI.
Is there any way to uninsta
Hello,
Our WIX setup installs a windows service after asking logon account through
a custom UI dialog..
The service starts after installation succeeds.
Entire setup requires elevated privileges.
Hoping for any pointers regarding couple of questions:
*Question 1*
On attempting "Repair" from "Add
What am I missing ?
I would like the setup to launch my UI application after installation
completes successfully.
My .wxs files are modularized as:
*InstallSequences.wxs*
..
NOT
Installed
..
*CustomActions.wxs*
..
..
Intention is to launch the application once the instal
msi package will automatically get redirected to use 32-bit registry
> locations.
>
> Edwin G. Castro
> Software Developer - Staff
> Digital Channels
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> Please consider the environment before printin
Hi,
I need a way decide the registry path to write to based on the OS
architecture the installer is installing on.
E.g:
If OS is x64 bit
create a registry key under HKLM\SOFTWARE\WoW6432Node\MyCompany
otherwise write to
create a registry key under HKLM\SOFTWARE\MyCompany
To achieve this, I nest
Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
> -Original Message-
> From: Sameer Arora [mailto:arora...@gmail.com]
> Sent: 22 June 20
Hi,
I am totally new to WiX, Setup world and have just converted a Visual Studio
setup project to WiX using dark.
Now I need to redist an external MSI as part of our "converted" WiX setup.
Any pointers how I should go about this would really help:
- Are there any WiX redist samples I could lear
Am reading the tramontana tutorial - one of the best online I have to say.
Just need some clarification from WIX practitioners about custom actions (in
C# preferably):
- Can one perform custom actions during and post installation and
uninstallation ?
- I guess custom action post uninstall may not
21 matches
Mail list logo
