>> And then I end up with the following folder structure:
>> C:\Inetpub\wwwroot\MyApp\v2.0.0\bin
>> C:\Inetpub\wwwroot\MyApp\v3.0.0
>> It seems that the bin folder doesn't receive the new value of
INSTALLLOCATION
>> so it uses the previous value. Any idea as to what is causing this
Interesting, I don't know anything about that kind of set up. I'll have to
look into it.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Monday, July 10, 2006 6:55 PM
To: [EMAIL PROTECTED]
Cc: Albert van Peppen; Wix-Devs; wix-users@lists.
Rafuse Robert wrote:
> The target machines have two hard drive partitions, C: and E: and we must
> install components into several folders on both partitions. We also need to
> install some components to Windows system areas, but not in the standard
> folders that seem to be supported by WiX (for
Rob Mensching wrote:
> [robmen] I truly hope it won't come to that. Creating a separate project
> would essentially fork the development of the WiX toolset.
It shouldn't. I assume Frederik was talking about something like the
NAnt-Contrib project. It serves the same purpose as an incubator or l
> I'd love to be able to contribute to WiX (in particular
> MSBuild support and Votive) but the hoop-jumping
> required to complete the assignment agreement totally
> put me off.
I know what you are saying here. The assignment agreement has been
something I've been arguing against since the begi
> I think it would be worth creating a space where people
> can contribute their own additions to WiX that are of
> signification value but did not make it through the legal
> process. A WiX-contrib project, or something like that.
[robmen] I truly hope it won't come to that. Creating a separat
inline
From: Wilson, Brad
[mailto:[EMAIL PROTECTED]
Sent: Monday, July 10, 2006 1:57
PM
To: [EMAIL PROTECTED];
wix-devs@lists.sourceforge.net; wix-users@lists.sourceforge.net
Subject: RE: [WiX-devs] WiX
v3.0.1828.0 Overridable attribute causing buildbreak.
Thanks for the
In WiX 3.0, !(loc.Variable) is the proper syntax for a localization variable
(the dollar sign is deprecated).
The [ProductName] syntax is not substituted until the MSI package is
installed. This is perfectly find, just note that Windows Installer handles
the substitution, not WiX (this is a commo
that was it. that's awesome.
thanks for the quick reply.
From: Derek Cicerone
[mailto:[EMAIL PROTECTED] Sent: Monday, July 10, 2006
6:24 PMTo: Wilson, Brad;
wix-users@lists.sourceforge.netSubject: RE: [WiX-users] language
specific wixlibs
You didn’t specify a
culture for light to
You didn’t specify a culture for
light to use, so it didn’t load any localization strings from the library.
Since wix libraries may contain multiple languages of localized strings, the
culture is necessary to pick one. In this case, you’d probably want
“en-us”.
Derek
From:
WiX 2.0.4305
Sorry if this is a stupid question... I've spelunked through the SourceForge
mailing archive, as well as the tutorial, but can not find any concrete
examples that seem to address the type of setup I am attempting (or maybe
they do and my only cursory understanding of the Windows Insta
This is probably the sort of thing best handled by a bootstrapper. Do a search on the archives for info about it.
-Francis
On 7/8/06, X Y <[EMAIL PROTECTED]> wrote:
Hi All,I am new to wix and was wondering if there was anexample out there that does the following:
1. Detect .NET (found in tutor
Rob,
I'd love to be able to contribute to WiX (in particular MSBuild support
and Votive) but the hoop-jumping required to complete the assignment
agreement totally put me off.
Why the requirement for us to print off and post a piece of paper to
Microsoft? All other open source projects I've work
Crouch, John wrote:
> My votive2.msi did not install a WixUI_en-us.wxl file - Is the tutorial out
> of date?
No, it's the Votive installer that's out of date. Justin and I have a
revamp of the installer on our plates, but it'll be a bit before that
happens. In the meantime, just download the bin
Title: WixUI_InstallDir problems
Nordvik, Christer wrote:
And
then I end up with the following folder structure:
C:\Inetpub\wwwroot\MyApp\v2.0.0\bin
C:\Inetpub\wwwroot\MyApp\v3.0.0
It
seems that the bin folder doesn't receive the new value of
INSTALLLOCATION so it
Frederik Carlier wrote:
> I think it would be worth creating a space where people can contribute
> their own additions to WiX that are of signification value but did not
> make it through the legal process. A WiX-contrib project, or something
> like that.
>
So go ahead and create it.
> I still
I think it would be worth creating a space where people can contribute
their own additions to WiX that are of signification value but did not
make it through the legal process. A WiX-contrib project, or something
like that.
I still think the "single copyright owner" argument is void; anyone is
fre
Thanks for the suggestions on cleaning up my wxs
file. I try to be efficiently lazy so that certainly
helps.
I added the stuff when I first
started working on this because I wasn't seeing any entries in the
LanuchConditions or AppSearch tables when including the wixlib that clearly
had
Derek,
Sorry to have forgotten to give the wix version I'm using; it is the
3.0.1821.0
I saw one other thing: "[ProductName]" is not replaced by it's value.
Thanks,
Laurent
Derek Cicerone a écrit :
> Localization strings are not evaluated during compilation. Something else
> is going on here. L
0. I think there
is a great opportunity to create a WixManagementExtension for v3. It
would be like the other WiX v3 extension. I wouldn't try to add it to WiX
v2, the improved v3 platform makes it far easier.
1. We talked about
writing an Event extension in the past. As you noted,
WiX version being
used: 3.0.1828.0
It appears that
light.exe is failing to parse the elements that are
included in wixlibs. The following is an example of a generated wixlib
that i'm trying to include in an install
(Feature_Designer.wixlib):
http://schemas.microsoft.com/wix/2003/11/l
Adding wix-users to this topic – I just
noticed it was sent to wix-devs. Please only use wix-devs for discussions
of code and other internals of the WiX toolset, all discussion about using the
toolset should go to wix-users.
It’s not necessary to have this
authoring:
Localization strings are not evaluated during compilation. Something else
is going on here. Laurent, could you please tell us what version of wix you
are using?
Thanks,
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Simoneau
Sent: Monday, J
On Mon, 10 Jul 2006 15:39:26 +0200, Crouch, John wrote:
John,
> My votive2.msi did not install a WixUI_en-us.wxl file - Is the
> tutorial out of date?
Hopefully not, although I have to admit, I never tried Votive (I don't use
Visual Studio).
> I suspect the wxl file so if that is the case can
Looks like I saved up all the legal questions for the same day. Again, I'm
not a lawyer so if you want real answers to these questions you need to talk
to your lawyer. I'm just passing on what I've heard about the topic.
1. As far as I know, if you make a change to any of the files in the WiX
t
First, if you have a patch to the code, please start the discussion on the
wix-devs mailing list about that patch. There should be no confusion about
that. We talk about the code on wix-devs.
Now, Pedrum is still waiting for an answer for his last patch... but I'll
get to that (hopefully, this
Not really. Tallow pulls a bunch of VB6 properties, and additional registry
info, which creates additional issues, like possibly blowing up VB with an
uninstall.
In this case the MSI created by VS.NET only conatins those keys necessary to
install the single object.
--
View this message in con
A dependency issue seems most likely in the circumstances. What happens if
you install the service but don't attempt to start it during the
installation? Does it start manually from the services applet? If it does
you know that the account is fine but something like a dependent Dll or
assembly is m
Another place to look is in the .Net 2.0 Bootstrapper and the MSBuild
GenerateBootstrapper task. With a little help from Google, it is
possible to find information on using the 2.0 bootstrapper with any old
generic MSI. By referencing the correct "package", one can create a boot
strapper that will
I agree I don't mind sacrificing my own rights, but I can't really speak for my employer...On 7/10/06, Albert van Peppen <
[EMAIL PROTECTED]> wrote:Same here; all my work is property of the company I work for. But it is possible for me to donate my bugfixes/enhangements back to the community un
The syntax for using the localization string should be
$(loc.UninstallAppShortcut). I'm guessing that
!(loc.UninstallAppShortcut) is evaluating to the null value.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Laurent
Courbet
Sent: Monda
Hi,
I have a strange behaviour when I use localization with Shortcut tag:
I have in wxl file the string Uninstall [ProductName]
and in an other file I use
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
WiX-users mailing lis
Title: WixUI_InstallDir problems
Hi,
I don't have these problems, but did you
checked the wix.chm help (search for WIXUI_INSTALLDIR)?
Another great resource is the tutorial at http://www.tramontana.co.hu/wix/index.php#TOC
I use the DirectoryRef-way.. Maybe that's why i don't have
the pro
Title: WixUI_InstallDir problems
Hi.
That almost did it, but I ran into another problem (which
is the same issue really).
I have:
...
...
Title: WixUI_InstallDir problems
Most likely becouse you need to set the property to
your installation location like this:
Albert
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Namens Nordvik,
ChristerVerzonden: maandag 10
Just here to say that .ocx files should be easy to get sorted. I used tallow
on one about a year
ago and it pulled out all the needed entries no problem.
Rob
Derek Cicerone wrote:
> If they work with regsvr32 they should be the same as normal self-reg dll
> files (a simple fix). Please open a
Try looking at
http://www.codeproject.com/dotnet/dotNetInstaller.asp
Rob
X Y wrote:
> Hi All,
> I am new to Wix and was wondering if there was an
> example floating out there that does the following:
>
> 1. Detect whether .NET is installed in the machine (an
> example has already been done via t
Same here; all my work is property of the company I work for. But it is
possible for me to donate my bugfixes/enhangements back to the community under
strict guidelines.
So, on to of that there is this agreement.
Nonetheless I think it would be far more easier for a lot of people if they got
a
I have a service that installs under LocalSystem. I found that when I tried
adding it with a given
user name, I had to add permissions to that user with a Custom Action. Even
Administrator doesn't
have the rights to change services by default. When you go to the services app
it gets given
Title: WixUI_InstallDir problems
Hi!
I have the following wxs file:
Property>
Hello there,
JH> Valery
JH> Can you explain to me how this script is working. I only seem to
JH> understand this up to the point of where it gets the W3SVC object.
JH> After that I'm a bit confused.
JH> Sorry to bother you on your personal email. If you want me to I can
JH> submit this to wix-u
41 matches
Mail list logo