Windows Installer only permits a component to install to a single
directory. If you have many directories you will have to author at least
one component per directory.
As Cullen says, it may be better in the long run to create one component
per file. As I recall, you cannot add or remove a file fr
If you have a service configured to run as an administrator, the
administrator's password is stored as an LSA secret in the registry (in
the SAM hive, as I recall). It is encrypted but the decryption key is in
there too. However, if someone is able to steal the SAM hive to crack it
offline - which
Bob:
The suggestion does not seem to be working. I have tried all of the
following combinations to no avail.
I have four properties defined in their respective CheckBox controls
(DEV_ENVIRONMENT, TEST_ENVIRONMENT, QA_ENVIRONMENT, & PROD_ENVIRONMENT).
What I am trying to do is control which on
They had started again exactly at eleven. Betty
came to him in the librarya few minutes before nine.
She should be in Paris tomorrowmorning, England
tomorrow night.
The road by which we have come is the better one,
she continued.
If shecould get to England they couldnt bring her
back, could
I believe this is part of the VisualStudio 2005 extensibility SDK. I
didn't have it on hand so I searched around for it on google (search for
: ProjectAggregator2.msi download) and found it. Here's one place you
can find it (it's in the archive):
http://www.sapphiresteel.com/Steel-Download-and-Cha
Hi,Was excited to try out the new release but found a bug right away. After installing the Votive v3 latest build, I couldn't create a new project in Visual Studio. In the New Project dialog, under Wix, the project template list is empty. Is there some way to manually add the templates so I can
When I install an msi, I am keeping a log like so:
c:\>msiexec /i foo.msi /l* foo.log
The problems is that when I open foo.log, it turns out it's in UCS-2 Little
Endian encoding. Chaning the encoding in .NET is trivial, but we have a
legacy app that needs to append to the log file, and it's in
Hello,
I have just started using Votive2-2.0.4415.0 and Visual Studio 2005.
In order to add the UI features to the installer, you need to supply
the '-loc' parameter (and associated value) to the 'light' linker. I
have been able to do this successfully from the command line. I have
not found a w
Salut,
trying to create my first setup using WIX. My software does not support
Windows 95. In the http://www.tramontana.co.hu/wix/lesson1.php#1.4 wix
tutorial I found the following lines:
Version9X =
400
Version9X = 400 AND
WindowsBuild =
Unfortunately I get the message "Operatin
In Wix, and with MSI installers in general I believe, the condition has
to be *true* to install. So in these cases, you will *only* be able to
install on Windows 95. I believe you want to change your '=' to 'NOT'.
-Matt
-Original Message-
From: vbtricks [mailto:[EMAIL PROTECTED]
Sent:
Salut,
thanks. I changed it to
Version9X =
400
and it gives me no error anymore. Next time I get the chance to test it on
Windows 95 I'll see if it works completely correct ;)
Stefan
Matthew Janulewicz-2 wrote:
>
> In Wix, and with MSI installers in general I believe, the condition has
The good news is that you're not a complete n00b. :) Votive v2 does not have
support for passing in command line parameters to candle/light. However, all
you have to do is add the .wxl file to the project and then it should
automatically pass in the -loc parameter.
I would recommend that you insta
When you installed Votive3.msi, did you have any instances of
Visual Studio 2005 open? If so, please uninstall and reinstall without them
open. If not, please let me know so I can look into it further.
Thanks,
Justin
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of
Sorry about that. I forgot to put it up on the web site. See my blog for
where you can download it (I've attached it to the blog):
http://blogs.msdn.com/jrock/archive/2006/09/18/761044.aspx.
Justin
-Original Message-
From: Torsten Rudnick [mailto:[EMAIL PROTECTED]
Sent: Monday, September
Hello:
Has anyone considered using name-based (e.g. URL-based) UUID's, as
specified in RFC 4122, to reduce the tedium of creating Windows
Installer packages with WIX? This would be especially helpful for
component GUID's. Maybe the Component element could have an optional
GuidUrl attribute,
Derek Cicerone has blogged on this, see here:
http://installing.blogspot.com/2006/09/automatically-generating-componen
t.html. I don't know if there are any plans to implement this.
Neil
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matt
Campbell
Sent:
Let's begin with the facts:
I'm a relative wix n00b and I'm running Wix 3.0.2015.0 (under Vista RC1 x64 if that matters)
Due to the lack of samples I'm having trouble with creating a shortcut in my wxs file.
My first attempt:
Re: [WiX-users] UCS-2 Little Endian encoding of MSI Log file problem.
Solution:
Someone replied...the answer was to use the MultiByteToWideChar function to
convert from ANSI to UCS-2 before appending to the file.
Thanks!
Roy Abou Assaly wrote:
>
> When I install an msi, I am keeping a log like so:
>
> c:\>msiexec /i foo.msi /l* foo.log
>
> The problems is th
Hello All,
Please, i am having a problem here, is there a way to disable a radiobutton from a radiobuttongroup based on a property?
I have some registrysearches that set properties in the start of my setup. Based in this properties the user must have some options enabled or disabled in the ra
WIX-Users,
I
have a shortcut which isn’t generating anything in where I expect it to
be:
I’m
using WIX v 2.0.4117.0, if that helps. Is there anything I’m doing
wrong?
--
Frank
Hsueh | [EMAIL PROTECTED]
-
Simon,
I am new to using WiX too, but I just got some help from the list, so
I think I will try to give back.
I think your first attempt is really close.
I think that all you need to add is the following line
after your
and before your
"ProgramMenuFolder" is a special (reserved/magic) name
Thanks for the email. Yes, this problem has been reported a couple of times.
The issue is that our PLK (Package Load Key) hash no longer matches our
registration since I bumped the version to 3.0 and changed the package GUID.
I'll get this fixed for the next drop (which should be on Wednesday).
Unf
I am having the same problem too, but no I didn't have an instance of Visual
Studio Open at the time of Installation.
Justin Rockwood wrote:
>
> When you installed Votive3.msi, did you have any instances of Visual
> Studio
> 2005 open? If so, please uninstall and reinstall without them open. I
I have since found out the problem. It's a PLK (package load key) issue and
I'll have a fix for the next drop. Basically, since I revved the version
from 2.0 to 3.0, the PLK hash no longer matches. Watch for the next drop.
I'll also drop a line to wix-users and wix-devs to let people know that the
I am having trouble getting an install condition based on
land ID to work… I have consulted the WIX doc’s and my
implementation seems to be correct but since it’s not working I am
missing something.
We are building a Multilanguage MSI for a small product and
we wish to only allow instal
Frank Hsueh wrote:
"http://server/path/file.html" />
I’m
using WIX v 2.0.4117.0, if that helps. Is there anything I’m doing
wrong?
MSI shortcuts must point to a file or a directory (or be to an
advertised feature). You need to write a .url file and create a
shortcut to
gboreki wrote:
> Please, i am having a problem here, is there a way to disable a
> radiobutton from a radiobuttongroup based on a property?
MSI doesn't support that. In MSI terms, the radio button group is the
control and the radio buttons are non-control children. It's annoying
and not intuitiv
Mike Dimmick wrote:
> If you must use a service, install the service as manual start and use a
> element under to allow the service to be
> started and stopped by a non-privileged user. Then start the service to
> perform the upgrade and stop it when you've finished (or perhaps have it
> stop its
Jeff MacDuff wrote:
My condition statement is
formatted like this:
Re: [WiX-users] Feature List conditional control
david adams wrote:
If I set the Feature @Level="1" and use Condition #1 or #4 in an attempt to
"disable" the other three, then all four features stay at level = 1 in
CustomizeDlg (i.e. feature set for install).
If I set the Feature @Level="0" and use either Condition #2 or #3 in an
attem
It’s being set through a custom
Action:
Which is basiccly this code
(snipped a bit)
LANGID langId =
::GetSystemDefaultUILanguage();
TCHAR
szLang[10] = {0}; _itot((UIN
Jeff MacDuff wrote:
It’s being
set through a custom
Action:
What does a verbose log show it's being set to? More important is the
timing; make sure the CA is sche
I will run a verbose install tomorrow and
see what the return is.
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Monday, September 18, 2006
9:33 PM
To: Jeff MacDuff
Cc:
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Problem
with install condition based on lang ID
Hi all,
With the major update to Votive and Derek's enhancements to the core WiX toolset, there for sure is a lot of new stuff that needs to find its way to SourceForge.
However, there seem to be some issues that still need to be resolved (for example, Votive not loading). That's why I am wai
Also forwarding my
query to the right group.
Take
Care
Anirban
From: Anirban Basu
Sent: Tuesday, September 19, 2006
11:24 AM
To: Windows Installer XML
Subject: RE: issue around
INSTALLDIR
Hi,
Have not got
response in this. so re-sending.
Take
Care
Anirba
Frank Büttner wrote:
> I have zip the files with 7 ZIP now it is only 552KB, because it is to
> big for SF I post it here.
>
Well, the "good" news is that I was able to duplicate your bug. Bad news
is that I'm not sure what the problem is. I can pinpoint it to the code
that parses the .manifes
How do you measure the number of successful installs?
PS: Sorry for the mess, I'm cleaning up right now and this next build should
be much better.
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Frederik
Carlier
Sent: Monday, September 18, 2006 22:48
To:
37 matches
Mail list logo