Well,
after many weeks of work, I've finally checked in Votive v3. It is now
available after any build >= 3.0.2115.0. You can download it from http://wix.sourceforge.net/releases/3.0.2115.0/Votive3.msi.
For details about what is in the new version, you can find
out on my blog. It also h
Thanks
Saranath
_
From: Saranath Aravamudhan
Sent: Friday, September 15, 2006 2:36 PM
To: Windows Installer XML
Subject: custom actions
Hi-
Can you please let me know how to restrict custom actions to run only during the installation an
I do something quite similar as
well. We use nant for our builds, and in the build file I set an
environment variable, then use it in the wix file. Src=""
I wasn’t able to use the var. for some reason I had to set the variable
to an environment variable before I could access it.
So
Reggie,
From what I've seen, the general guidance is to keep your components as
small as possible. If, for instance, you found a bug in one of your source
files, but had all source files in one component, your patch or upgrade
installer would have to include all of the files in that co
We've been using Wix for some time now and recently got around to cleaning
up our wix files. As we are adding samples and source code to the
installer, I find it hard to believe that I can't make a single component
include all my source files. As I understand it, a component should be
anything th
I have a few random wix questions below, that I wondered if anyone could help with.
Thanks!-Tina
1. How do you determine if an existing Wix code file is written for Wix 1.0, 2.0, or 3.0?
2. Is there any way to specify a default web page when creating a WebSite using the WebSite n
I've just posted my last 3 blog posts:
Addition of two new tools to WiX for transform (Torch) and patch creation (Pyro):
http://installing.blogspot.com/2006/09/torch-and-pyro.html
Ability to auto-generate safe component guids (limited to single-file components):
http://installing.blogspot.com
Is there a way to conditionally manage the Feature List?
I have a dialog that populates a set of properties. Depending upon those
properties, I would like to conditionally hide / disable specific feature
options on the Customize dialog.
So far, I have gotten the conditionals working within the
Windows Installer 3.0 the first version which supports it. It is mentioned
here, too:
http://blogs.msdn.com/windows_installer_team/archive/2006/06/27/648447.aspx
(see rule 45 LUA patching)
Regards,
Martin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
I did some more digging and found out that:
(1) Our .wxs does use the ServiceInstall element, with values for Account and
Password provided via external octopus-driven config;
(2) Despite specifying these values, the service still runs as "SystemLocal";
(3) I'm not sure what password to specify
Did you use votive.msi or votive3.msi? The votive3.msi has a brand new
Votive that you'll probably want to use if you do use Votive. It's got all
sorts of new stuff and a lot of bug fixes. I think you'll find that it's
much more usable than votive2.
Justin
-Original Message-
From: [EMAIL
I had a similar problem about a month ago.
I think many things can cause this, but in my case I was trying to create a
website and did not have an IP address tag for it.
-Matt
From: Peter Stokes
[mailto:[EMAIL PROTECTED]
Sent: Friday, September 15, 2006
2:47 AM
To:
wix-u
In this particular customer case - nope, admin credentials couldn't be on the system or in the hands of the restricted user. I suggested that the credential be written to the system in some obscure, highly encrypted fashion during the initial install (which had to be done by an Admin), then used i
I'm finding that the key is only deleted if it's empty: it has no
values, and the default value is not set. This is both using your
example, and using an Action='createKey' element to
explicitly create the key that you're interested in, as follows:
I suspect this is an underlying issue
On some computes I got undeleted registry values, while on others all
registry is cleaned.
I suppose that MSI somehow counts references to the registry keys and
values that it writes and remove them when ref count is 0.
If I am right where it stores that reference counts?
Best regards,
Peter G.
WIX Version: 2.0.4415.0
Problem Summary: How to prevent pre-existing
registry keys from being removed during uninstall.
I’m still quite new to
WiX so please bear with me. I am trying to understand a scenario.
I am going to install an
application that will create some registry entries
Hi
I'm using version 3.0.2015.0 of Wix and am getting the following message
when I light the wixobj.
error LGHT0132 : The assembly file 'blah.dll' appears to be invalid. Please
ensure this is a valid assembly file and that the user has the appropriate
access rights to this file. More informatio
Bob has added support to WiX 3 for custom event sources, but I don't think
the custom log is in there yet. It is on the list.
Luckily, both event logs and sources are simply a bunch of registry keys.
This is bread and butter for WiX/MSI, so it is not difficult to implement
this natively with n
hi
Can anybody provide an working example of using the ServiceInstall element
including the custom actions. I have tryed but cannot get it working. I can
create the msi but it fails. If I had a simple one that worked, I might be able
to find where I'm going wrong
(see Topic "ServiceInstall e
Hopefully you haven't already distributed the first MSI. If so, you might have a problem. You need to set the NOT UPGRADINGPRODUCTCODE condition in the original MSI (the one you are upgrading now). When you upgrade an existing MSI, the cached MSI is called to perform the uninstall, the new MSI d
Hi Anton,If you had used tallow, it might have indiscriminately picked up some files which you might not have expected. Try performing an administrative install on a test machine and verify if the files that are included are really the ones that you need. If not, check the wxs files and fragments i
roxana wrote:
>
> the installer gives me the well known error. I don't understand why MSI
> doesn't consider the Users group as a well known sid, for this seems to
> be the problem...
>
AFAIK Windows Installer only knows the SID for the Administrator and
Everyone. If you want to use other SID
Simon Burgess-2 wrote:
>
>
> GenericRead="yes" GenericWrite="yes" />
>
>
>
>
> But now, the service does not have enough permissions to start, not least
> because setting the permission as I have done above gets rid of all
> existing
> permissions on that director
Today I switched to the latest version of votive from yesterday. Now it
is not possible to add new files to the WiX project. There is no
template available. A bad workaround is to add an empty text file and
rename it to example.wxs.
Additional I am not be able to create a new WiX project in VS 2
Rene Hollan wrote:
>
> I've searched but can't find the Wix magic (if there is any) to install a
> service to run as a particular user. Can anyone point me in the right
> direction?
>
Check the "Account" and "Password" attributes of the ServiceInstall element.
http://wix.sourceforge.net/manual
Hi,
You might use a special user account with just enough
rights to install your application, with just the correct amount of rights in
the registry.
Then run the service described on this
user.
By adding impersonation tricks you might be able to
switch to the user context and use the HKCU
Hot on the heels of my last issue I have a bigger issue ...
I have two separate msi's which both create a website both need to run on port 80 and have different host headers.
Each installs fine on it's own but when I install one after the other I get the following error in the trace log:
Co
There's already a bug in the database at
http://sourceforge.net/tracker/index.php?func=detail&aid=1515154&group_i
d=105970&atid=642714. Submitted in June.
--
Mike Dimmick
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Crouch,
John
Sent: 15 September 200
Folks,
Am I using the 'Permanent' attribute incorrectly in the XMLFile Element?
I have,
This gives a Linker error
"C:\Documents and Settings\crouchjc\Desktop\Wix_Sample\myDemo.msi :
fatal error LGHT0010: There was an error importing table: XmlFile with
file: C:\Documents
and Settings\crouchjc\Loc
On Fri, 15 Sep 2006 13:07:50 +0700, Anton Filippov wrote:
Anton,
> How I can make installer smaller?
> My all files required 4mb space on hdd, but .msi file have size of
> 8mb!
There can be many reasons for that that we can't decide from here, not knowing
your actual setup. But one usual proble
Bob Arnson schrieb:
>>
> Interesting. It's binding at that point. Can you build any merge module?
>
Yes the sample that comes with WiX will build. But my own will fails:(
smime.p7s
Description: S/MIME Cryptographic Signature
---
31 matches
Mail list logo