Are you saying that TARGETDIR should not be set to
\\wmiscratch\scratch\davut\DaRT? But that's where software was installed
right?. Installer should be setting it internally. My problem is; if the share
become unavailable then there seems to be no way out. Can't uninstall or
repair, or install
Not a bad suggestion:)
Paul would you mind to have a look at this, in case the linker is case
sensitive.
Thank you.
E.
From: Kelly Leahy [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 01, 2007 4:59 PM
To: Eric Baudouin
Cc: Paul Houldridge; wix-users@lists.sourceforge.net; [EMAIL PROTECTED
Ok... It also appears that your error message says 'Facename' (lowercase
'N'), but your declaration shows an uppercase. Not sure if it matters,
just thought I'd mention it since I noticed it.
Kelly
Eric Baudouin <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
11/01/2007 04:44 PM
To
Kelly L
Here is the answer from Paul, so it look like syntaxically speaking we were
doing the right thing.
So I think we need to focus more on the methodology. Thank you anyway for your
reply.
No luck. Using the ! instead of the $ is right. $ is deprecated.
.\SetupUI.wix(26) : warning LGHT1073 : The
Thanks a lot. You are right. I was using the display name and so it was not
working. It is now working with the correct service name.
Again thanks!
Richard-45 wrote:
>
>
> In article <[EMAIL PROTECTED]>,
> shapla <[EMAIL PROTECTED]> writes:
>
>> I checked it in Orca. I see that it has t
Let me check with Paul, this might simply explains why the variables were not
replaced.
Thank you.
E.
From: Kelly Leahy [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 01, 2007 4:31 PM
To: Eric Baudouin
Cc: Paul Houldridge; wix-users@lists.sourceforge.net; [EMAIL PROTECTED]
Subject: Re: [WiX
Don't you want $(loc.BannerTextStyle_Size) not
!(loc.BannerTextStyle_Size)?
Kelly
Eric Baudouin <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
11/01/2007 04:17 PM
To
"wix-users@lists.sourceforge.net"
cc
Paul Houldridge <[EMAIL PROTECTED]>
Subject
[WiX-users] Font definition and WXL
It doesn't look to me like there's a way to do this, but I don't know
anything about WiX's support for IIS.
Hopefully somebody else will recommend.
Kelly
Rolando <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
11/01/2007 04:00 PM
To
Kelly Leahy <[EMAIL PROTECTED]>
cc
[EMAIL PROTECTED], wix-
Hello,
We have moved our resource to a wxl file to facilitate the localization of our
component.
In the localization world it is a good practice to make sure that the font size
and the font facename can be localized.
I was hoping that I could move the font style attribute in the WXL as well so
Rob, Peter, Blair and Chad - Thank you guys all for the help. Turns out I
haven't changed Package/@Id. Now it is working as charm! Thanks a lot.Davut
> Date: Thu, 1 Nov 2007 15:49:24 -0700> From: [EMAIL PROTECTED]> To: [EMAIL
> PROTECTED]> CC: wix-users@lists.sourceforge.net> Subject: Re: [WiX-u
Thank you for your reply,
I've tried this before but it doesn't work, because is not possible to
add a reference from the children web directories to the common web
directory.
Is there any way to add a reference to an existing web directory?
Kelly Leahy wrote:
I don't know anything about us
Can you share the before and after values for:
Product/@Id
Product/@UpgradeCode
Package/@Id
What version of the WiX toolset are you using?
Davut Karabay wrote:
> Hi,
>
> When I run the new version of installer, it invokes the installed old
> version. I don't want that happen. I want the new v
Sadly, not supported yet. It's one of those features I wish was
implemented.
Marc Scheuner wrote:
> Is there a way in WiX / Windows Installer to get a dialog that will show the
> currently available IIS web sites, and the currently defined virtual
> directories inside each web site, so that I
Note that Package ID and ProductCode are different. One is on the Package
element and should always change, one is on the Product element and should
change with each release.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut Karabay
Sent: Thursday, November 01, 2007 2:54 PM
To
That was the first thing I did, changing both product id and upgrade code. But
still invokes the cached msi. I think I will give another try because everyone
suggests it will work.
By the way please bare with me on installers :). It is one of the things that I
inherited recently.
Subject: RE
Is your new package id different than the old one? Almost no one should ever
explicitly set the package id. They should always have it autogenerated
instead. (http://msdn2.microsoft.com/library/aa370568.aspx)
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut Karabay
Sent: Thur
MSI (c) (4C:38) [13:48:25:762]: PROPERTY CHANGE: Modifying TARGETDIR property.
Its current value is 'C:\Program Files\Microsoft Diagnostics and Recovery
Toolset'. Its new value: '\\wmiscratch\scratch\davut\DaRT'.
This line seems to me to be the primary reason. TARGETDIR is the location where
th
Peter is suggesting you change your Product Id="GUID". I think you might
want to also consider changing the UpgradeCode="GUID" also for future
ease of upgrading one product versus the other, but it really depends on
what your ultimate goal is.
From: [EMAIL PROT
On 11/1/07, 0x001A4 <[EMAIL PROTECTED]> wrote:
>
> How would I go about changing the default installation directory from Program
> Files to the C:\ or whatever drive the user has windows installed on?
Your Directory structure probably looks something like this:
.
>From the msi documentation: "The ProductCode property is a unique identifier
>for the particular product release"
It sounded to me like you have a completely separate release so you should
change the ProductCode property of the MSI. This is set by the Product/@Id
attribute in WiX.
From: Davut
I generated a real GUID (package id) :). But that didn't work. It still invokes
the cache. Do you think it shouldn't?
Re: [WiX-users] How to prevent cached msi being invoked (not askingmsiexec
/fv)From: Hugues Valois <[EMAIL PROTECTED]> - 2007-11-01 21:03Attachments:
Message as HTML
Hi Rob - Thank you for your reply. Do you mean I require network share to exist
during uninstall (in the WIX code)? Isn't that a requirement by MSI which I
don't have control over? Here is the log. I couldn't understand anything useful
other than error code.
...Id start 13:48:25: CostFinalize.
Did you forget to change the package id? Or use
---- to have a package id generated
automatically by Wix.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Davut
Karabay
Sent: Thursday, November 01, 2007 12:41 PM
To: wix-users@lists.sourceforge.net
Change the product code.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davut Karabay
Sent: Thursday, November 01, 2007 1:40 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to prevent cached msi being invoked (not asking
msiexec /fv)
Re: [WiX-users] How to pr
Is there a way in WiX / Windows Installer to get a dialog that will show the
currently available IIS web sites, and the currently defined virtual
directories inside each web site, so that I can pick a web site / virtual
directory as my installation target directory??
Also, I'd like to be able
Where does the disk usage dialog get the values to put into the table?
The selection tree in the custom setup dialog indicates that the install
requires 68 MB, but in the disk usage dialog it says that 159 MB are
required on the drive. I would expect these values to be the same.
Brian Simoneau
So
Hello Richard, thank you for your help.
I will try to include the SelfRegModules action and test it on a
virtual machine, and see if that solves the problem.
Do you know where can I get the Crystal Reports runtime MSI packages?
We are using version XI, and in the crystal page, I can only find
MS
In article <[EMAIL PROTECTED]>,
Davut Karabay <[EMAIL PROTECTED]> writes:
> When I run the new version of installer, it invokes the installed old versi=
> on. I don't want that happen. I want the new version installed anyway.
Why?
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft avai
I don't know anything about using MSI to install virtual directories, but
I think the solution is to put your 'shared' parent directory in a
component that is used by all of your applications, using the same
ComponentGuid. Then, only the 'first' application installed will add the
directory, an
Hi,
When I run the new version of installer, it invokes the installed old version.
I don't want that happen. I want the new version installed anyway. How can I
break the link between the new and the old? I changed Product ID GUID but it
didn't help. Using Launch Conditions do not help because
Hi, I have five products, each one of them creates one or more virtual
directories. I need to put all this virtual directories inside a common
virtual directory.
ie.
Default Web Site
|-[My product line]
|-ProductOne
|-ProductTwo
...
|-Prod
In article <[EMAIL PROTECTED]>,
Adam Majer <[EMAIL PROTECTED]> writes:
> Huh? Hacky is allowing files to be modified in install locations.
Agreed, but you can't "fix" everything. Attempting to modify files in
the installed program location is likely to break on a highly locked
down Windows
Hi,
I'm still trying to register my help2 files, and if I use the
WixVSExtension I end up with the same problem as described in bug
1588180
If I follow do it the manual way according to
http://msdn2.microsoft.com/en-us/library/bb164959(VS.80).aspx it
works, if I decompile this msi then I once aga
Pedro,
My first recommendation would be to use a bootstrapper and the Crystal
reports runtime MSI file instead of the merge modules. The merge modules
are IMHO almost useless, not to mention the fact that if you use WiX 3
you'll have to turn off verification because the CR merge modules have
so ma
Richard wrote:
> In article <[EMAIL PROTECTED]>,
> Craig0ss <[EMAIL PROTECTED]> writes:
>
>> Basically my installer installs certain standard letters for use with the
>> software, if i change the standard letter to incorperate client specific
>> details and then uninstall the product the modi
In article <[EMAIL PROTECTED]>,
Craig0ss <[EMAIL PROTECTED]> writes:
> Basically my installer installs certain standard letters for use with the
> software, if i change the standard letter to incorperate client specific
> details and then uninstall the product the modified file is removed, i
I'm learning WiX and have been experimenting with a 64-bit install package for
Vista64 During the install, I would like to run a 64-bit configuration tool.
I can successfully launch the tool with a normal MSI custom action.
However, when I try to launch the 64-bit exe silently using the Wix
Also make sure the 's Level attribute is not set to "0".
Best regards,
Sebastian Brand
Instyler Software - http://www.instyler.com
On Oct 30, 2007, at 2:29 , Richard wrote:
>
> In article
> <[EMAIL PROTECTED]>,
>"Sajo Jacob" <[EMAIL PROTECTED]> writes:
>
>> I have defined all my featur
Hello, I have what might probably be an easy problem to solve, but I can not
find a way :(
I currently have an installer that shows ".will install PRODUCT". I wish it
to say ". will install the PRODUCT".
Is there a way to override the resource strings? I need to change this in a
few place
How would I go about changing the default installation directory from Program
Files to the C:\ or whatever drive the user has windows installed on?
--
View this message in context:
http://www.nabble.com/Changing-the-default-installation-directory-tf4731406.html#a13528883
Sent from the wix-users
A so you were thinking along the lines of the preprocessor would just
produce a file with the correct values in the right place - so why wouldn't
the compiler eat it.
I was just delving into perl to get perl to read a file of file names and
produce the correctly formatted components. Am glad
Cryptonomicon wrote:
>
> I am guessing that
>
>
> and
>
> Guid="C4AB05E7-BE8D-40F2-891F-583750779D05" DiskId="1" Win64=$(var.Is64)>
>
> will cause pain grief and misery?
>
Not for me it didn't :) I tried this (actually: Win64="$(var.Win64)"), got
the squiggly blue lines and gave up for ot
Hey
Basically my installer installs certain standard letters for use with the
software, if i change the standard letter to incorperate client specific
details and then uninstall the product the modified file is removed, is
there a way to check if the file has been modified and do not delete it on
Sajo Jacob wrote:
>
> Thanks! that explains the exe's but how about the dlls with this issue?
>
64-bit DLLs? I don't know how heat.exe even manages to load and call
DllRegisterServer on 64-bit DLLs (it's a 32-bit .exe in the WiX download),
but it definitely doesn't produce what you'd expect. Ho
I am guessing that
and
will cause pain grief and misery?
or is there a variation on
I have missed?
--
View this message in context:
http://www.nabble.com/Wix-Integer-Variables-tf4730515.html#a13526479
Sent from the wix-users mailing list archive at Nabb
I am putting together a package of number crunching code that will be opened
sourced and I need to run parallel versions. I envision that users will be
running the validated release version and may also be playing with a non
validated version (by validation i mean the number crunching routines
pr
sai
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> ht
47 matches
Mail list logo
