In article <[EMAIL PROTECTED]>,
Chesong Lee <[EMAIL PROTECTED]> writes:
> > My question is: Can I safely ignore this warning?
>
> It would be wise to avoid the warning.
While I agree with this, I would add that in practice I've never seen
a problem arising from overflowing the field. Stil
Hi,
1) Is it possible to create one MSI for both 32bit and 64 bit OS
2) If yes
my queries are
1) In my case, except 2 binaries, remaining all binaries are same.
The binaries which are different are service32.exe for 32bit and
service64.exe for 64 bit
So I added win64="yes" for service64.exe.
> My question is: Can I safely ignore this warning?
It would be wise to avoid the warning.
Schema of the CustomAction table shows that Action field is S255 which is up to
255 characters.
CustomAction.idt
Action TypeSource Target
s72 i2 S72 S255
CustomActionAction
Property
Bob Arnson írta:
> Szentpali Janos wrote:
>> Does that mean that the same file, installed by two unrelated setup
>> packages into the same path, with two distinct component and file ids
>> (guids) will still be correctly uninstalled/managed?
>
> No, that's what component rules are about. The compo
I'm trying to prepare my product for localization and I ran into a problem
localizing the GUIDs for the Product ID and Upgrade Code. I noticed a couple
messages about this and I also saw that a bug about this was closed several
months ago, and I'm curious if this has been fixed in a more-recent bu
On Thu, 3 Jan 2008 08:57:04 -0800, Chris Weiss wrote:
Chris,
> the problem of creating a help icon for my .CHM shortcut. Should I
> be creating a single DLL that only contains the help icon (and if I
> copy the one from WinHlp32.exe, am I violating some sort of
> Microsoft copyright)?
Yes, creat
Does anyone have a suggestion on how to disable autoplay after the first
disk in a multi-disk install? Right now I have the following:
- Insert Disk 1: Autoplay runs and executes my setup.msi via a setup.exe
program. Disk 1 files are installed.
- Installer prompts for Disk 2, but at the same ti
On Jan 2, 2008 4:22 PM, Mike Dimmick <[EMAIL PROTECTED]> wrote:
> What you specify in the Icon elements gets incorporated in your .msi as a
> binary at build time, so it should be something you have control over, not
> attempting to use a system executable.
>
> The warning message is described in t
Nope, I wasn't. That fixed it. Thanks all!
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 03, 2008 10:31 AM
To: Alex Steen
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] SQL Elements are not recognized in Visual
Studio?
JCWrs wrote:
JCWrs wrote:
> I still get an error that says the Product element contains an unexpected
> child element 'User'.
> I get another one that says the Component element contains an unexpected
> child element 'SqlDatabase'.
>
Are you supplying the namespace in the element name (i.e.,
and )?
--
s
Szentpali Janos wrote:
> Does that mean that the same file, installed by two unrelated setup
> packages into the same path, with two distinct component and file ids
> (guids) will still be correctly uninstalled/managed?
No, that's what component rules are about. The component GUID and
resource I
Henning Eiben wrote:
> Yeah, I've found this article before ... but how would I do this within
> my app? Do I have to create multiple (identical) -elements like this:
>
Yes. You can use CopyFile to install one and copy it elsewhere but it's
about the same amount of work and CopyFile isn't nece
Joa wrote:
> But what about installing empty directories? They do not contain files,
> therefore no components are created and thus they are not installed.
> How can I use tallow to collect all files and create a component for the
> empty directories, too?
>
Tallow doesn't support that. You can
I did not have those so I added them, the top of my file now looks like this:
http://schemas.microsoft.com/wix/UtilExtension";
xmlns:sql=" http://schemas.microsoft.com/wix/SqlExtension";
xmlns:ui="http://schemas.microsoft.com/wix/UIExtension";>
I added a reference to WixSqlExte
In the end it was the the exe.config file not being included with the
serice.exe file.
I added the following in the service component and it works.
Thanks for all your help identifying this.
Wilson, Phil wrote:
> If it can be started ok after the install then the issue could b
I am new to WIX and am using "tallow -d" to generate a FileSet for a specific
directory and all the directories and files below. The output is a FileSet
that contains several components, each one for the files of a certain
directory. These components get collected in the FeatureSet for later
insta
Bob Arnson írta:
> Szentpali Janos wrote:
>> "Merge modules are generally now considered bad practice..." If this
>> is true than what is the point of the whole MSI system? I mean if I
>> have a 3rd party component (x.dll) that 4th party and 5th party are
>> using too, how does the system decide th
I did find the new WIX project types..
I guess I expected to find a WIX Add-In.. which must not apply in this case.
I will move forward and work with the WIX project types.
Thanks for your assistance.
Philip
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January
Could you also give an example please? I tried following but it also
didn't work - it says "Failed to create network share. ( -2147 Root)":
And additionally I have another question: How can I
Could you also give an example please? I tried following but it also
didn't work - it says "Failed to create network share. ( -2147 Root)":
And additionally I have another question: How can I
Bob Arnson wrote:
>> I didn't find an obvious way to include a file only once in the MSI and
>> install it to serveral locations ...
>>
>
> Generally you don't. Instead, you can use WiX's support for "smart
> cabbing" so that only a single copy of the file is included in your MSI
> package reg
21 matches
Mail list logo
