Re: [WiX-users] Accented character in Shortcut Name causes Error LGHT0204: ICE03: Invalid Filename
Schuett, Michael wrote: I converted all my wx* files to utf-16 and saved them as Unicode with the same result. Thanks, Mike -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Szentpali Janos Sent: Friday, November 30, 2007 3:27 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Accented character in Shortcut Name causes Error LGHT0204: ICE03: Invalid Filename Schuett, Michael wrote: Hello, If I use an accented character in a Shortcut Name, the following error results... D:\WiX\ClientInstall\Application.wxs(39,0): Error LGHT0204: ICE03: Invalid Filename; Table: Shortcut, Column: Name, Key(s): TrayAppShortcut Here's the section from Application.wxs. File Id=Tray.exe Name=Tray.exe KeyPath=yes Source=ClientFiles\Tray.exe Shortcut Id=TrayAppShortcut Directory=ProgramGroupDir WorkingDirectory=INSTALLLOCATION Arguments=/EnableTray Name=Redémarrer le moniteur Icon=tray.ico Advertise=yes / /File If I remove the é from the Shortcut Name it builds successfully. Any suggestions? I'm using WiX 3.0.2925.0. Thanks, Mike -- --- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users Try changing the encoding... put ?xml version='1.0' encoding='utf-8'? on the beginning of the .wxs file... or whatever encoding that is the one you are using -- Szentpáli János - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users You really mean utf-16 and not utf-8? Are you sure that the file(s) was(were) saved in the specified (utf-16) fromat? I must admit I still use Wix2, but I guess Wix3 would/should behave the same in this regard :-? It happened to me to, that I specified utf-8 in the xml incoding, but actually did not save the source files in utf-8 incoding and it did complain when found the accented characters... What editor did you use to save the files (curiosity :D)? -- Szentpáli János - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Accented character in Shortcut Name causes Error LGHT0204: ICE03: Invalid Filename
Schuett, Michael wrote: If I use an accented character in a Shortcut Name, the following error results... D:\WiX\ClientInstall\Application.wxs(39,0): Error LGHT0204: ICE03: Invalid Filename; Table: Shortcut, Column: Name, Key(s): TrayAppShortcut Are you setting Product/@Codepage? Take a look at your package in Orca; if the codepage is incorrect, MSI will show special characters as question marks. -- sig://boB http://joyofsetup.com/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSCONFIG shows unknown for service manufacturer
Kevin Richardson wrote: I completely agree with you that msconfig is supposed to grab the company name from the resources of the code file; the point of my post is that it's not doing that when I install the service through the ServiceInstall table. It only displays the company name if the service is self-registered from the command-line. Export the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services registry key after using both approaches and diff them. That will let you see what the differences are and maybe whether the MSI service support will work. That said, as long as it works as expected in other programs like Explorer and the Services snap-in, abandoning native MSI just to make MSConfig happy seems a bad bargain. -- sig://boB http://joyofsetup.com/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Handling Feature Dependencies
[EMAIL PROTECTED] wrote: Okay. So what if the hidden fC actually contains a merge module (meaning, a MergeRef / element)? But I still don't want fC displayed in the interface anywhere. AFAIK, ComponentGroupRefs do not contain MergeRefs. Should I make fC an sub-Feature of fA and fB? Will it still be hidden from the interface if I do that? Should work, using @InstallDefault=followParent and @Display=hidden. -- sig://boB http://joyofsetup.com/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Not Supported Exception with Candle
Eldiberto Espinosa wrote: I'm getting a Not Supported Exception when I run Candle. The error seems related to path's formats but even when I switch to absolute paths on command line and inside the WXS I get the error. I'm running Wix version 3.0.2925.0. Command Line : candle.exe -IC:\Program Files\Windows Installer XML v3\bin -out D:\Workspaces\Source\build\Setup\Authorize.net.wixobj -pedantic:easy -v D:\Workspaces\Source\build\Setup\Authorize.net.wxs Microsoft (R) Windows Installer Xml Compiler version 3.0.2925.0 Copyright (C) Microsoft Corporation 2003. All rights reserved. Authorize.net.wxs candle.exe : error CNDL0001 : The given path's format is not supported. Please file a bug so we can beef up the command line parsing. The problem is that -p is a valid switch to preprocess a file; candle is trying to write to a file named edantic:easy which is illegal. The -pedantic switch doesn't take any arguments, so just drop the :easy and it'll work. -- sig://boB http://joyofsetup.com/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Deletion of sys, cab and inf files after succesful DIFx install
ashatilo wrote: But how to specify that folder is temporary in WiX. MSI doesn't support that. And also will DIFx work correctly at uninstallation time if I will delete *.cat, *.sys and *.inf files upon successful install. You'd have to ask the DDK folks. -- sig://boB http://joyofsetup.com/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to use CloseApps custom action
V K Gangwar wrote: I can see the CloseApps.cpp file in WiX sources. But how can use this file for custom action. I have to build this. How I can build this DLL using VS2005 or VC++. You don't need to build it -- it's in the WixUtilExtension.dll extension. See CloseApplication Element in wix.chm. -- sig://boB http://joyofsetup.com/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
