[WiX-users] Updating the License Agreement
Hi, When iam updating the License agreement its is throwing some error called codepage should be-1252'. I updated my codepage but still it is throwing same error. My code is. ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Product Id=24F2B50A-BB6B-49D6-B4D3-3DEAC4FA512C Name=test Language=1033 codepage=1252 Version=3.2.5.0 Manufacturer=test UpgradeCode=c5870159-96cb-45a3-82b8-f2a4af250832 Package InstallerVersion=200 Compressed=yes / Property Id=WIXUI_INSTALLDIR Value=ProgramFilesFolder / WixVariable Id=WixUILicenseRtf Overridable=yes Value=C:\Users\Desktop\License.rtf / Media Id=1 Cabinet=media1.cab EmbedCab=yes / !--MajorUpgrade AllowSameVersionUpgrades=yes DowngradeErrorMessage=A VERSION IS ALREADY INSTALLED/-- Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder / Directory Id=INSTALLLOCATION Name=test Component Id=test DiskId=1 Guid=54FD7816-E770-4738-BDD6-EA118326724B File Id=chaitu.txt Name=chaitu.txt Source=C:\Users\Desktop\New folder\smeu.txt/File /Component /Directory /Directory Feature Id=ProductFeature Title=test Level=1 ComponentRef Id=test/ /Feature UIRef Id=WixUI_InstallDir / /Product /Wix Error is: A string was provided with characters that are not available in the specified database code page '1252'. Either change these characters to ones that exist in the database's code page, or update the database's code page by modifying one of the following attributes: Product/@Codepage, Module/@Codepage, Patch/@Codepage, PatchCreation/@Codepage, or WixLocalization/@Codepage How to over come the error Thanks Regards, avg -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] acces hklm from a current user installer
Your code looks like a registry search I do in an MSI that is built for 32 and 64 bit and works fine. The error you are getting resolves to %1 could not be found. Which is basically that key or value is not there. Double check the key/value is there and you have access, try creating it in the 32bit hive to see if it is a bitness issue. Open your MSI up in Orca or InstEd and check out the RegLocator table to see if the 64bitsearch bit is set on the relevant signature. -Original Message- From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: 08 March 2013 19:48 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] acces hklm from a current user installer The platform attribute is x64. Cheers Sean. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: 08 March 2013 19:40 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] acces hklm from a current user installer Then I assume you have Package/@Platform assigned as anything other than x86? @Win64 on the default RegistrySearch element instructs the search to look in the 64-bit registry when the value is 'yes'. When the value is 'no', the search looks in the 32-bit registry. The default value depends on the value of the Package/@Platform attribute: if the @Platform attribute value is 'x86', the default @Win64 attribute value is 'no'; otherwise, the default value is 'yes'. -Original Message- From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: Friday, March 08, 2013 1:31 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] acces hklm from a current user installer Hi: I'm not using th util extension--this is just in msi as tandard! Cheers Sean. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: 08 March 2013 19:15 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] acces hklm from a current user installer From the documentation... RegistrySearch Element (Util Extension) Attributes Name Type Description Required Win64 YesNoTypemk:@MSITStore:C:\Program%20Files%20(x86)\WiX%20Toolset%20v3.7\doc\W iX.chm::/html/util_xsd_simple_type_yesnotype.htm Instructs the search to look in the 64-bit registry when the value is 'yes'. When the value is 'no', the search looks in the 32-bit registry. The default value is 'no'. -Original Message- From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: Friday, March 08, 2013 12:07 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] acces hklm from a current user installer Hi: The key definitely exists on my test system, exporting the key from the registry editor gives: [HKEY_LOCAL_MACHINE\SOFTWARE\Freedom Scientific\JAWS\14.0] The Target value exists underneath. If I author a custom action, this can open the top level software\freedom scientific\jaws key but carn't see anything underneath this. The package is being built for x64, so I'm assuming the RegistrySearch will use the 64-bit hive. Any help/info apeciated. Regards Sean. -Original Message- From: Gabriel Ivanes [mailto:g...@fastmail.net] Sent: 08 March 2013 15:41 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] acces hklm from a current user installer Hi, You're sure your key and value exist ? To me -2147287038 means : not exist Le %:Date:, Sean Farrow sean.far...@seanfarrow.co.ukmailto:sean.far...@seanfarrow.co.uk a écrit: Hi, I need to access the hklm key from a per-user install from a registry search element My property looks like: Fragment !--JAWS 14 exe path.-- Property Id=JAWS14PATH Secure=yes RegistrySearch Id=JAWS14PATH Root=HKLM Key=SOFTWARE\Freedom Scientific\JAWS\14.0 Name=Target Type=raw/ /Property The log looks a follows: Action 20:40:11: AppSearch. Searching for installed applications Action start 20:40:11: AppSearch. AppSearch: Property: JAWS14PATH, Signature: JAWS14PATH MSI (c) (A0:84) [20:40:11:112]: Note: 1: 2262 2: Signature 3: -2147287038 Do I need escaped backslashes in strings? Does anyone have any ideas how I can get this working? Cheers Sean. -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Sincèrement, Gabriel I know no way of judging the future but by the
[WiX-users] I am getting no UninstallCommand from using ExePackage
The following is a simple call from a out of the box Wix bootstrapper trying to use ExePackage to a simple exe: ExePackage Id=MyApp Name=MyApp Description=MyApp Installation SourceFile=L:\bldtools\Setup\Bin\MyInstaller.exe InstallCommand=/ACTION=Install /t=MyApp /i=c:\common2d\MyApp /msi=L:\bldtools\Setup\DVD\MyMsi\MyInstallation.msi /l=20 RepairCommand=/ACTION=Repair /t=MyApp /msi=L:\bldtools\Setup\DVD\MyMsi\MyInstallation.msi /l=20 UninstallCommand=/ACTION=Uninstall /t=MyApp /msi=L:\bldtools\Setup\DVD\MyMsi\MyInstallation.msi Permanent=no PerMachine =yes Vital=yes / MyInstaller is called on Install and repair, but UninstallCommand never occurs. Is there a variable or flag I need to set in the bootstrapper to tell it I want the uninstallcommand too? I am using Wix 3.6 Thanks in Advance. - - jon -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/I-am-getting-no-UninstallCommand-from-using-ExePackage-tp7584223.html Sent from the wix-users mailing list archive at Nabble.com. -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Registering the .exe
Hi All, I am able to register a .dll or .ocx to the registry. We need to do the same this for .exe. Please could you advise or provide me the sample code to do this. Please let me know if you require any more information. Thanks in advance. Thanks, Sijo Joseph -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] I am getting no UninstallCommand from using ExePackage
Need to adjust comment above. On repair, I am getting Install command not the repair command. - - jon -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/I-am-getting-no-UninstallCommand-from-using-ExePackage-tp7584223p7584226.html Sent from the wix-users mailing list archive at Nabble.com. -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Registering the .exe
See http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Registration-of-COM-Executable-Server-td6557760.html or any of the other dozen or so times this has been asked answered on this list. Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Joseph, Sijo [mailto:sijo.jos...@cgi.com] Sent: 11 March 2013 11:25 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Registering the .exe Hi All, I am able to register a .dll or .ocx to the registry. We need to do the same this for .exe. Please could you advise or provide me the sample code to do this. Please let me know if you require any more information. Thanks in advance. Thanks, Sijo Joseph -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Question about transforms.
MsiPackage Id=RADInstall1 InstallSize=112640 Cache=yes Compressed=no Name=RADInstall1 SourceFile=L:\MainProject\bin\Release\MainProject.msi Vital=yes MsiProperty Name=TRANSFORMS Value=L:\MainProject\bin\Release\Jon.mst/ MsiProperty Name=INSTALLFOLDER Value=c:\Common2D\MyProject/ MsiProperty Name=ARPSYSTEMCOMPONENT Value=1/ First, I installed my little msi (only delivers a txt file. without the TRANSFORMS... line and it installs and uninstalls fine. I did this several times. However, Adding the TRANSFORMS ... line I can install but it does not uninstall. I created my transform by opening my little msi in Orca and starting the transform... changed the Productname and ProductCode then saved the mst. The above MsiPackage is in a Bundle's chain in the standard bootstrapper you get just out of the wix toolset (DevStudio - New project - Wix Bootstrapper). I am about to abandon transforms. I don't know how to get Wix to do them. Uninstalling is very important and just because it installs isn't good enough. How can I insure that it will uninstall? Looks like to me, that tranforms cannot be in the msiPackage if you want to support install, repair and uninstall. There has to be a way... Thanks - - jon -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Question-about-transforms-tp7584229.html Sent from the wix-users mailing list archive at Nabble.com. -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] I am getting no UninstallCommand from using ExePackage
You need a DetectCondition or Burn will never think the ExePackage is installed, thus never needs to be uninstalled. On Mon, Mar 11, 2013 at 4:42 AM, jeamis jonathan.a...@intergraph.comwrote: Need to adjust comment above. On repair, I am getting Install command not the repair command. - - jon -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/I-am-getting-no-UninstallCommand-from-using-ExePackage-tp7584223p7584226.html Sent from the wix-users mailing list archive at Nabble.com. -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Updating the License Agreement
I'm not sure what might be wrong with your code, but here's what I have for a custom license agreement: UIRef Id=WixUI_Minimal / UIRef Id=WixUI_ErrorProgressText / WixVariable Id=WixUILicenseRtf Value=License.rtf / In the same dir as the wxs, the License.rtf file contains my custom text of the agreement. Alain -Original Message- From: Chaitanya [mailto:chaita...@pointcross.com] Sent: March 11, 2013 03:57 To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] Updating the License Agreement Hi, When iam updating the License agreement its is throwing some error called codepage should be-1252'. I updated my codepage but still it is throwing same error. My code is. ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Product Id=24F2B50A-BB6B-49D6-B4D3-3DEAC4FA512C Name=test Language=1033 codepage=1252 Version=3.2.5.0 Manufacturer=test UpgradeCode=c5870159-96cb-45a3-82b8-f2a4af250832 Package InstallerVersion=200 Compressed=yes / Property Id=WIXUI_INSTALLDIR Value=ProgramFilesFolder / WixVariable Id=WixUILicenseRtf Overridable=yes Value=C:\Users\Desktop\License.rtf / Media Id=1 Cabinet=media1.cab EmbedCab=yes / !--MajorUpgrade AllowSameVersionUpgrades=yes DowngradeErrorMessage=A VERSION IS ALREADY INSTALLED/-- Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder / Directory Id=INSTALLLOCATION Name=test Component Id=test DiskId=1 Guid=54FD7816-E770-4738-BDD6-EA118326724B File Id=chaitu.txt Name=chaitu.txt Source=C:\Users\Desktop\New folder\smeu.txt/File /Component /Directory /Directory Feature Id=ProductFeature Title=test Level=1 ComponentRef Id=test/ /Feature UIRef Id=WixUI_InstallDir / /Product /Wix Error is: A string was provided with characters that are not available in the specified database code page '1252'. Either change these characters to ones that exist in the database's code page, or update the database's code page by modifying one of the following attributes: Product/@Codepage, Module/@Codepage, Patch/@Codepage, PatchCreation/@Codepage, or WixLocalization/@Codepage How to over come the error Thanks Regards, avg -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] I am getting no UninstallCommand from using ExePackage
Thank You - - jon -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/I-am-getting-no-UninstallCommand-from-using-ExePackage-tp7584223p7584233.html Sent from the wix-users mailing list archive at Nabble.com. -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question about transforms.
maybe the TRANSFORMS is specific to instance transforms. So how do you add a
regular transform to a msi?
On the commandline of MSIEXEC.exe it states to apply a transform via the /J
msifile module /T transform.mst.
How do you tell Wix to do this?
I get this (from log file):
...
[0DAC:0960][2013-03-11T09:44:17]: Applying execute package: RADInstall1,
action: Uninstall, path: C:\Documents and Settings\All Users\Application
Data\Package
Cache\{8B14C1DC-38C4-4CC6-9B05-5AA4320EC3C5}v1.0.0.0030\RADInstall1,
arguments: ' ARPSYSTEMCOMPONENT=1 MSIFASTINSTALL=7
/t=L:\MainProject\bin\Release\Jon.mst
INSTALLFOLDER=c:\Common2D\MyProject ARPSYSTEMCOMPONENT=1'
...
So how do you appy a regular transform?
-
- jon
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Question-about-transforms-tp7584229p7584234.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Is using Powershell script as a Wix Custom Action a good idea?
Hello Wix users, I have a very simple custom action something on the lines of validating a key as part of setup, the min requirement that the setup to run is on Win2k8 R2+. Now I can achieve the same thing in a dll but I feel its an overkill and is easily achieved in a script, for a while I was pondering over using vbscript until I read the warning in http://blogs.msdn.com/b/robmen/archive/2004/05/20/136530.aspx and decided against vbscript. Could folks point out if doing the same in powershell is ok? Thanks., Raghu -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Is using Powershell script as a Wix Custom Action a good idea?
I wouldn't, simply because some of the difficulties others have reported as well as introducing another dependency to your installer. A simple C++ CA DLL can be compiled for a minimal footprint and has no dependencies. -Original Message- From: Raghu [mailto:raghu_ti...@yahoo.com] Sent: Monday, March 11, 2013 8:05 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Is using Powershell script as a Wix Custom Action a good idea? Hello Wix users, I have a very simple custom action something on the lines of validating a key as part of setup, the min requirement that the setup to run is on Win2k8 R2+. Now I can achieve the same thing in a dll but I feel its an overkill and is easily achieved in a script, for a while I was pondering over using vbscript until I read the warning in http://blogs.msdn.com/b/robmen/archive/2004/05/20/136530.aspx and decided against vbscript. Could folks point out if doing the same in powershell is ok? Thanks., Raghu -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Is using Powershell script as a Wix Custom Action a good idea?
cool thanks for the info. our custom actions are typically in native code, so wanted to check out an easy way with a script, will embed the code into a dll itself then. Raghu Microsoft Corp, Redmond. From: Christopher Painter chr...@iswix.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net; Raghu raghu_ti...@yahoo.com; General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Monday, March 11, 2013 7:23 PM Subject: Re: [WiX-users] Is using Powershell script as a Wix Custom Action a good idea? Check out C# / DTF for managed custom action support instead of PowerShell. I have millions of successful installations logged and failure caused by DTF are extremely rare in WiX 3.6 / 3.7. In WiX 3.5 there was a bug that resulted in a 1% failure rate. From: Hoover, Jacob jacob.hoo...@greenheck.com Sent: Monday, March 11, 2013 8:29 PM To: Raghu raghu_ti...@yahoo.com, General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Is using Powershell script as a Wix Custom Action a good idea? I wouldn't, simply because some of the difficulties others have reported as well as introducing another dependency to your installer. A simple C++ CA DLL can be compiled for a minimal footprint and has no dependencies. -Original Message- From: Raghu [mailto:raghu_ti...@yahoo.com] Sent: Monday, March 11, 2013 8:05 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Is using Powershell script as a Wix Custom Action a good idea? Hello Wix users, I have a very simple custom action something on the lines of validating a key as part of setup, the min requirement that the setup to run is on Win2k8 R2+. Now I can achieve the same thing in a dll but I feel its an overkill and is easily achieved in a script, for a while I was pondering over using vbscript until I read the warning in http://blogs.msdn.com/b/robmen/archive/2004/05/20/136530.aspx and decided against vbscript. Could folks point out if doing the same in powershell is ok? Thanks., Raghu -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Updating the License Agreement
Chaitanya, My answer would be that your Licence.rtf file contains one or more characters that don't fit into the 1252 codepage. Either change your codepage to match the one that the RTF file was created in, or remove the characters from that file that don't fit into that codepage. Blair From: afor...@cmu.edu To: wix-users@lists.sourceforge.net Date: Mon, 11 Mar 2013 10:29:05 -0400 Subject: Re: [WiX-users] Updating the License Agreement I'm not sure what might be wrong with your code, but here's what I have for a custom license agreement: UIRef Id=WixUI_Minimal / UIRef Id=WixUI_ErrorProgressText / WixVariable Id=WixUILicenseRtf Value=License.rtf / In the same dir as the wxs, the License.rtf file contains my custom text of the agreement. Alain -Original Message- From: Chaitanya [mailto:chaita...@pointcross.com] Sent: March 11, 2013 03:57 To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] Updating the License Agreement Hi, When iam updating the License agreement its is throwing some error called codepage should be-1252'. I updated my codepage but still it is throwing same error. My code is. ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Product Id=24F2B50A-BB6B-49D6-B4D3-3DEAC4FA512C Name=test Language=1033 codepage=1252 Version=3.2.5.0 Manufacturer=test UpgradeCode=c5870159-96cb-45a3-82b8-f2a4af250832 Package InstallerVersion=200 Compressed=yes / Property Id=WIXUI_INSTALLDIR Value=ProgramFilesFolder / WixVariable Id=WixUILicenseRtf Overridable=yes Value=C:\Users\Desktop\License.rtf / Media Id=1 Cabinet=media1.cab EmbedCab=yes / !--MajorUpgrade AllowSameVersionUpgrades=yes DowngradeErrorMessage=A VERSION IS ALREADY INSTALLED/-- Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder / Directory Id=INSTALLLOCATION Name=test Component Id=test DiskId=1 Guid=54FD7816-E770-4738-BDD6-EA118326724B File Id=chaitu.txt Name=chaitu.txt Source=C:\Users\Desktop\New folder\smeu.txt/File /Component /Directory /Directory Feature Id=ProductFeature Title=test Level=1 ComponentRef Id=test/ /Feature UIRef Id=WixUI_InstallDir / /Product /Wix Error is: A string was provided with characters that are not available in the specified database code page '1252'. Either change these characters to ones that exist in the database's code page, or update the database's code page by modifying one of the following attributes: Product/@Codepage, Module/@Codepage, Patch/@Codepage, PatchCreation/@Codepage, or WixLocalization/@Codepage How to over come the error Thanks Regards, avg -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Is using Powershell script as a Wix Custom Action a good idea?
Which is fine as long as you don't mind the added dependency of .Net. I seem to remember some issues with newer os's not liking the standard .net installer as it is an optional feature of the OS. On Mar 11, 2013, at 9:57 PM, Christopher Painter chr...@iswix.com wrote: Check out C# / DTF for managed custom action support instead of PowerShell. I have millions of successful installations logged and failure caused by DTF are extremely rare in WiX 3.6 / 3.7. In WiX 3.5 there was a bug that resulted in a 1% failure rate. From: Hoover, Jacob jacob.hoo...@greenheck.com Sent: Monday, March 11, 2013 8:29 PM To: Raghu raghu_ti...@yahoo.com, General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Is using Powershell script as a Wix Custom Action agood idea? I wouldn't, simply because some of the difficulties others have reported as well as introducing another dependency to your installer. A simple C++ CA DLL can be compiled for a minimal footprint and has no dependencies. -Original Message- From: Raghu [mailto:raghu_ti...@yahoo.com] Sent: Monday, March 11, 2013 8:05 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Is using Powershell script as a Wix Custom Action a good idea? Hello Wix users, I have a very simple custom action something on the lines of validating a key as part of setup, the min requirement that the setup to run is on Win2k8 R2+. Now I can achieve the same thing in a dll but I feel its an overkill and is easily achieved in a script, for a while I was pondering over using vbscript until I read the warning in http://blogs.msdn.com/b/robmen/archive/2004/05/20/136530.aspx and decided against vbscript. Could folks point out if doing the same in powershell is ok? Thanks., Raghu -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Updating the License Agreement
How can we Know the Code page is suitable for this line.. I tried with 860 also its not working for me. -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: 12 March 2013 09:57 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Updating the License Agreement Chaitanya, My answer would be that your Licence.rtf file contains one or more characters that don't fit into the 1252 codepage. Either change your codepage to match the one that the RTF file was created in, or remove the characters from that file that don't fit into that codepage. Blair From: afor...@cmu.edu To: wix-users@lists.sourceforge.net Date: Mon, 11 Mar 2013 10:29:05 -0400 Subject: Re: [WiX-users] Updating the License Agreement I'm not sure what might be wrong with your code, but here's what I have for a custom license agreement: UIRef Id=WixUI_Minimal / UIRef Id=WixUI_ErrorProgressText / WixVariable Id=WixUILicenseRtf Value=License.rtf / In the same dir as the wxs, the License.rtf file contains my custom text of the agreement. Alain -Original Message- From: Chaitanya [mailto:chaita...@pointcross.com] Sent: March 11, 2013 03:57 To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] Updating the License Agreement Hi, When iam updating the License agreement its is throwing some error called codepage should be-1252'. I updated my codepage but still it is throwing same error. My code is. ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Product Id=24F2B50A-BB6B-49D6-B4D3-3DEAC4FA512C Name=test Language=1033 codepage=1252 Version=3.2.5.0 Manufacturer=test UpgradeCode=c5870159-96cb-45a3-82b8-f2a4af250832 Package InstallerVersion=200 Compressed=yes / Property Id=WIXUI_INSTALLDIR Value=ProgramFilesFolder / WixVariable Id=WixUILicenseRtf Overridable=yes Value=C:\Users\Desktop\License.rtf / Media Id=1 Cabinet=media1.cab EmbedCab=yes / !--MajorUpgrade AllowSameVersionUpgrades=yes DowngradeErrorMessage=A VERSION IS ALREADY INSTALLED/-- Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder / Directory Id=INSTALLLOCATION Name=test Component Id=test DiskId=1 Guid=54FD7816-E770-4738-BDD6-EA118326724B File Id=chaitu.txt Name=chaitu.txt Source=C:\Users\Desktop\New folder\smeu.txt/File /Component /Directory /Directory Feature Id=ProductFeature Title=test Level=1 ComponentRef Id=test/ /Feature UIRef Id=WixUI_InstallDir / /Product /Wix Error is: A string was provided with characters that are not available in the specified database code page '1252'. Either change these characters to ones that exist in the database's code page, or update the database's code page by modifying one of the following attributes: Product/@Codepage, Module/@Codepage, Patch/@Codepage, PatchCreation/@Codepage, or WixLocalization/@Codepage How to over come the error Thanks Regards, avg -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net
