Re: [WiX-users] Calling functions in standard dlls

You can create a simple "proxy" DLL which: - will be compatible with WiX - will redirect the custom action call to a standard DLL. -Original Message- Date: Sun, 07 Sep 2008 13:32:44 -0700 From: Bob Arnson <[EMAIL PROTECTED]> Subject: Re: [WiX-users] Calling functions in standard dlls T

Re: [WiX-users] finding .net 3.5 or greater

Don, You can use an approach from the article "How to determine which versions of the .NET Framework are installed and whether service packs have been applied": http://support.microsoft.com/kb/318785 Just enumerate and analyze subfolder names from the folder "%systemroot%\Microsoft.NET\Framework"

Re: [WiX-users] Generate MSI during install

Hello Phil, You can create 2 separate WiX projects, for a server, and for a client. Than add a Custom Action to the first one (server), which will launch a batch file for compiling and linking the second one (client). MBR, Yuri -Original Message- Date: Fri, 16 May 2008 10:05:47 -0400 Fr

Re: [WiX-users] WiX-users Digest, Vol 23, Issue 180

Hi, This is the link you asked about. Just a hint: DIFx is part of DDK. MSDN | MSDN Library | Win32 and COM Development | Windows Driver Kit | Device Installation | Design Guide } Using Driver Install Frameworks (DIFx) Driver Install Frameworks for Applications (DIFxApp): http://msdn2.microsof

Re: [WiX-users] WiX-users Digest, Vol 23, Issue 153

I played with the 1st sample (SampleFirst.zip) from this tutorial: http://www.tramontana.co.hu/wix/ and got the same message. After removing some stuff from the .wxs: - Vital='yes' from from Subject: [WiX-users] CNDL0001 : Culture 'en' is a neutral culture. To: Message-ID: <[EMAIL PROTE

Re: [WiX-users] Votive error

Yes, it seems to be a bug. The source of troubles seems to be the "non-alphanumeric" dot. I know two ways to bypass: - Rename file "License.rtf" to "License_rtf" and use "WixUILicenseRtf=License_rtf" - Move this definition into the .wxs: I myself prefer the 2nd. BR Yuri Gendelman --