Hi,
What might be the cause of the error with the error code of LGHT0112 ?
The following might be the code which produces the error code :
CustomAction Id='ChkProgDLL' BinaryKey='ChkProgDLL'
DllEntry='CheckProgramExist'/
The name of the DLL is ChkProgDLL.dll and the function is in
Hi,
I wish to enable an OK button if the folder path choose by user does
not exist on the machine and disable the OK button if the folder already
exist. In order words, the user only can create the target folder if it does
not exist on the machine. Following are my code :
Dialog Id=BrowseDlg
No, the latest is always at http://wix.sourceforge.net/releases.
Frederik Carlier (our release manager) has been exceptionally busy lately and
hasn't been updating the Releases Page of SourceForge for a couple months.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Burton
Yes, look at the Conditional Statement Syntax in the MSI SDK. There are
symbols that track the various states of a Feature and Component.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hongping Lim
Sent: Friday, April 20, 2007 6:58 PM
To: wix-users@lists.sourceforge.net
Subject:
Hi,
I have solved the problem. It seems like i forgot to add the following
code
at the end of my .wxs file
Binary Id=ChkProgDLL SourceFile=ChkProgDLL.dll/
After i add the code, i can build the installer ( .msi ). However, an
error
is reported when i try to run the DLL from a button
I wrote the DLL by using Microsoft Visual Studio .NET 2005 C#.
there you have your problem. If you search the mailinglists you'll find out
*many times* that managed custom actions aren't supported..
-
This SF.net
Hi,
I dont think so. I'm able to call an .EXE written using Microsoft Visual
Studio .NET 2005 C# . It's managed code too. I'm just wondering why not the
DLL. I guess there must be something wrong in my wix source files .
--
View this message in context:
Hello,
Is it by any means possible to include multiple files in a single
statement automatically in a component? I would like to add the full
contents of a PrecompiledWeb directory in a component, but without the
need for having to add a file element for each (100+) file.
Thanks!
Kind
That's a totally different thing.. (but still unsupported)
On 4/22/07, teckJBMsia [EMAIL PROTECTED] wrote:
Hi,
I dont think so. I'm able to call an .EXE written using Microsoft Visual
Studio .NET 2005 C# . It's managed code too. I'm just wondering why not
the
DLL. I guess there must be
No. The composition of a component must not change (or at least it is
recommended that it does not change) because components are
reference-counted, not resources. This means that Windows Installer will
remove all the resources associated with a component when that component's
resource count
Please keep /wix-users/ on the thread.
[EMAIL PROTECTED] wrote:
Our Deployment project has a number of Web components(each has their own Msi).
And using WIX we are trying to generate an single msi which
in turn would call each.I was suggested to use Merge Modules instead of nested
Msi.
Any
Kevin Burton wrote:
OutputFile=!-- Example, obj\Debug\MySetup.wixobj --
@(Compile-gt;'..\PACKAGE\WiX_Temp\Release\%(Filename).wixobj')
There's a difference in either your project file or the WiX MSBuild
project. I've never used the WiX v2 MSBuild support so I can't
12 matches
Mail list logo