stant during the WiX version change.
I'm assuming your firewall change wouldn't have affected the
RadioButton schema. I don't see why Text would now have a length of 0.
-kevin
> Kevin Richardson wrote:
>> WixFirewallException : Port => String, length 0
>> Ra
I use Torch to create language transforms of products I generate, and
lately I've been getting several instances of the following warning:
warning TRCH1115 : The value '0' in table '_Validation', column
'KeyColumn' is invalid according to the column's validation
information. The deco
In that case, something is definitely wrong. Uninstall should work
from any install location without your intervention.
You had said that we were both doing the same thing, but your
directory table is not the same as mine. You have:
>
>
>
>
> < File
You probably want the directory tree to look like this:
>
>
>
>
...
...
...
...
-kevin
On Nov 24, 2008, at 9:23 AM, [EMAIL PROTECTED]
wrote:
> Date: Mon, 24 Nov 2008 21:25:05 +0800
> From: "Jianjun An (Person Consulting)" <[EMAIL PROTECTED]>
I was happy to see Bob's changes to add multi-platform DIFxApp support
to WiX3
(http://sourceforge.net/tracker2/?func=detail&aid=1962701&group_id=105970&atid=642714
).
Unfortunately, I seem to be missing something because I can't get the
linker to find MsiProcessDrivers. I get the LGHT0094
Hi all,
I have to generate localized MSIs for a deliverable. To do this, I
build a language-neutral package, followed by each culture. In all
cases, I pass -cc and -reusecab to light.
The cabinet file is being regenerated each time light is called (I can
watch the modification time and lat
Hi there,
I'm installing a driver using DIFxApp, and just migrated to WiX3. I
found that I had no issues using WixDifxAppExtension.dll on the x86
installer, but the install fails on x64 (compile/link does not).
As expected, the error is "You need to use the 64-bit version of
DIFXAPP.DLL to
HI there,
Forgive my MSBuild-noobness...
When using MSBuild, it looks like the WiX executables (candle/light)
are located via a registry key. Can this be overridden?
Thanks,
-kevin
-
This SF.net email is sponsored by t
You'll want to use instead. Include
WixUtilExtension.dll with and use:
This will append the permissions rather than replacing them.
Remember to add xmlns:util="http://schemas.microsoft.com/wix/UtilExtension
" in your element.
-kevin
> I am using Wix Release 3.0.4102.0 and I want to gra
Greetings,
Does anyone have an example of building multi-language WiX installers
with MSBuild? I've looked at the single-language examples, but what
I'd like to do is have a .wixproj that builds an installer in 10+
languages.
My current process uses the WiX tools manually through batch file
Hi all,
I'm authoring an installer that contains several merge modules (among
the other things):
- Microsoft_VC80_CRT_x86.msm
- policy_8_0_Microsoft_VC80_CRT_x86.msm
- Microsoft_VC80_DebugCRT_x86.msm
- policy_8_0_Microsoft_VC80_DebugCRT_x86.msm
The installer has been building and installing f
27;ll need to
choose the correct msiexec.exe (system32 for 64-bit on x64, syswow64
for 32-bit on x64, system32 on 32-bit), or can x64's system32\msiexec
install 32-bit MSIs?
-kevin
On Jan 23, 2008, at 7:46 PM, Bob Arnson wrote:
> Kevin Richardson wrote:
>> Is it "OK&quo
Hi there,
For several products, I have distinct 32-bit and 64-bit MSIs, as you'd
expect.
I'd like a single download that contained both, and would install the
correct MSI, depending on the system architecture. For this to work,
the executable would have to be compiled as 32-bit.
Is it "OK"
Thanks Julie.
The example you gave is what I fell back on. Unfortunately, we pull in
(localized) files dynamically and those tools make heavy use of the
FeatureRef/ComponentRef structure that apparently only works in WiX2.
I believe Bob's webpage mentioned adding support for so hopefully I c
/>
SourceName="Program.msi" DestinationDirectory="INSTALLERCACHE" />
Name="Program.msi" On="uninstall" />
On="uninstall" />
Hi all,
I'm in the process of converting from WiX2 -> WiX3.
Everything is fine in WiX2... in WiX3, when I run the linker, I get
the following error:
error LGHT0095: Multiple primary references were found for Feature
'OnlyFeature' in Product 'GUID' and Product 'SAME GUID'.
I have one file
Thanks, Nathan.
Turns out that having the word "Install" in the shortcut was enough to
get ruled out. Sheesh!
-kevin
Original message
From: "Nathan Stohlmann" <[EMAIL PROTECTED]>
Subject: Re: [WiX-users] "Newly installed" start menu highlight
To: wix-users@lists.so
Hi all,
When a new program is installed, XP/Vista generally highlight the
start menu shortcut in orange (unless you have disabled it). Is there
anything that can prevent this from happening?
The shortcut from an installer I'm currently working on never appears
as a new program with highligh
> There is very little doubt in my mind that msconfig is getting the
> company name from the resources of the code file (in the cases where
> it
> gets it right). For just one example, look at what msconfig says about
> the Logical Disk Administrator Service, and then look at the company
> name i
doesn't have
> the company name in its resources (which is where I believe MSConfig
> gets it from).
>
> Phil Wilson
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Kevin
> Richardson
> Sent: Wednesd
Hi all,
After installing a service using the ServiceInstall table/element,
MSCONFIG reports the manufacturer as "unknown."
If I use the self-registering code of the service executable (i.e.
myservice.exe /i), the manufacturer field is populated correctly.
Is this a known issue with MSI's Ser
21 matches
Mail list logo
