Re: [WiX-users] rename registry keys
Changing the product code on its own isn't enough. Take a look here http://www.tramontana.co.hu/wix/lesson4.php Rob Adam Clay wrote: I have a question, about changing versions and upgrading, in previos versions, i have made a registry key HKEYLOCALMACHINE\...\version 2.0, but now in an update, i would like to change this to 2.0.1 though it seems that it only creates a new one, and changes the existing one. This also applys to the name of the instilation folder, I would like it to say application 2.0.1 are there any ways of doing an update that will change such things, but not reinstall the whole application. I was under the impression that changeing the product code would force an uninstall, then reinstall, though this doesnt seem to be the case. If anyone could point me to something that is relevant to read, or give me a few pointers, that would be great. I dint write the *.wxs, though i have to edit it, hense the plee for help. Thanks, .. *IMPORTANT NOTICE** This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. You are not to disseminate, copy or use any information from this e-mail if you are not the intended recipient. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of the Illawarra Division of General Practice. This message has been scanned for Viruses. .. - 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 - 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] heat cannot find MSVCR80.dll
Yes, it does indeed do this. However, you should have a publisher policy installed on your machine which redirects to 8.0.50727.42. I also have one which redirects to 8.0.50727.163. I'm running Windows XP SP2 with all current patches. Look in %SystemRoot%\WinSXS\Policies\x86_policy.8.0.Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_x-ww_77c24773 and check that 8.0.50727.42.policy is present, and that the corresponding .cat file is also present. If not, reinstall the vcredist package. You can't just copy MSVCR80.DLL - you must use an installer which correctly installs the Win32 assemblies. -- Mike Dimmick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven ChinSent: 20 September 2006 19:03To: wix-users@lists.sourceforge.netSubject: [WiX-users] heat cannot find MSVCR80.dll Visual Studio 2005 Released version 8.0.50727.42 creates output DLLs with a manifest that says it depends upon assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50608.0" Thus, heat can never find the MSVCR80.DLL version on the machine. Is there a way to make heat ignore the version dependency so as to take the latest version which is on the machine? Alternatively, is there a patch to VS 2005 to create correct manifest that indicates the correct version of VC80.CRT that it is using instead of a beta 2 version? - 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] failure in custom action.
Do you think the doubled directory separators could have
any significance? The [ProgramFilesFolder] property includes a trailing
directory separator, so you normally use it like
[ProgramFilesFolder][Manufacturer]\[ProductName]
to build a TARGETDIR.
--
Mike Dimmick
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sean Wang
(MSN)Sent: 20 September 2006 23:33To:
wix-users@lists.sourceforge.netSubject: [WiX-users] failure in custom
action.
Hi,
I hope this is the right alias for
my questions. If not, please kindly forward of you know any place
proper.
After moving to wix2.0. some of the
custom actions we used before began to fail. Manually running the action in
command line works just fine, but the msi fails with error message
:
Action
start 13:51:30: RemoveDatabaseFixXML.
MSI
(s) (8C:88) [13:51:31:171]: Note: 1: 1722 2: RemoveDatabaseFixXML 3: D:\Program
Files\FinReporting\OLAPCubes\ 4: "D:\Program
Files\\FinReporting\OLAPCubes\ChangeDSOXMLServer" "D:\Program
Files\\FinReporting\OLAPCubes\Remove database.xml" "D:\Program
Files\\FinReporting\OLAPCubes\Remove database.xml" "PREETITEST" "MSInsightOlap"
"oldDatasourceName" "AggregateReports" "PREETITEST" true true true
"PREETITESTDOM\FinRptWebUsers"
MSI
(c) (B4:D4) [13:51:31:171]: Font created. Charset: Req=0, Ret=0, Font:
Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI
(s) (8C:88) [13:51:47:671]: Product: OLAP Cubes -- Error 1722.There is a problem
with this Windows Installer package. A program run as part of the setup did not
finish as expected. Contact your support personnel or package vendor.
Action RemoveDatabaseFixXML, location: D:\Program Files\FinReporting\OLAPCubes\,
command: "D:\Program Files\\FinReporting\OLAPCubes\ChangeDSOXMLServer"
"D:\Program Files\\FinReporting\OLAPCubes\Remove database.xml" "D:\Program
Files\\FinReporting\OLAPCubes\Remove database.xml" "PREETITEST" "MSInsightOlap"
"oldDatasourceName" "AggregateReports" "PREETITEST" true true true
"PREETITESTDOM\FinRptWebUsers"
Action
ended 13:51:47: RemoveDatabaseFixXML. Return value
3.
( Ive traced my application to the
last line, where it write a line of trace and
completes:
Console.WriteLine("The file '" + args[Constants.destArgIndex] + "' was created
successfully.");
Tracer.Trace( Constants.TracerTag,
TraceLevel.Info,
"Operation completed successfully.");
System.Environment.ExitCode = 0;
)
Is this something other people also
see? How should I go with debugging such issue?
Thanks.
Sean
-
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] Message Queue Help Needed
Title: Message Queue Help Needed The deferred execution stage of Windows Installer - when the installation script actually runs - runs using the local computer's LocalSystem security context. This only has the network credentials of the machine account (in an Active Directory domain) or NULL permissions (if not on a domain). You most likely don't have permission to create a remote queue using these credentials. It's possible to make a custom action run as the user who ran the installer (Impersonate='yes', and I think this is the default - it would be helpful if the manual at wix.sourceforge.netlisted what the defaults are), and this may be the case with the custom action which processes the MessageQueue elements, but again this user would need to have whatever permissions are necessary to create a remote message queue. I think it would be better to make the message queue a Feature and the ability to select only that to install. Then the user would have to run the MSI on the machine that is to have the queue created. -- Mike Dimmick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Emma HannaSent: 21 September 2006 05:02To: wix-users@lists.sourceforge.netSubject: [WiX-users] Message Queue Help Needed Hi Everyone I am using the following code to create a Message Queue. It works fine when installed to the local machine (i.e. when AUDITQUEUESERVER is set to local machine name or .) but when I try to install to another machine name it fails. Can anyone give me some guidance as to how to install to a different machine? Component Id="MSMQPrivateQueue_Component" Guid="F744F282-2986-4acf-B2EA-A91E8AA2A1CF" pca:MessageQueue Id="AuditReceiveQueue" Label="Audit Receive Queue" Transactional="yes" PathName="[AUDITQUEUESERVER]\Private$\[AUDITQUEUENAME]" pca:MessageQueuePermission Id="AuditReceiveQueuePermissions" ReceiveMessage="yes" PeekMessage="yes" QueueGenericWrite="yes" User="MSMQDistributorServiceAccount"/ /pca:MessageQueue /Component Many Thanks Emma. - 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
[WiX-users] properties form previous versions
Hello, is there a way to get/access properties like INSTALLDIR and other custom properties from a previous installation which i update with an major upgrade using standard WIX functions? Thanks Alex - 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
[WiX-users] install multiple instances of app?
It is required to intall web application multiple times on the same server (i.e. into different web sites), or make multiple copies during single install. Each copy should have its own location (at least own Web.Config file) and perhaps own item in unistall list, preferable each copy to have own suffix, i.e. My application on Website1/My application on Website2, etc. How to do this? WiX msi allows only one instance. The only idea was to make few packages with different guids, or ajust package/product guid at runtime, but it seems not a good style. TIA - 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
[WiX-users] uninstall custom WebVirtualDir problem
there is a virtual folder, which name is configured from UI: Property Id=VIRTUALDFOLDERdefaultfoldername/Property ... Component Id=IIS5 ... WebVirtualDir Id=zzzVirtualDir Alias=[VIRTUALDFOLDER] Directory=INSTALLDIR WebSite=DefaultWebSite DirProperties=zzzSiteWebDirProperties WebApplication Id=zzzWebApplication Name=[VIRTUALDFOLDER] / /WebVirtualDir /Component ... Control Id=VirtualFolderEdit Type=Edit Property=VIRTUALDFOLDER ... / however, if we change defaultfoldername to something else (i.e. to newfoldername), uninstallation does not apply to newfoldername, it is still apply to defaultfoldername. i.e. newfoldername is left after uninstall, and defaultfoldername (if we had one before install) is deleted. this is certainly wrong. what to do with this? TIA - 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] uninstall custom WebVirtualDir problem
seems the answer: http://sourceforge.net/mailarchive/message.php?msg_id=36584651 - 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
[WiX-users] install multiple instances of app
It is required to intall web application multiple times on the same server (i.e. into different web sites), or make multiple copies during single install. Each copy should have its own location (at least own Web.Config file) and perhaps own item in unistall list, preferable each copy to have own suffix, i.e. My application on Website1/My application on Website2, etc. How to do this? WiX msi allows only one instance. The only idea was to make few packages with different guids, or ajust package/product guid at runtime, but it seems not a good style. TIA (please, delete previous message with this body - it has unreadable subject) - 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] install multiple instances of app
Thanks It seems my strategy should be: - place several static checkboxes/selectors for each copy of web app - make several hard-coded copies of web app, each of them will take it settings from corresponding check box - implement custom action, which will read settings for each app to make it possible smooth modifying application, when we will want to install just one more copy ...or perhaps it possible to modify product/package guid and name on the fly from inside of msi file -Original Message- From: Mike Dimmick [EMAIL PROTECTED] It's worse than that. Components should always have the same path, so you really need to generate new GUIDs for all the components for each instance. ... - 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] Installing extension for firefox
Salut, did it this way Property Id=FIREFOX_INSTALL_VERSION RegistrySearch Name=CurrentVersion Root=HKLM Id=FirefoxInstallVersion Type=raw Key=SOFTWARE\Mozilla\Mozilla Firefox / /Property Property Id=FIREFOX_INSTALL_PATH RegistrySearch Name=Install Directory Root=HKLM Id=FirefoxInstallPath Type=raw Key=SOFTWARE\Mozilla\Mozilla Firefox\[FIREFOX_INSTALL_VERSION]\Main / /Property and it works quite well. Thanks, Stefan -- View this message in context: http://www.nabble.com/Installing-extension-for-firefox-tf2305983.html#a6425889 Sent from the wix-users mailing list archive at Nabble.com. - 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
[WiX-users] Multiple files sharing registry
Could someone offer suggestions as to the best way of dealing with self registering files that share registry entries. There are a number of examples of this - 1. Later versions of files with different names (e.g. msxml.dll, msxml3.dll, etc) 2. Files that use other files (e.g. olepro32.dll uses oleaut32.dll) 3. Files that are part of the same subsystem (e.g. hhctrl.ocx and itss.dll) Etc Using tallow/heat/similar tools captures the registry for these types of files and puts it in a component with the file but this means that e.g. uninstalling a package containing msxml3.dll will break packages containing msxml.dll since the common registry will be deleted. The only solution I can think of is to create a separate component containing ALL the related registry entries (e.g. for all versions of msxml*.dll) and make sure that is always included with any of the relevant files. Is there a better way? This email originates from AXA Sun Life Services plc which distributes and administers financial services and products. Registered in England No. 3424940, registered office: 5 Old Broad Street, London, EC2N 1AD. AXA Sun Life Services plc is authorised and regulated by the Financial Services Authority and is entered on the Financial Services Authority register (www.fsa.gov.uk/register) number 185746. This message and any files transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed. If you have received this in error, you should not disseminate or copy this email. Please notify the sender immediately and delete this email from your system. Please also note that any opinions presented in this email are solely those of the author and do not necessarily represent those of the AXA UK Group of companies. Email transmission cannot be guaranteed to be secure, or error free as information could be intercepted, corrupted, lost, destroyed, late in arriving or incomplete as a result of the transmission process. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of email transmission. Finally, the recipient should check this email and any attachments for viruses. The AXA UK Group of companies accept no liability for any damage caused by any virus transmitted by this email. - 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] Multiple files sharing registry
For all the files you mention, you should be using the MSMs. If you generate your own component GUIDs for these files, you risk breaking other applications when they are uninstalled. See Rob Mensching's blog post 'Component Rules 101' for details (http://blogs.msdn.com/robmen/archive/2003/10/18/56497.aspx). For any case where you're redistributing a third-party's components, follow the supplier's guidance for how they should be redistributed. For HTML Help I think it should be the HTML Help Update package. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of DOLPHIN Paul (AXA-L) Sent: 21 September 2006 12:21 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Multiple files sharing registry Could someone offer suggestions as to the best way of dealing with self registering files that share registry entries. There are a number of examples of this - 1. Later versions of files with different names (e.g. msxml.dll, msxml3.dll, etc) 2. Files that use other files (e.g. olepro32.dll uses oleaut32.dll) 3. Files that are part of the same subsystem (e.g. hhctrl.ocx and itss.dll) Etc Using tallow/heat/similar tools captures the registry for these types of files and puts it in a component with the file but this means that e.g. uninstalling a package containing msxml3.dll will break packages containing msxml.dll since the common registry will be deleted. The only solution I can think of is to create a separate component containing ALL the related registry entries (e.g. for all versions of msxml*.dll) and make sure that is always included with any of the relevant files. Is there a better way? - 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] Component spanning directories
Cullen Thanks for the response. That makes some sense and I had not thought about the patching scenario (since we don't do that). -Original Message- From: Cullen Waters [mailto:[EMAIL PROTECTED] Sent: Friday, September 15, 2006 3:37 PM To: Reggie Burnett; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Component spanning directories Reggie, From what I've seen, the general guidance is to keep your components as small as possible. If, for instance, you found a bug in one of your source files, but had all source files in one component, your patch or upgrade installer would have to include all of the files in that component. It is my understanding that the generally accepted practice is to have many, many components (up to 1 per file), and then have features that describe what you are looking for. If I were authoring your installer, I would probably split up your files into components at the directory level (unless I had time to split at the file level), and then put all your components into a single feature. That way, all of your files get installed or uninstalled together, and you can still support smaller patch files if necessary down the road. Cullen -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Reggie Burnett Sent: Friday, September 15, 2006 1:27 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Component spanning directories We've been using Wix for some time now and recently got around to cleaning up our wix files. As we are adding samples and source code to the installer, I find it hard to believe that I can't make a single component include all my source files. As I understand it, a component should be anything that you want installed or removed as a unit. Well, if I want all my sources treated as a single unit, then a single component should do it. However, light complains about duplicate symbols. Can this be done? If not, why on earth not? It would seem ridiculous to create a thousand components to install a source tree of a thousand directories when it should be installed or removed as a unit. Thanks Reggie --- -- 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 - 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] Feature List conditional control
As promised, here was the solution to the problem. I am attaching my new dialog (EnvironmentDlg.wxs) to the email and will reference a subsection of it to explain what I did. Background: I wanted to create an installer that would install the same application across our staged environments (Dev, Test, Qa, Prod) without changing the install package. My installer includes a new dialog (EnvironmentDlg) that allows the installer to pick their environment as a checkbox. Depending upon their selection, I wanted the feature tree in CustomizeDlg to be updated based upon the installer's selection. From New Dialog (EnvironmentDlg): Control Id=DevEnvironmentCheckbox Type=CheckBox X=18 Y=78 Width=330 Height=18 CheckBoxValue=1 Property=DEV_ENVIRONMENT Text=Development Condition Action=disableTEST_ENVIRONMENT = 1 OR QA_ENVIRONMENT = 1 OR PROD_ENVIRONMENT = 1/Condition Condition Action=enable![CDATA[TEST_ENVIRONMENT 1]] AND ![CDATA[QA_ENVIRONMENT 1]] AND ![CDATA[PROD_ENVIRONMENT 1]]/Condition /Control Control Id=Next Type=PushButton X=236 Y=243 Width=56 Height=17 Text=amp;Next ... Publish Event=AddLocal Value=ConfigDevDEV_ENVIRONMENT/Publish Publish Event=Remove Value=ConfigDevNOT DEV_ENVIRONMENT/Publish ... /Control From my main wxs file: Feature Id=Configuration Level=1 Title=Web Application Configuration Description=Handles configuration for selected installation environment AllowAdvertise=yes Display=expand TypicalDefault=install Feature Id=ConfigDev Level=1 Title=Development AllowAdvertise=no Display=expand Description=Configuration (Development) TypicalDefault=install ComponentRef Id=InstallInstDevCfg / ComponentRef Id=CreateTemplateWebSiteDev / ComponentRef Id=CreateWebSiteDevKey / /Feature ... /Feature Depending upon the checkbox selected (Dev, Test, Qa, or Production [they are mutually-exclusive in my implementation]), the [Next] button fires a Publish event to either keep remove the four possible features. Thanks to all for the help in finding the solution! David Adams MSN MessengerID: [EMAIL PROTECTED] ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2003/01/wi; Fragment UI Dialog Id=EnvironmentDlg Width=370 Height=270 Title=[ProductName] Control Id=Next Type=PushButton X=236 Y=243 Width=56 Height=17 Text=amp;Next Publish Event=SpawnDialog Value=WaitForCostingDlgCostComplete = 1/Publish Publish Event=NewDialog Value=[WixUI_EnvironmentDlg_Next]1/Publish Publish Event=AddLocal Value=ConfigDevDEV_ENVIRONMENT/Publish Publish Event=Remove Value=ConfigDevNOT DEV_ENVIRONMENT/Publish Publish Event=AddLocal Value=ConfigTestTEST_ENVIRONMENT/Publish Publish Event=Remove Value=ConfigTestNOT TEST_ENVIRONMENT/Publish Publish Event=AddLocal Value=ConfigQaQA_ENVIRONMENT/Publish Publish Event=Remove Value=ConfigQaNOT QA_ENVIRONMENT/Publish Publish Event=AddLocal Value=ConfigProdPROD_ENVIRONMENT/Publish Publish Event=Remove Value=ConfigProdNOT PROD_ENVIRONMENT/Publish Condition Action=disable![CDATA[DEV_ENVIRONMENT 1]] AND ![CDATA[TEST_ENVIRONMENT 1]] AND ![CDATA[QA_ENVIRONMENT 1]] AND ![CDATA[PROD_ENVIRONMENT 1]]/Condition Condition Action=enableDEV_ENVIRONMENT = 1 OR TEST_ENVIRONMENT = 1 OR QA_ENVIRONMENT = 1 OR PROD_ENVIRONMENT = 1/Condition /Control Control Id=DevEnvironmentCheckbox Type=CheckBox X=18 Y=78 Width=330 Height=18 CheckBoxValue=1 Property=DEV_ENVIRONMENT Text=Development Condition Action=disableTEST_ENVIRONMENT = 1 OR QA_ENVIRONMENT = 1 OR PROD_ENVIRONMENT = 1/Condition Condition Action=enable![CDATA[TEST_ENVIRONMENT 1]] AND ![CDATA[QA_ENVIRONMENT 1]] AND ![CDATA[PROD_ENVIRONMENT 1]]/Condition /Control Control Id=TestEnvironmentCheckbox Type=CheckBox X=18 Y=98 Width=330 Height=18 CheckBoxValue=1 Property=TEST_ENVIRONMENT Text=Test Condition Action=disableDEV_ENVIRONMENT = 1 OR QA_ENVIRONMENT = 1 OR PROD_ENVIRONMENT = 1/Condition Condition Action=enable![CDATA[DEV_ENVIRONMENT 1]] AND ![CDATA[QA_ENVIRONMENT 1]] AND ![CDATA[PROD_ENVIRONMENT 1]]/Condition /Control Control Id=QaEnvironmentCheckbox Type=CheckBox X=18 Y=118 Width=330 Height=18 CheckBoxValue=1 Property=QA_ENVIRONMENT Text=QA / UAT Condition Action=disableDEV_ENVIRONMENT = 1 OR TEST_ENVIRONMENT = 1 OR PROD_ENVIRONMENT = 1/Condition Condition Action=enable![CDATA[DEV_ENVIRONMENT 1]] AND ![CDATA[TEST_ENVIRONMENT 1]] AND ![CDATA[PROD_ENVIRONMENT 1]]/Condition /Control Control Id=ProdEnvironmentCheckbox Type=CheckBox X=18 Y=138 Width=330 Height=18 CheckBoxValue=1 Property=PROD_ENVIRONMENT Text=Production Condition
Re: [WiX-users] properties form previous versions
It knows all your paths because given a ProductCode and a component guid it can use things like MsiGetComponentPath to find them. it knows all your properties is too general to reply to, but it certainly doesn't persist the values of properties that you create during your first install (unless they are standard properties persisted as part of its usual behavior, like MsiGetProductInfo can get your Manufacturer property, your version, company). Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexander Gnauck Sent: Thursday, September 21, 2006 6:24 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] properties form previous versions Hello David, I use the RegistrySearch element of the Property to retrieve previous user-selected property values on uninstalls. I think you could do the same thing for updates. Property Id=YOUR_PROPERTY Value=SomeValue RegistrySearch Id=PropSearch Root=HKLM Name=YourKeyName Type=raw Key=SOFTWARE\YourCompany\YourSection\YourKey / /Property In this case, the property value is retreived from the registry if found. If the key is not found in the registry, then the property value is defaulted to the @Value attribute. I would think the same model would work with the IniFileSearch element of the Property as well. yes that is what i also do with my NON MSI installs. Write the stuff i need later in updates to the registry and retrieve it then again. I thought there must be a simpler solution and the installer does that automatically. Because when you repair installations it knows all your paths, properties etc Alex - 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=DEVDE V ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - 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] properties form previous versions
The standard way to persist that (the main application directory) is to use a type 51 custom action and set the ARPINSTALLLOCATION property, then it will get persisted in the MSI way (meaning that MsiGetProductInfo with INSTALLPROPERTY_INSTALLLOCATION and other standard APIs can get it). Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexander Gnauck Sent: Thursday, September 21, 2006 2:28 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] properties form previous versions Hello, is there a way to get/access properties like INSTALLDIR and other custom properties from a previous installation which i update with an major upgrade using standard WIX functions? Thanks Alex - 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=DEVDE V ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - 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] Quick question on upgrade checking
What about version specs in your Wix UpgradeVersionElement? I don't know how Wix behaves in the absence of them, but there's nothing in your Wix that targets the versions you want to upgrade. Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff MacDuff Sent: Wednesday, September 20, 2006 5:17 PM To: Stefan Pavlik Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Quick question on upgrade checking It's still not working for me... here's what I did: I looked at the new msi ( the one we are building now ) and in the upgrade table it has a upgrade code. I then looked at the old MSI in orca, and in it's property table it has the exact same GUIDS for it's upgrade code. Is there any execection order I need to worry about for the upgrade check or something? I am getting really stumped... I actually copied the upgrade code from the old MSI via orca and put it directly into my new WIX project.. I rebuilt but still it doesn't work. -Jeff -Original Message- From: Stefan Pavlik [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 6:32 AM To: Jeff MacDuff Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Quick question on upgrade checking Hi, After reading the MSDN and Wix help (at the end of my email) I think that you can ommit the ExcludeLanguages attribute since you do not use the Language attribute. Anyway I think it should work as you want. Try to check the resulting MSI file with ORCA (or any other viewer) and look at the Upgrade Table. I know that I have not help you much, but... __ msdn: Upgrade Table Language The set of languages detected by FindRelatedProducts. Enter msidbUpgradeAttributesLanguagesExclusive in Attributes to detect all languages exclusive of those listed in Language. If Language is null or an empty string (), FindRelatedProducts ignores msidbUpgradeAttributesLanguagesExclusive and detects all languages. Wix Help: Language Specifies the set of languages detected by FindRelatedProducts. Enter a list of numeric language identifiers (LANGID) separated by commas (,). Leave this value null to specify all languages. Set ExcludeLanguages to yes in order detect all languages, excluding the languages listed in this value. -- Stefan Pavlik | [EMAIL PROTECTED] Whitestein Technologies | www.whitestein.com Panenska 28 | SK-81103 Bratislava | Slovak Republic Tel +421(2)5930-0735 | Fax +421(2)5443-5512 - 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=DEVDE V ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - 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] Controls and Events Help
Doug: See if this helps. I sent it this morning to the list and Deak (Tutorial). http://sourceforge.net/mailarchive/forum.php?thread_id=30596548forum_id=39978 David Adams MSN MessengerID: [EMAIL PROTECTED] From: Douglas Watts [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Subject: [WiX-users] Controls and Events Help Date: Thu, 21 Sep 2006 13:18:09 -0400 MIME-Version: 1.0 Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by bay0-mc5-f10.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Thu, 21 Sep 2006 10:19:16 -0700 Received: from sc8-sf-list1-new.sourceforge.net (unknown [10.3.1.93])by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTPid 08DAB1225E; Thu, 21 Sep 2006 10:19:07 -0700 (PDT) Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]helo=mail.sourceforge.net)by sc8-sf-list1-new.sourceforge.net with esmtp (Exim 4.43)id 1GQSCW-0006XS-Fmfor wix-users@lists.sourceforge.net; Thu, 21 Sep 2006 10:19:04 -0700 Received: from uslec-66-255-189-125.cust.uslec.net ([66.255.189.125]helo=EXCHANGE-01.advectis.office)by mail.sourceforge.net with esmtp (Exim 4.44) id 1GQSCT-0004JA-Qcfor wix-users@lists.sourceforge.net; Thu, 21 Sep 2006 10:19:04 -0700 X-Message-Info: LsUYwwHHNt1cyPYGWrLwGxjkZDlUzUZozJmCfqdqsoc= X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Controls and Events Help Thread-Index: Acbdoeky7xUM4RsJTry388eCeMJKCA== X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by sourceforge.net.See http://spamassassin.org/tag/ for more details.Report problems tohttp://sf.net/tracker/?func=addgroup_id=1atid=211.0 FORGED_RCVD_HELO Received: contains a forged HELO0.0 HTML_MESSAGE BODY: HTML included in message X-BeenThere: wix-users@lists.sourceforge.net X-Mailman-Version: 2.1.8 Precedence: list List-Id: General discussion for Windows Installer XML toolset.wix-users.lists.sourceforge.net List-Unsubscribe: https://lists.sourceforge.net/lists/listinfo/wix-users,mailto:[EMAIL PROTECTED] List-Archive: http://sourceforge.net/mailarchive/forum.php?forum=wix-users List-Post: mailto:wix-users@lists.sourceforge.net List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: https://lists.sourceforge.net/lists/listinfo/wix-users,mailto:[EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 21 Sep 2006 17:19:16.0621 (UTC) FILETIME=[10FEC3D0:01C6DDA2] As a newbie to WiX, I am still trying to understand the eventing mechanism in dialogs. Basically, I'm trying to understand how controls use and set properties; and how they consume and expose events. Can someone provide a very simple explanation of the following? 1. How dialog controls expose events 2. How dialog controls consume events 3. How controls set properties (set the property value based on user input in a dialog) 4. How controls use properties (to set values) I have been through the tutorial at www.tramontana.co.hu/wix but as good as it is, it does not explain a lot of the details. The help file (CHM) is a reference only. Sorry for such rookie questions but I'm trying to learn WiX ASAP. Thanks. __ Doug Watts - 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-user - 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] Controls and Events Help
I guess part of my problem is understanding the syntax. In your example, you have the following: Condition Action=disableTEST_ENVIRONMENT = 1 OR QA_ENVIRONMENT = 1 OR PROD_ENVIRONMENT = 1/Condition Condition Action=enable![CDATA[TEST_ENVIRONMENT 1]] AND ![CDATA[QA_ENVIRONMENT 1]] AND ![CDATA[PROD_ENVIRONMENT 1]]/Condition /Control In one place you test the TEST_ENVIRONMENT property using this syntax: TEST_ENVIRONMENT = 1 Elsewhere you use this syntax: [CDATA[TEST_ENVIRONMENT 1]] Can you explain when to use one versus the other? __ Doug Watts -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of david adams Sent: Thursday, September 21, 2006 1:28 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Controls and Events Help Doug: See if this helps. I sent it this morning to the list and Deak (Tutorial). http://sourceforge.net/mailarchive/forum.php?thread_id=30596548forum_id =39978 David Adams MSN MessengerID: [EMAIL PROTECTED] From: Douglas Watts [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Subject: [WiX-users] Controls and Events Help Date: Thu, 21 Sep 2006 13:18:09 -0400 MIME-Version: 1.0 Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by bay0-mc5-f10.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Thu, 21 Sep 2006 10:19:16 -0700 Received: from sc8-sf-list1-new.sourceforge.net (unknown [10.3.1.93])by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTPid 08DAB1225E; Thu, 21 Sep 2006 10:19:07 -0700 (PDT) Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]helo=mail.sourceforge.net)by sc8-sf-list1-new.sourceforge.net with esmtp (Exim 4.43)id 1GQSCW-0006XS-Fmfor wix-users@lists.sourceforge.net; Thu, 21 Sep 2006 10:19:04 -0700 Received: from uslec-66-255-189-125.cust.uslec.net ([66.255.189.125]helo=EXCHANGE-01.advectis.office)by mail.sourceforge.net with esmtp (Exim 4.44) id 1GQSCT-0004JA-Qcfor wix-users@lists.sourceforge.net; Thu, 21 Sep 2006 10:19:04 -0700 X-Message-Info: LsUYwwHHNt1cyPYGWrLwGxjkZDlUzUZozJmCfqdqsoc= X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Controls and Events Help Thread-Index: Acbdoeky7xUM4RsJTry388eCeMJKCA== X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by sourceforge.net.See http://spamassassin.org/tag/ for more details.Report problems tohttp://sf.net/tracker/?func=addgroup_id=1atid=211.0 FORGED_RCVD_HELO Received: contains a forged HELO0.0 HTML_MESSAGE BODY: HTML included in message X-BeenThere: wix-users@lists.sourceforge.net X-Mailman-Version: 2.1.8 Precedence: list List-Id: General discussion for Windows Installer XML toolset.wix-users.lists.sourceforge.net List-Unsubscribe: https://lists.sourceforge.net/lists/listinfo/wix-users,mailto:wix-us [EMAIL PROTECTED] List-Archive: http://sourceforge.net/mailarchive/forum.php?forum=wix-users List-Post: mailto:wix-users@lists.sourceforge.net List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: https://lists.sourceforge.net/lists/listinfo/wix-users,mailto:wix-us [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 21 Sep 2006 17:19:16.0621 (UTC) FILETIME=[10FEC3D0:01C6DDA2] As a newbie to WiX, I am still trying to understand the eventing mechanism in dialogs. Basically, I'm trying to understand how controls use and set properties; and how they consume and expose events. Can someone provide a very simple explanation of the following? 1. How dialog controls expose events 2. How dialog controls consume events 3. How controls set properties (set the property value based on user input in a dialog) 4. How controls use properties (to set values) I have been through the tutorial at www.tramontana.co.hu/wix but as good as it is, it does not explain a lot of the details. The help file (CHM) is a reference only. Sorry for such rookie questions but I'm trying to learn WiX ASAP. Thanks. __ Doug Watts --- -- 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=DEVD EV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-user - 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
Re: [WiX-users] Controls and Events Help
Doug, It's an XML encoding thing. You can't have the or characters inside an element (at least not in the way they need to be there) unless you encode them (use lt; and gt;), or put them in a CDATA block. Regards, Richard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Watts Sent: Thursday, September 21, 2006 13:44 To: david adams; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Controls and Events Help I guess part of my problem is understanding the syntax. In your example, you have the following: Condition Action=disableTEST_ENVIRONMENT = 1 OR QA_ENVIRONMENT = 1 OR PROD_ENVIRONMENT = 1/Condition Condition Action=enable![CDATA[TEST_ENVIRONMENT 1]] AND ![CDATA[QA_ENVIRONMENT 1]] AND ![CDATA[PROD_ENVIRONMENT 1]]/Condition /Control In one place you test the TEST_ENVIRONMENT property using this syntax: TEST_ENVIRONMENT = 1 Elsewhere you use this syntax: [CDATA[TEST_ENVIRONMENT 1]] Can you explain when to use one versus the other? __ Doug Watts -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of david adams Sent: Thursday, September 21, 2006 1:28 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Controls and Events Help Doug: See if this helps. I sent it this morning to the list and Deak (Tutorial). http://sourceforge.net/mailarchive/forum.php?thread_id=30596548forum_id =39978 David Adams MSN MessengerID: [EMAIL PROTECTED] From: Douglas Watts [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Subject: [WiX-users] Controls and Events Help Date: Thu, 21 Sep 2006 13:18:09 -0400 MIME-Version: 1.0 Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by bay0-mc5-f10.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Thu, 21 Sep 2006 10:19:16 -0700 Received: from sc8-sf-list1-new.sourceforge.net (unknown [10.3.1.93])by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTPid 08DAB1225E; Thu, 21 Sep 2006 10:19:07 -0700 (PDT) Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]helo=mail.sourceforge.net)by sc8-sf-list1-new.sourceforge.net with esmtp (Exim 4.43)id 1GQSCW-0006XS-Fmfor wix-users@lists.sourceforge.net; Thu, 21 Sep 2006 10:19:04 -0700 Received: from uslec-66-255-189-125.cust.uslec.net ([66.255.189.125]helo=EXCHANGE-01.advectis.office)by mail.sourceforge.net with esmtp (Exim 4.44) id 1GQSCT-0004JA-Qcfor wix-users@lists.sourceforge.net; Thu, 21 Sep 2006 10:19:04 -0700 X-Message-Info: LsUYwwHHNt1cyPYGWrLwGxjkZDlUzUZozJmCfqdqsoc= X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Controls and Events Help Thread-Index: Acbdoeky7xUM4RsJTry388eCeMJKCA== X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by sourceforge.net.See http://spamassassin.org/tag/ for more details.Report problems tohttp://sf.net/tracker/?func=addgroup_id=1atid=211.0 FORGED_RCVD_HELO Received: contains a forged HELO0.0 HTML_MESSAGE BODY: HTML included in message X-BeenThere: wix-users@lists.sourceforge.net X-Mailman-Version: 2.1.8 Precedence: list List-Id: General discussion for Windows Installer XML toolset.wix-users.lists.sourceforge.net List-Unsubscribe: https://lists.sourceforge.net/lists/listinfo/wix-users,mailto:wix-us [EMAIL PROTECTED] List-Archive: http://sourceforge.net/mailarchive/forum.php?forum=wix-users List-Post: mailto:wix-users@lists.sourceforge.net List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: https://lists.sourceforge.net/lists/listinfo/wix-users,mailto:wix-us [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 21 Sep 2006 17:19:16.0621 (UTC) FILETIME=[10FEC3D0:01C6DDA2] As a newbie to WiX, I am still trying to understand the eventing mechanism in dialogs. Basically, I'm trying to understand how controls use and set properties; and how they consume and expose events. Can someone provide a very simple explanation of the following? 1. How dialog controls expose events 2. How dialog controls consume events 3. How controls set properties (set the property value based on user input in a dialog) 4. How controls use properties (to set values) I have been through the tutorial at www.tramontana.co.hu/wix but as good as it is, it does not explain a lot of the details. The help file (CHM) is a reference only. Sorry for such rookie questions but I'm trying to learn WiX ASAP. Thanks. __ Doug Watts --- -- 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=DEVD EV
Re: [WiX-users] Controls and Events Help
Excuse me while I remove my shoe and proceed to kick my bottom!!! I was so focused on WiX syntax that I completely overlooked the XML requirements. I apologize for the brain blackout. __ Doug Watts Advectis, Inc. Direct:678.460.4605 Cell:770.314.6704 The #1 Network for Mortgage Document Collaboration -Original Message- From: Foster, Richard - PAL [mailto:[EMAIL PROTECTED] Sent: Thursday, September 21, 2006 1:55 PM To: Douglas Watts; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Controls and Events Help Doug, It's an XML encoding thing. You can't have the or characters inside an element (at least not in the way they need to be there) unless you encode them (use lt; and gt;), or put them in a CDATA block. Regards, Richard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Watts Sent: Thursday, September 21, 2006 13:44 To: david adams; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Controls and Events Help I guess part of my problem is understanding the syntax. In your example, you have the following: Condition Action=disableTEST_ENVIRONMENT = 1 OR QA_ENVIRONMENT = 1 OR PROD_ENVIRONMENT = 1/Condition Condition Action=enable![CDATA[TEST_ENVIRONMENT 1]] AND ![CDATA[QA_ENVIRONMENT 1]] AND ![CDATA[PROD_ENVIRONMENT 1]]/Condition /Control In one place you test the TEST_ENVIRONMENT property using this syntax: TEST_ENVIRONMENT = 1 Elsewhere you use this syntax: [CDATA[TEST_ENVIRONMENT 1]] Can you explain when to use one versus the other? __ Doug Watts -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of david adams Sent: Thursday, September 21, 2006 1:28 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Controls and Events Help Doug: See if this helps. I sent it this morning to the list and Deak (Tutorial). http://sourceforge.net/mailarchive/forum.php?thread_id=30596548forum_id =39978 David Adams MSN MessengerID: [EMAIL PROTECTED] From: Douglas Watts [EMAIL PROTECTED] To: wix-users@lists.sourceforge.net Subject: [WiX-users] Controls and Events Help Date: Thu, 21 Sep 2006 13:18:09 -0400 MIME-Version: 1.0 Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by bay0-mc5-f10.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Thu, 21 Sep 2006 10:19:16 -0700 Received: from sc8-sf-list1-new.sourceforge.net (unknown [10.3.1.93])by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTPid 08DAB1225E; Thu, 21 Sep 2006 10:19:07 -0700 (PDT) Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]helo=mail.sourceforge.net)by sc8-sf-list1-new.sourceforge.net with esmtp (Exim 4.43)id 1GQSCW-0006XS-Fmfor wix-users@lists.sourceforge.net; Thu, 21 Sep 2006 10:19:04 -0700 Received: from uslec-66-255-189-125.cust.uslec.net ([66.255.189.125]helo=EXCHANGE-01.advectis.office)by mail.sourceforge.net with esmtp (Exim 4.44) id 1GQSCT-0004JA-Qcfor wix-users@lists.sourceforge.net; Thu, 21 Sep 2006 10:19:04 -0700 X-Message-Info: LsUYwwHHNt1cyPYGWrLwGxjkZDlUzUZozJmCfqdqsoc= X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Controls and Events Help Thread-Index: Acbdoeky7xUM4RsJTry388eCeMJKCA== X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by sourceforge.net.See http://spamassassin.org/tag/ for more details.Report problems tohttp://sf.net/tracker/?func=addgroup_id=1atid=211.0 FORGED_RCVD_HELO Received: contains a forged HELO0.0 HTML_MESSAGE BODY: HTML included in message X-BeenThere: wix-users@lists.sourceforge.net X-Mailman-Version: 2.1.8 Precedence: list List-Id: General discussion for Windows Installer XML toolset.wix-users.lists.sourceforge.net List-Unsubscribe: https://lists.sourceforge.net/lists/listinfo/wix-users,mailto:wix-us [EMAIL PROTECTED] List-Archive: http://sourceforge.net/mailarchive/forum.php?forum=wix-users List-Post: mailto:wix-users@lists.sourceforge.net List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: https://lists.sourceforge.net/lists/listinfo/wix-users,mailto:wix-us [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 21 Sep 2006 17:19:16.0621 (UTC) FILETIME=[10FEC3D0:01C6DDA2] As a newbie to WiX, I am still trying to understand the eventing mechanism in dialogs. Basically, I'm trying to understand how controls use and set properties; and how they consume and expose events. Can someone provide a very simple explanation of the following? 1. How dialog controls expose events 2. How dialog controls consume events 3. How controls set properties (set the property value based on user input in a dialog) 4. How controls use properties (to set values) I have been through the tutorial at
Re: [WiX-users] Order of Menu Items
Hi Charly, What about the order when the user customized his Start menu? (i.e. by disabling the option Enable dragging and Dropping or by Sorting the menu (which isn't an option if you have the previous option disabled...)) I could imagine that Windows is only looking for this Reg key when the start menu option Enable dragging and Dropping is enabled. Regards, Marcel Scherpenisse - 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
[WiX-users] NativeImage element in NetFx
Im using this element in WiX 2.0. For the most part its been fine, but with internal product builds Ive had a few users hit a failure with uninstall where ngen returns that the assembly has already been uninstalled. This causes uninstalls to fail. I havent been able to get repro steps. Im left with a few questions: 1. Any suggestions on potential reasons for this or how I might track it down? 2. Why fail at all on uninstall with ngen? 3. Is it possible for me to override the custom action info for the extension in WiX? (ie- to ignore failures) My big concern is that we get inundated with support calls to help uninstall the application- I dont know of an easy way to skip extension actions with WiX (see the above #3). Thanks, -Jeremy - 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
[WiX-users] Wix 3 and WebSite element
Im a Wix newbie, sorta. About a month ago. I had some installers for our websites using Wix 2. We are in the process of moving to VisualStudio 2005 so I thought Id get a head start on converting the installers. Im getting this error in Candle: C:\localdev\Installation\GetMyGreenInstaller\GetMyGreenWebInstaller.wxs(91) : error CNDL0005 : The Component element contains an unexpected child element WebSite'. Using Votive I get a better description, but basically it says the element should be in namespace 'http://schemas.microsoft.com/wix/2006/wi' as well as any element in namespace '##other'. In the schema description it says the WebSite element is in the ##other namespace, but how do I specify I want to use it? Or do I need to? I tried this, but to no avail: candle.exe -ext WixIIsExtension.dll InstallerProject.wxs -out wixobj.obj Am I dumb? I cant figure it out. Thanks in advance for any tips! -- Matthew Janulewicz SCM Engineer Green Dot Corporation [EMAIL PROTECTED] (626) 775-3857 - 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] how to add URL info in MSI
Use a Property element to set the ARPHELPLINK property. See http://msdn.microsoft.com/library/default.asp?url="">for details. -- Mike Dimmick From: [EMAIL PROTECTED] on behalf of Ning YangSent: Thu 21/09/2006 21:06To: wix-users@lists.sourceforge.netSubject: [WiX-users] how to add URL info in MSI Hi, Im looking for the way to add URL info in MSI. When ask user to choose the options also add a hyper-link to provide more information. Is there any way to do it? Thanks a lot. Ning- 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] Wix 3 and WebSite element
Awesome! It worked! Thanks! My xml skills are poor, plus I didnt realize you could have more than one xmlns* argument in the Wix element. -Matt From: Mike Dimmick [mailto:[EMAIL PROTECTED] Sent: Thursday, September 21, 2006 1:51 PM To: Matthew Janulewicz; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Wix 3 and WebSite element WebSite appears to have been moved into the http://schemas.microsoft.com/wix/IIsExtensionnamespace. You'll need to add an xmlns:iis attribute to the Wix element, and reference WebSite as iis:WebSite. I think. I'm not too hot on XML Namespaces, but I think it should look like: ?xml version='1.0'? Wix xmlns='http://schemas.microsoft.com/wix/2006/wi' xmlns:iis='http://schemas.microsoft.com/wix/IIsExtension' Product ... ... Component ... iis:WebSite ... / /Component /Product /Wix To get IntelliSense for WebSite (etc) in Visual Studio, add iis.xsd (in your [WiX install folder]\doc) to the list of schemas. -- Mike Dimmick From: [EMAIL PROTECTED] on behalf of Matthew Janulewicz Sent: Thu 21/09/2006 21:02 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix 3 and WebSite element Im a Wix newbie, sorta. About a month ago. I had some installers for our websites using Wix 2. We are in the process of moving to VisualStudio 2005 so I thought Id get a head start on converting the installers. Im getting this error in Candle: C:\localdev\Installation\GetMyGreenInstaller\GetMyGreenWebInstaller.wxs(91) : error CNDL0005 : The Component element contains an unexpected child element WebSite'. Using Votive I get a better description, but basically it says the element should be in namespace 'http://schemas.microsoft.com/wix/2006/wi' as well as any element in namespace '##other'. In the schema description it says the WebSite element is in the ##other namespace, but how do I specify I want to use it? Or do I need to? I tried this, but to no avail: candle.exe -ext WixIIsExtension.dll InstallerProject.wxs -out wixobj.obj Am I dumb? I cant figure it out. Thanks in advance for any tips! -- Matthew Janulewicz SCM Engineer Green Dot Corporation [EMAIL PROTECTED] (626) 775-3857 - 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] DifxApp
I think you need to include difxapp.wixlib in the command line to light.exe. I believe difxapp.wixlib is in the WDK. If this doesn't work (the DIFxApp documentation on MSDN seems to refer to WiX 2.0) then my next question is around case-sensitivity: the documentation refers to MsiProcessDrivers, not MSIProcessDrivers. Unless, of course, the documentation is wrong. This could just be your transcription error, though: the source code definitely gives MsiProcessDrivers. See http://msdn.microsoft.com/library/default.asp?url="">for using DIFxApp with WiX. In WiX 3.0, the extension can supply the .wixlib internally from a resource(by overriding the GetLibrary method) but it appears that WixDifxAppExtension doesn't do this yet. -- Mike Dimmick From: [EMAIL PROTECTED] on behalf of Dennis RoySent: Thu 21/09/2006 21:04To: wix-users@lists.sourceforge.netSubject: [WiX-users] DifxApp I sent this to wix-devs and then realized is should probably go to wix-users. I get an error LGHT0094 : Unresolved reference to symbol CustomAction:MSIProcessDrivers in section Fragment:. When trying run light on my project. The command line Im running is light ext WixDifxAppExtension out install.msi *.wixobj . Im using version 3.0.2015. Any suggestions as to what Im doing wrong. Thanks Dennis - 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] how to add URL info in MSI
Thanks, Mike. As I understand, ARPHELPLINK property can be used to add product support URL at Add/Remove programs panel. What I intend to do is to add URL at the setup UI dialog. Any suggestion? -ning From: Mike Dimmick [mailto:[EMAIL PROTECTED] Sent: Thursday, September 21, 2006 2:30 PM To: Ning Yang; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] how to add URL info in MSI Use a Property element to set the ARPHELPLINK property. See http://msdn.microsoft.com/library/default.asp?url="">for details. -- Mike Dimmick From: [EMAIL PROTECTED] on behalf of Ning Yang Sent: Thu 21/09/2006 21:06 To: wix-users@lists.sourceforge.net Subject: [WiX-users] how to add URL info in MSI Hi, Im looking for the way to add URL info in MSI. When ask user to choose the options also add a hyper-link to provide more information. Is there any way to do it? Thanks a lot. Ning - 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
[WiX-users] Votive v3 has been re-released!
All of the issues have (hopefully) been fixed and the new build should be good to go. You can find it at http://wix.sourceforge.net/releases/3.0.2120.0/Wix3.msi. Let me know what you think! Thanks, Justin - 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] how to add URL info in MSI
You mean add a hyperlink to a MSI dialog? If so, then No, the Windows Installer does not support hyperlinks. You'd have to go to an external UI handler and that is a whole lot of work that just isn't worth it. I'd suggest a button instead. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ning Yang Sent: Thursday, September 21, 2006 13:06 To: wix-users@lists.sourceforge.net Subject: [WiX-users] how to add URL info in MSI Hi, Im looking for the way to add URL info in MSI. When ask user to choose the options also add a hyper-link to provide more information. Is there any way to do it? Thanks a lot. Ning - 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] Wix 3 and WebSite element
Also, note that there is a tool called WixCop that will automagically upgrade your WiX v2 source code to WiX v3 source code. It handles cases like this. It can save you significant amounts of time. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Dimmick Sent: Thursday, September 21, 2006 13:51 To: Matthew Janulewicz; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Wix 3 and WebSite element WebSite appears to have been moved into the http://schemas.microsoft.com/wix/IIsExtensionnamespace. You'll need to add an xmlns:iis attribute to the Wix element, and reference WebSite as iis:WebSite. I think. I'm not too hot on XML Namespaces, but I think it should look like: ?xml version='1.0'? Wix xmlns='http://schemas.microsoft.com/wix/2006/wi' xmlns:iis='http://schemas.microsoft.com/wix/IIsExtension' Product ... ... Component ... iis:WebSite ... / /Component /Product /Wix To get IntelliSense for WebSite (etc) in Visual Studio, add iis.xsd (in your [WiX install folder]\doc) to the list of schemas. -- Mike Dimmick From: [EMAIL PROTECTED] on behalf of Matthew Janulewicz Sent: Thu 21/09/2006 21:02 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix 3 and WebSite element Im a Wix newbie, sorta. About a month ago. I had some installers for our websites using Wix 2. We are in the process of moving to VisualStudio 2005 so I thought Id get a head start on converting the installers. Im getting this error in Candle: C:\localdev\Installation\GetMyGreenInstaller\GetMyGreenWebInstaller.wxs(91) : error CNDL0005 : The Component element contains an unexpected child element WebSite'. Using Votive I get a better description, but basically it says the element should be in namespace 'http://schemas.microsoft.com/wix/2006/wi' as well as any element in namespace '##other'. In the schema description it says the WebSite element is in the ##other namespace, but how do I specify I want to use it? Or do I need to? I tried this, but to no avail: candle.exe -ext WixIIsExtension.dll InstallerProject.wxs -out wixobj.obj Am I dumb? I cant figure it out. Thanks in advance for any tips! -- Matthew Janulewicz SCM Engineer Green Dot Corporation [EMAIL PROTECTED] (626) 775-3857 - 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] NativeImage element in NetFx
0. I was not intimately involved with the NGen development so if I sound like I don't know what I'm talking about, I don't and I'm sorry. 1. Verbose log of the failed uninstall should show much more detail. 2. Not sure. It looks like install and uninstall use the same entry point so they must be the same return value checking. We could create different entry points and modify the CustomAction. I'll bounce this off K and see what he thinks (since he wrote that part). 3. Unfortunately in WiX v2, you have to actually modify the .wixlib. In WiX v3 the condition could be overridden but I think you'd need to modify the .wixlib. Really this sounds more like a bug issue. Can you open a bug on Source Forge to track it and I'll ping K right away. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Kuhne Sent: Thursday, September 21, 2006 12:54 To: WiX-users@lists.sourceforge.net Subject: [WiX-users] NativeImage element in NetFx Im using this element in WiX 2.0. For the most part its been fine, but with internal product builds Ive had a few users hit a failure with uninstall where ngen returns that the assembly has already been uninstalled. This causes uninstalls to fail. I havent been able to get repro steps. Im left with a few questions: 1. Any suggestions on potential reasons for this or how I might track it down? 2. Why fail at all on uninstall with ngen? 3. Is it possible for me to override the custom action info for the extension in WiX? (ie- to ignore failures) My big concern is that we get inundated with support calls to help uninstall the application- I dont know of an easy way to skip extension actions with WiX (see the above #3). Thanks, -Jeremy - 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] install multiple instances of app?
There is a topic in the MSI SDK about creating multiple instance MSI files. It is pretty tricky and a fair bit of work (not much different than proposed, but transforms are used to minimize the number of MSIs distributed). I do *not* recommend using CopyFile to try and solve this problem. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Dimmick Sent: Thursday, September 21, 2006 03:43 To: Dmitry Briliuk; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] install multiple instances of app? It's worse than that. Components should always have the same path, so you really need to generate new GUIDs for all the components for each instance. MSDE 2000 duplicates every component that needs to be isolated to an instance and uses a condition 'InstanceComponentSet.n' where n is 1 to 16 to choose which components are installed for an instance. It then has a DLL custom action (type 1) to set the appropriate InstanceComponentSet.n property, which selects the required files. They must also be doing something else to associate the right files to the components, because Orca only shows the files once in the File table. Is it possible to edit the running copy of the MSI from a custom action? There are 17 MSIs supplied which appear to contain the same information, but have different package and product codes. I'm not quite sure what the purpose of the supplied patches in Release A is - it seems to merely change the product name from 'Microsoft SQL Server Desktop Engine' to 'SQL Server 2000 Desktop Edition'. The actual files are in a CAB shared by all the MSIs. This is what I'm able to guess by viewing the MSIs in Orca. I don't suppose anyone from the SQL Server team would like to explain how exactly it works? Given the extreme complexity, I'd say that trying to make independently-uninstallable and independently-updatable instances is a non-starter unless you're the SQL Server team. If you do want to make duplicate files from a single installer, you can use the CopyFile element under the File element to be duplicated. Presumably you could use some Condition to turn a particular CopyFile element on or off, but you'll have to author one CopyFile action for each instance you want to support. I don't think you'll be able to support having different versions in different directories, though - when you update, all folders would be updated at the same time. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dmitry Briliuk Sent: 21 September 2006 10:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] install multiple instances of app? It is required to intall web application multiple times on the same server (i.e. into different web sites), or make multiple copies during single install. Each copy should have its own location (at least own Web.Config file) and perhaps own item in unistall list, preferable each copy to have own suffix, i.e. My application on Website1/My application on Website2, etc. How to do this? WiX msi allows only one instance. The only idea was to make few packages with different guids, or ajust package/product guid at runtime, but it seems not a good style. TIA - 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=DEVDE V ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - 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 - 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] Question about additional translations
Hi Jim,... You can of course use the files which are in WDK: C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Samples\SysMgmt\Msi\database\INTL These files include already translated texts for common Action and Error texts. You can create simple script to create the wxl files from these files. Hope it will help you. regards Stefan Jim Hewes wrote: I've been working to convert our current InstallShield installer to WiX 2.0 and everything's working fine. But the thing that's actually preventing me from switching is that I need five languages for the GUI: English, French, Spanish, Italian, and German. Currently French and Italian are not available. There are a lot of strings there and I don't really have the available resources to do all that myself. I realize that it's a volunteer effort. So I think that means that the translations may happen next week, or they may never happen at all, true? I guess my question is: what hope do I have? Is there a definite expectation for more languages to be done? Also, I should throw another question in while I'm at it. Will WiX 3.0 have a different GUI? Will that invalidate all the existing languages? Or will the existing language files be updated at the same time? Thanks for any info! Jim -- Stefan Pavlik | [EMAIL PROTECTED] Whitestein Technologies | www.whitestein.com Panenska 28 | SK-81103 Bratislava | Slovak Republic Tel +421(2)5930-0735 | Fax +421(2)5443-5512 - 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
