Re: [WiX-users] Using heat.exe as part of an automated build process
After receiving emails from people on this subject asking about our process, I will reply to all publicly here. Unfortunatly my employer 'owns' the code, getting OS in the door is hard enough, getting it out is not an option I am afraid. However for those interested the general methodology used is as follows. Each file has an XML file which describes it, how it gets installed and any required params which cannot be auto harvested. It also lists what products this file gets used by ( we have a lot of code sharing among products). This file is then read and generates wix source files for each product using transforms and xpath. This pass also tell the products what components they have. The component files are then built, tranforms are done to generate the features using the information from pass 1 and then the final generation of msms and then msis. This process currently manages our msi generation for 20+ installation products from 240ish components built from source and a few hundred ancillary files. It removes most of the tedium and mistakes made, but is still fully extensible by careful use of include files. It's not quite the nirvana of fully automated code generation but it does remove the tedium and potential mistakes from changing one component which is used in all products. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using heat.exe as part of an automated build
Although Rob et al, don't recommend this approach we have been using Heat, and it's predecessor, as part of our automated build process for over a year with Wix3. The main things to be wary of are the spurious entries generated by Heat, for example VB6 entries which should not be there. However this is where XML shines, using both Xpath and tranforms, you can sanitise the output from heat directly into compilable code. We use Ant as our main build tool and xmltask a contributed package for ant works very well for the substitions and removal. I am unaware if Nant has a similar package. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Registry Search REG_DWORD Handling
I am trying to be nice to users upgrading from one version (or rolling back) and use the general method of creating a default value which the user can override in the install, or may override by editing the registry value itself later on (perfectly valid in the context of the applications, things change and we must cope with this). On installing over an existing install I read all the values from the registry, assign to property, and use this if not changed again in the GUI. This all works fine for REG_SZ but for REG_DWORD the registry search prepending a # converts the DWORD to a REG_SZ and give it a string value of #12345. Below is the code I am generally using to try to achieve this, first install I get a dword, after that it gets converted to REG_SZ. Include Property Id=PORT Value=12345 RegistrySearch Id=idPORT Key=SOFTWARE\Company\Product Name=Port Root=HKLM Type=raw / /Property File .. RegistryKey Root=HKLM Key=SOFTWARE\Company\Product Action=create RegistryValue Name=Port Value=#[PORT] Type=integer / /RegistryKey /File /Include What are the issues in getting just the Value from a reg search without the prepended #? Will I have to write a CA just to get rid of this value? Any ideas welcome, thanks Peter - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Com LocalServer32 in 8.3 format
I upgraded to the latest binary build on SourceForge (3.0.2211.0). A bit painful as tallow has been deprecated and Heat is very much different, but have it working again in my headless build. Unfortunately the registry entries are still in [!MyServerExe] format not [#MyServerExe]. Maybe the next build then. Peter -Original Message- From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: 07 November 2006 16:01 To: Dyson, Peter Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Com LocalServer32 in 8.3 format Dyson, Peter wrote: I am currently using v3.0.1703.0 a bit old in the tooth now but have not had time to use any later. I'm not sure exactly when the change was made, but the current version uses [#] syntax. BTW, if you use WiX v3, you should consider taking drops more often. As v3 is still in development, schema changes still happen and if you wait too long, you can get hit with a lot at once. The WixCop tool upgrades the schema so it's not a manual job at least. -- sig://boB http://bobs.org - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Com LocalServer32 in 8.3 format
I am currently using v3.0.1703.0 a bit old in the tooth now but have not had time to use any later. Peter -Original Message- From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: 07 November 2006 03:34 To: Dyson, Peter Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Com LocalServer32 in 8.3 format Dyson, Peter wrote: This seems to be because of the [!MyServer.exe] generated in the msi. If Which version of WiX are you using? I believe that WiX v3 was changed some time ago to use LFNs. WiX v2 wasn't changed because it would break patching for products already released with v2. -- sig://boB http://bobs.org - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Com LocalServer32 in 8.3 format
Hi, I am authoring wix version 3 com servers in the 'correct' way as below, but the LocalServer32 @ registry entry is generated in 8.3 format names. This seems to be because of the [!MyServer.exe] generated in the msi. If I use orca to change that to [#MyServer.exe] then I get the long filename as I require. I would much prefer to maintain the code below rather than a load of registry entries which are prone to mistakes, is there any method of forcing the [#MyServer.exe] to be generated. ?xml version=1.0 encoding=utf-8? Include TypeLib Id=EA305BC3-2E79-4D45-80ED-1255CA84833F Advertise=no Language=0 MajorVersion=1 MinorVersion=0 Description=MyServer 1.0 Type Library HelpDirectory=INSTALLDIR AppId Id=94C608D3-2ACA-419F-BF70-F66CC418CCBE Description=MyServer Advertise=no Class Id=BBAFBB6F-4BB7-41BC-8770-A723EABDC901 Advertise=no Context=LocalServer32 ProgId Id=MyServer.Control.1 ProgId Id=MyServer.Control / /ProgId Interface Id=B62C4D30-0086-4AB1-ABDB-F0E74D36D1C7 Name=IControl ProxyStubClassId=00020424---C000-0046 ProxyStubClassId32=00020424---C000-0046 / /Class /AppId /TypeLib /Include Thanks, Peter - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users