I'm a little foggy on what the specific arguments are for installing
.Net assemblies, our product requires that the assemblies be installed
in both the GAC and INSTALLDIR. I've tried creating duplicate
components, but am getting ICE30 errors during install. The component
definitions look like
I think if there was, someone would have spoken up. I've not seen any.
Personally, I prefer the mailing list. Archives are there for the
searching on the web and I subscribe to mailing lists on Gmail, so I
never delete the old posts anyhow and the search is nice and fast.
Overall, I feel it's
On Jan 23, 2008 7:49 PM, Bob Arnson [EMAIL PROTECTED] wrote:
Chris Weiss wrote:
I've got two versions of an assembly installed based on whether the
user is on a Terminal Services machine or not. The files are
associated with two different mutually-exclusive features that are set
Is there some special voodoo that needs to occur to copy files into
system32 subfolders? I've got the following (paraphrased) component
definitions:
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder
Directory Id=INSTALLLOCATION Name=Symyx
Directory
Is there a way to read the return of a DLL call CA into a property? I
have a DLL that tracks down a particular printer driver and returns a
path to the files. The DLL is pre-written, so I can't use
MSISetProperty or any fun-ness like that.
--
-Chris
On Jan 12, 2008 11:15 AM, Bob Arnson [EMAIL PROTECTED] wrote:
Chris Weiss wrote:
Condition Message='This setup requires the .NET Framework 3.5 or
higher.'
NETFRAMEWORK35
/Condition
I'm including the WixNetFxExtension v3.0.2925.0
Is NETFRAMEWORK35 not set? Are you
I'm in the process of implementing .Net Framework 3.5 checking in my
WiX installer using the WixNetFxExtension, but the call seems to be
returning incorrect results. My code check is pretty basic:
Condition Message='This setup requires the .NET Framework 3.5 or higher.'
NETFRAMEWORK35
The point appears to be moot - For whatever reason, WiX is picking up
the proper help icons correctly without needing any whacked shortcut
associations. Not sure why InstallShield fails at this.
On Jan 8, 2008 2:13 PM, Mike Dimmick [EMAIL PROTECTED] wrote:
No you _can't_. That will embed hh.exe,
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 the
I'm trying to create a merge module with the file list as a separate
file so that programmers can edit it while still exposing as little of
the installer as possible. I'd planned to use a Fragment, but
discovered that Fragments are no longer supported (why?). If this were
not a merge module, I
When we created help file shortcuts in the start menu using
InstallShield, we had to manually set the icon to
System32\WinHlp32.exe. If I try to do this with WiX, it complains that
the extension of icon 'xyz' for shortcut 'abc' does not match the
extension of the Key File for component 'foo.chm'.
11 matches
Mail list logo