Kevin Burton wrote:
> There are no custom actions in the .wxs file and the only language specific
> thing that is being set is via the element and the Language
> attribute.
>
WiX sets the ProductLanguage property from Product/@Language. It doesn't
set a PRODUCTLANGUAGE property.
--
sig://bo
There are no custom actions in the .wxs file and the only language specific
thing that is being set is via the element and the Language
attribute.
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 14, 2007 7:06 PM
To: Kevin Burton
Cc: 'WiX-users'
Subjec
Kevin Burton wrote:
> Could this be the source of my problems? How do I set PRODUCTLANGUAGE to be
> the same as ProductLanguage?
>
I don't think MSI would use it because it's not a standard property. See
if your package (through a merge module or custom action, for example),
sets it.
--
sig
Rennie Petersen wrote:
I_USERS =
"cur"
I_USERS = "all"
That makes sense.
--
sig://boB
http://bobs.org
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2
OK, thanks again, that hint and a lot of searching finally got me to a
solution. Which is (this solution is for the case where default should
be a single-user install):
In the non-UI part of your project, place a definition similar to the
following:
cur
Do NOT try to define a default nul
Just another doubt... excuse me I've no previous experience programming any
setups...
I got my .wxs compiled and linked adding -ext WixIIsExtension
-cultures:en-us. How do I add the culture switch to the votive sentence?
--
View this message in context:
http://www.nabble.com/IIS-schema-problem-
Is there an example on how to use the MessageQueue element? I would like to
see a full example, please. Namespace required? If it is under the component
section what are the consequences of putting it in multiple features? I want
the MessageQueue to be a part of all the features installed but I don
How do i configure Votive to include it in candle and light sentence?
Just do a "Add reference" to WixIIsExtension.dll
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 expre
Bob Arnson-3 wrote:
>
> You need to use the -ext switch to load the WixIIsExtension to process
> the Web* elements.
>
I compiled and linked with extension with no problems using command
prompt... Thanks!
How do i configure Votive to include it in candle and light sentence?
TIA
Jose
--
View
I don't see German on install (I have seen it on install when the disk is
full but the disk is not full any more). I do see a button with a German
label on uninstall right now. I don't notice anything in the log on
uninstall that would look like a German string. I do see when it is dumping
the prop
The components are Office PIAs and other similar things that are best placed
in the GAC...
I don't seem to be able to build the perfect setup program for my case, so I
might have to just swallow the pill and require elevated privileges in Vista
> -Original Message-
> From: [EMAIL PROTECTE
Thanks.
But how is it possible from a dialog box to choose "per-user" and
"per-machine" installs?
Can you define a property on-the-fly from a radio button control?
Are there examples of how to do this somewhere?
(I know that Wise for Windows Installer somehow supports this.)
Thanks again
Rennie Petersen wrote:
When the ALLUSERS property is not defined I get a per-user install.
But when I define ALLUSERS and give it a value of 0 then I get a
per-machine install.
For reasons long to the mists of time, ALLUSERS=0 isn't a valid value;
only 1, 2, and null are, per the ALLUSERS
Doug Payne wrote:
A have a checkbox on my Setup Finished dialog which uses the ShellExec
CA to launch my application. Is there a way to specify the default
directory for my application in the CA? I think this would be the same
as specifying the lpDirectory in ShellExecute().
That's not cu
WenWu Ru wrote:
> Yep, that was my confusion. I also thought Impersonate="no" was the correct
> way to set the msidbCustomActionTypeNoImpersonate flag and run as
> LocalSystem. However, the action type is 1025. The custom action still
> fails when an admin launches the installer elevated via
Alex Steen wrote:
> After doing a lot more fiddling, I don't believe it's a problem with my
> INSTALLDIR at all (the property is correct when I call my CustomAction
> at the end of the install so it appears to be setting correctly).
That doesn't mean it's being set at the right time. Take a look
Nick Hennemann wrote:
And it appears that the minor upgrades (service packs) would be
approximately the same size as the original install?
Depends on the extent of the changes. Minor upgrade patches can also
take advantage of delta patching so how well they delta and compress
controls the
Kevin Burton wrote:
> Do you know how to change that?
>
It's impossible to say without knowing the root cause. Use a verbose
(/l*vx) log to determine which action/dialog is being shown when you see
the German string.
--
sig://boB
http://bobs.org
--
Thanks for your replies.
Yep, that was my confusion. I also thought Impersonate="no" was the correct
way to set the msidbCustomActionTypeNoImpersonate flag and run as
LocalSystem. However, the action type is 1025. The custom action still
fails when an admin launches the installer elevated vi
Heat documentation is non-existent unless you count the source code. It was a
tool that Derek created and enhanced and basically owned before he left to do
different things. Nobody has picked up where he left off.
I took a quick look at the code and it seems like TypeLib harvesting should
hap
I'm very new to WiX and Windows Installer, so maybe I'm doing something
dumb...
When the ALLUSERS property is not defined I get a per-user install.
But when I define ALLUSERS and give it a value of 0 then I get a
per-machine install.
I've checked the MSI with Orca, and the value of ALLUSERS is 0
21 matches
Mail list logo
