[WiX-users] group policy
Hello, I would like to create msi package (executable, shortcuts, file association) and use it with Group Policy in MS Windows Server 2003. Both server and client (MS Windows 2000) are running under Virtual PC (this should not be problem). I just can not do it properly. Could someone provide me example wxs file? I do not know what I am doing wrong. Thanks S. Kunc - 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] Performance issues
Title: Performance issues Simon Topley wrote: I'm sure this is a problem others have encounted. I have now replace our suite of installsheild products with spanky new WIX versions. I have managed to elimitnate a large amount of redundant code (previous installers copied large amounts of file that were never used). Most of the installers are now half the size in compressed form. Dispite this the installation process now takes longer (so I'm told, I intend to run some performance tests later today). Is there a standard explaination for this that I can give to people (i.e. talk to city hall) I am playing with the idea of having internal versions (products that will only be used by testers and support staff) as uncompressed in the hope that most of the time is being spent extracting files. Was the InstallShield package also compressed? Are the tests being run over the network? Sometimes bandwidth constraints make it faster to have a compressed image. -- sig://boB http://bobs.org - 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] Performance issues
Title: Performance issues InstallShield versions were compressed yes, I ran some tests and here are the results (as accurate as I can get them): Installsheild Versions: Product Size Install Time Floodwork 178 mb 2:25.5 infonet mapx 155 mb infonet mapo 153 mb 1:40.5 infoworks demo 272 mb infoworks mapx 403mb 2:51.7 infoworks mapo 422mb 2:57.2 (installed without sample data) Windows Installer Versions: Product Size Install Time floodworks: 121mb 3:21.6 floodworks tutorial: 38mb infonet mapx: 78mb infonet mapo: 83mb 2:15.1 infonet tutorial 22mb infoworks demo: 222 mb infoworks mapx 185mb 2:58.9 inworks mapo 190mb 3:01.9 combined infoworks tutorials: 46mb That will probably read as total gibberish on the mailing list. Aanyway, the short version is that the performance hit isn't too bad at all, it just seems longer to the people in support because it takes longer to load and doesn't tell them the name of every file it is copying as it does so. There are a few installers that have a heavy hit (the ones in the list are just the main players, there are a load more). I suspect that the stupid slow versions have issues that are as yet unknown. I tried running an uncompressed version and saved about 30 second off a 3 minute install time. Windows installers are certainly slower, but not by much, it's worth the trade off for ease of delivery, not to mention maintenance. Simon From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: 03 August 2006 15:34To: Simon TopleyCc: 'wix-users@lists.sourceforge.net'Subject: Re: [WiX-users] Performance issues Simon Topley wrote: I'm sure this is a problem others have encounted. I have now replace our suite of installsheild products with spanky new WIX versions. I have managed to elimitnate a large amount of redundant code (previous installers copied large amounts of file that were never used). Most of the installers are now half the size in compressed form. Dispite this the installation process now takes longer (so I'm told, I intend to run some performance tests later today). Is there a standard explaination for this that I can give to people (i.e. talk to city hall) I am playing with the idea of having internal versions (products that will only be used by testers and support staff) as uncompressed in the hope that most of the time is being spent extracting files.Was the InstallShield package also compressed? Are the tests being run over the network? Sometimes bandwidth constraints make it faster to have a compressed image. -- sig://boB http://bobs.org The information contained in this e-mail is likely to be confidential and may be legally privileged. It is intended only for the addressee. If you have received this message in error please notify the sender immediately at the above address. The disclosure, copying or distribution of this message or its contents without the prior approval of Wallingford Software Ltd. is strictly prohibited. Wallingford Software Ltd. is not liable for unauthorised disclosures nor for subsequent actions or omissions in reliance upon them. - 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] group policy
Standa Kunc wrote: I would like to create msi package (executable, shortcuts, file association) and use it with Group Policy in MS Windows Server 2003. Both server and client (MS Windows 2000) are running under Virtual PC (this should not be problem). I just can not do it properly. Could someone provide me example wxs file? I do not know what I am doing wrong. What problems are you having? Have you seen the doc and tutorial link at http://wix.sourceforge.net/? Group policy and SMS just need MSI packages that support silent installation. -- sig://boB http://bobs.org - 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] Calling custom actions in Merge Modules
Hi I have a merge module that I created including all the files for a product, including the exe. I now want to launch that exe at the end of my main wix project. I have tried using a custom action which was created in the merge module as below Publish Event='DoAction' Value=LaunchFile.8757FF80_A4ED_45C0_8672_55821E0CB48F(NOT Installed) AND (LAUNCHPRODUCT = 1)/Publish But light complains about not knowing what this reference is. I have added this by hand using Orca and it works so how can I get Wix to understand it. Cheers Stuart Cullen Confidentiality: This communication contains information which is confidential. It is for the exclusive use of the intended recipient(s). __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/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
[WiX-users] Keep files after uninstall
Hello, What is the correct way of installing files which i don't want to uninstall later, or only uninstall with a custom action (eg. important databases). I read that files in a component without GUID will not be uninstalled. Is this the way to go? 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
Re: [WiX-users] Keep files after uninstall
Rob is right. Permanent is better than absent GUID because you can still patch the files. However, be very careful about what you leave behind. It would be very, very bad to leave behind files that could have security exploits in them. Nobody would know to patch them. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: Thursday, August 03, 2006 7:15 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Keep files after uninstall That's true, but I prefer to set [EMAIL PROTECTED]yes. That way you can still specify a GUID and track it, patch it, etc. Rob - 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] Performance issues
Title: Performance issues When you say youve replaced InstallShield with the WiX toolset, what version of InstallShield did you replace? I ask because the non-MSI versions of InstallShield used a scripting engine to do the install. That engine (as Ive been told) doesnt do nearly the same amount of integrity checking that the Windows Installer does. For example, the Windows Installer maintains a rollback script of all the files that were replaced during the installation. Thus, if the user cancels, everything gets put back the way it was. That adds overhead that most installation technologies dont implement (and one of the reasons I cringe every time I see another product released on those engines). Now, if you were using InstallShield for Windows Installer and the package you created with the WiX toolset was slower... well, then the WiX toolset probably has a bug. smile/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simon Topley Sent: Thursday, August 03, 2006 1:12 AM To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] Performance issues Good morning to the Brotherhood/Sisterhood, I'm sure this is a problem others have encounted. I have now replace our suite of installsheild products with spanky new WIX versions. I have managed to elimitnate a large amount of redundant code (previous installers copied large amounts of file that were never used). Most of the installers are now half the size in compressed form. Dispite this the installation process now takes longer (so I'm told, I intend to run some performance tests later today). Is there a standard explaination for this that I can give to people (i.e. talk to city hall) I am playing with the idea of having internal versions (products that will only be used by testers and support staff) as uncompressed in the hope that most of the time is being spent extracting files. Simon The information contained in this e-mail is likely to be confidential and may be legally privileged. It is intended only for the addressee. If you have received this message in error please notify the sender immediately at the above address. The disclosure, copying or distribution of this message or its contents without the prior approval of Wallingford Software Ltd. is strictly prohibited. Wallingford Software Ltd. is not liable for unauthorised disclosures nor for subsequent actions or omissions in reliance upon them. - 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] Performance issues
Title: Performance issues Now that you have these comparisons, I suggest generating a verbose log file and seeing where your time is spent in the Windows Installer. Each action has a start and stop so that should be pretty easy. You may find something surprising (like a CustomAction taking a lot of time or network latency being weird). Or you just might find that copying files with rollback takes longer... smile/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simon Topley Sent: Thursday, August 03, 2006 7:44 AM To: 'Bob Arnson'; Simon Topley Cc: 'wix-users@lists.sourceforge.net' Subject: Re: [WiX-users] Performance issues InstallShield versions were compressed yes, I ran some tests and here are the results (as accurate as I can get them): Installsheild Versions: Product Size Install Time Floodwork 178 mb 2:25.5 infonet mapx 155 mb infonet mapo 153 mb 1:40.5 infoworks demo 272 mb infoworks mapx 403mb 2:51.7 infoworks mapo 422mb 2:57.2 (installed without sample data) Windows Installer Versions: Product Size Install Time floodworks: 121mb 3:21.6 floodworks tutorial: 38mb infonet mapx: 78mb infonet mapo: 83mb 2:15.1 infonet tutorial 22mb infoworks demo: 222 mb infoworks mapx 185mb 2:58.9 inworks mapo 190mb 3:01.9 combined infoworks tutorials: 46mb That will probably read as total gibberish on the mailing list. Aanyway, the short version is that the performance hit isn't too bad at all, it just seems longer to the people in support because it takes longer to load and doesn't tell them the name of every file it is copying as it does so. There are a few installers that have a heavy hit (the ones in the list are just the main players, there are a load more). I suspect that the stupid slow versions have issues that are as yet unknown. I tried running an uncompressed version and saved about 30 second off a 3 minute install time. Windows installers are certainly slower, but not by much, it's worth the trade off for ease of delivery, not to mention maintenance. Simon From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: 03 August 2006 15:34 To: Simon Topley Cc: 'wix-users@lists.sourceforge.net' Subject: Re: [WiX-users] Performance issues Simon Topley wrote: I'm sure this is a problem others have encounted. I have now replace our suite of installsheild products with spanky new WIX versions. I have managed to elimitnate a large amount of redundant code (previous installers copied large amounts of file that were never used). Most of the installers are now half the size in compressed form. Dispite this the installation process now takes longer (so I'm told, I intend to run some performance tests later today). Is there a standard explaination for this that I can give to people (i.e. talk to city hall) I am playing with the idea of having internal versions (products that will only be used by testers and support staff) as uncompressed in the hope that most of the time is being spent extracting files. Was the InstallShield package also compressed? Are the tests being run over the network? Sometimes bandwidth constraints make it faster to have a compressed image. -- sig://boBhttp://bobs.org The information contained in this e-mail is likely to be confidential and may be legally privileged. It is intended only for the addressee. If you have received this message in error please notify the sender immediately at the above address. The disclosure, copying or distribution of this message or its contents without the prior approval of Wallingford Software Ltd. is strictly prohibited. Wallingford Software Ltd. is not liable for unauthorised disclosures nor for subsequent actions or omissions in reliance upon them. - 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] Performance issues
Title: Performance issues Preaching to the choir there, we were using an old shonky none msi version of installshield. It clearly did less work, it's just hard explaining that to users/support staff, when all they see is the end result. With the previous version the guy who wrote it put a million workarounds in there to allow our support staff to install multiple copies of the same version of the product... Trying to explain that this is bad practice just gets me insults. Oh well, all is well now, the performance figures have calmed people down a little now that they realize they are complaining about nothing. Cheers Rob. From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: 03 August 2006 16:17To: 'Simon Topley'; wix-users@lists.sourceforge.netSubject: RE: [WiX-users] Performance issues When you say you've replaced InstallShield with the WiX toolset, what version of InstallShield did you replace? I ask because the non-MSI versions of InstallShield used a scripting engine to do the install. That engine (as I've been told) doesn't do nearly the same amount of integrity checking that the Windows Installer does. For example, the Windows Installer maintains a rollback script of all the files that were replaced during the installation. Thus, if the user cancels, everything gets put back the way it was. That adds overhead that most installation technologies don't implement (and one of the reasons I cringe every time I see another product released on those engines). Now, if you were using InstallShield for Windows Installer and the package you created with the WiX toolset was slower... well, then the WiX toolset probably has a bug. smile/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simon TopleySent: Thursday, August 03, 2006 1:12 AMTo: 'wix-users@lists.sourceforge.net'Subject: [WiX-users] Performance issues Good morning to the Brotherhood/Sisterhood, I'm sure this is a problem others have encounted. I have now replace our suite of installsheild products with spanky new WIX versions. I have managed to elimitnate a large amount of redundant code (previous installers copied large amounts of file that were never used). Most of the installers are now half the size in compressed form. Dispite this the installation process now takes longer (so I'm told, I intend to run some performance tests later today). Is there a standard explaination for this that I can give to people (i.e. talk to city hall) I am playing with the idea of having internal versions (products that will only be used by testers and support staff) as uncompressed in the hope that most of the time is being spent extracting files. Simon The information contained in this e-mail is likely to be confidential and may be legally privileged. It is intended only for the addressee. If you have received this message in error please notify the sender immediately at the above address. The disclosure, copying or distribution of this message or its contents without the prior approval of Wallingford Software Ltd. is strictly prohibited. Wallingford Software Ltd. is not liable for unauthorised disclosures nor for subsequent actions or omissions in reliance upon them. The information contained in this e-mail is likely to be confidential and may be legally privileged. It is intended only for the addressee. If you have received this message in error please notify the sender immediately at the above address. The disclosure, copying or distribution of this message or its contents without the prior approval of Wallingford Software Ltd. is strictly prohibited. Wallingford Software Ltd. is not liable for unauthorised disclosures nor for subsequent actions or omissions in reliance upon them. - 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] Calling custom actions in Merge Modules
You should not be referencing a custom action from a merge module in a main installation. Who wrote the custom action? If its yours then you should use wixlib files instead of merge modules. If its not yours, whoever did write it should have made it a table-driven custom action. Derek From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stuart Cullen Sent: Thursday, August 03, 2006 7:46 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Calling custom actions in Merge Modules Hi I have a merge module that I created including all the files for a product, including the exe. I now want to launch that exe at the end of my main wix project. I have tried using a custom action which was created in the merge module as below Publish Event='DoAction' Value=LaunchFile.8757FF80_A4ED_45C0_8672_55821E0CB48F(NOT Installed) AND (LAUNCHPRODUCT = 1)/Publish But light complains about not knowing what this reference is. I have added this by hand using Orca and it works so how can I get Wix to understand it. Cheers Stuart Cullen Confidentiality: This communication contains information which is confidential. It is for the exclusive use of the intended recipient(s). __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/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] Performance issues
Title: Performance issues What are the install times like if you disable system restore? Apparently MSI installations take a large up-front hit while loading on system restore and disabling it (assuming you dont use it), can speed things up quite a bit. Derek From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simon Topley Sent: Thursday, August 03, 2006 8:26 AM To: '[EMAIL PROTECTED]'; Simon Topley; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Performance issues Preaching to the choir there, we were using an old shonky none msi version of installshield. It clearly did less work, it's just hard explaining that to users/support staff, when all they see is the end result. With the previous version the guy who wrote it put a million workarounds in there to allow our support staff to install multiple copies of the same version of the product... Trying to explain that this is bad practice just gets me insults. Oh well, all is well now, the performance figures have calmed people down a little now that they realize they are complaining about nothing. Cheers Rob. From: Rob Mensching [mailto:[EMAIL PROTECTED]] Sent: 03 August 2006 16:17 To: 'Simon Topley'; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Performance issues When you say you've replaced InstallShield with the WiX toolset, what version of InstallShield did you replace? I ask because the non-MSI versions of InstallShield used a scripting engine to do the install. That engine (as I've been told) doesn't do nearly the same amount of integrity checking that the Windows Installer does. For example, the Windows Installer maintains a rollback script of all the files that were replaced during the installation. Thus, if the user cancels, everything gets put back the way it was. That adds overhead that most installation technologies don't implement (and one of the reasons I cringe every time I see another product released on those engines). Now, if you were using InstallShield for Windows Installer and the package you created with the WiX toolset was slower... well, then the WiX toolset probably has a bug. smile/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simon Topley Sent: Thursday, August 03, 2006 1:12 AM To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] Performance issues Good morning to the Brotherhood/Sisterhood, I'm sure this is a problem others have encounted. I have now replace our suite of installsheild products with spanky new WIX versions. I have managed to elimitnate a large amount of redundant code (previous installers copied large amounts of file that were never used). Most of the installers are now half the size in compressed form. Dispite this the installation process now takes longer (so I'm told, I intend to run some performance tests later today). Is there a standard explaination for this that I can give to people (i.e. talk to city hall) I am playing with the idea of having internal versions (products that will only be used by testers and support staff) as uncompressed in the hope that most of the time is being spent extracting files. Simon The information contained in this e-mail is likely to be confidential and may be legally privileged. It is intended only for the addressee. If you have received this message in error please notify the sender immediately at the above address. The disclosure, copying or distribution of this message or its contents without the prior approval of Wallingford Software Ltd. is strictly prohibited. Wallingford Software Ltd. is not liable for unauthorised disclosures nor for subsequent actions or omissions in reliance upon them. The information contained in this e-mail is likely to be confidential and may be legally privileged. It is intended only for the addressee. If you have received this message in error please notify the sender immediately at the above address. The disclosure, copying or distribution of this message or its contents without the prior approval of Wallingford Software Ltd. is strictly prohibited. Wallingford Software Ltd. is not liable for unauthorised disclosures nor for subsequent actions or omissions in reliance upon them. - 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] WixUI_Minimal without license agreement
Im surprised Bob hasnt responded to this yet J Im not sure how it works in WiX 2.0, but in 3.0, doing something like this should be very easy since we moved all the dialog flow into one file apiece for each of the dialog packs (mondo, minimal, etc). You can just take the single file for a pack that is closest to what you want, copy it to your setup sources, tweak it as necessary, then link call light with -ext WixUIExtension like normal and be done. You dont need to set various properties, re-compile the library or anything like that. It should be exceedingly simple for 3.0. Derek From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Beaudet Sent: Thursday, August 03, 2006 11:51 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WixUI_Minimal without license agreement Scott, I have the same concern except that I'm referencing the WixUI_FeatureTree. I should say that I'm still working my way through the tutorial so the answer may be in there but I'd sure like to hit the easy button and find a way to make the license screen disappear. My installer is for our field techs who can't agree on anything much less whether or not to accept some licensing terms. ;) Brian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam Sent: Thursday, August 03, 2006 1:12 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WixUI_Minimal without license agreement I want to use the Minimal wixui because I want the user to be able to just click next and have the install go, but I dont want eula in it. Is there any way to use the regular welcomeDlg in place of the WelcomeEulaDlg. I get an error 2803 when I click the next button when I tried just changing the dialogRef. What am I missing? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Thursday, August 03, 2006 10:57 AM To: Simon Porter Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] installing fonts via msi Simon Porter wrote: I'm trying to put together a simple msi that will install a bunch of fontsthat I can then deploy using active directory. The problem I'm gettingthough is when I run the setup program it complains that it couldn'tregister the fonts and to check I have sufficient permissions. I amcurrently logged on as the local admin and domain admin. The log contains this message too: Cannot get the font title for LT_50255.ttf. The doc is kinda ambiguous but it does say: Font name. It is recommended that you leave this column null for TrueType Fonts and TrueType Collections because the installer can register the font after reading the correct font title from the font file. If the font name is entered, it must be identical to font title from the font file. You must specify a title for fonts that do not have embedded names, such as .fon files. So not being able to read the font title is probably a genuine error condition. -- sig://boBhttp://bobs.org - 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] WixUI_Minimal without license agreement
I got it working for the feature_tree one. You have to remove the dialogref for the licenseagreementdlg. Then delete these lines: Property Id=WixUI_LicenseAgreementDlg_Back Value=WelcomeDlg / Property Id=WixUI_LicenseAgreementDlg_Next Value=CustomizeDlg / Then change this line Property Id=WixUI_CustomizeDlg_BackFeatureTree Value=LicenseAgreementDlg / To Property Id=WixUI_CustomizeDlg_BackFeatureTree Value=WelcomeDlg / And change this line Property Id=WixUI_WelcomeDlg_Next Value=LicenseAgreementDlg / to Property Id=WixUI_WelcomeDlg_Next Value=CustomizeDlg / And make sure you add the dialogref DialogRef Id=WelcomeDlg / But the minimal one seems to work differently. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Beaudet Sent: Thursday, August 03, 2006 2:51 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WixUI_Minimal without license agreement Scott, I have the same concern except that I'm referencing the WixUI_FeatureTree. I should say that I'm still working my way through the tutorial so the answer may be in there but I'd sure like to hit the easy button and find a way to make the license screen disappear. My installer is for our field techs who can't agree on anything much less whether or not to accept some licensing terms. ;) Brian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam Sent: Thursday, August 03, 2006 1:12 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WixUI_Minimal without license agreement I want to use the Minimal wixui because I want the user to be able to just click next and have the install go, but I dont want eula in it. Is there any way to use the regular welcomeDlg in place of the WelcomeEulaDlg. I get an error 2803 when I click the next button when I tried just changing the dialogRef. What am I missing? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Thursday, August 03, 2006 10:57 AM To: Simon Porter Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] installing fonts via msi Simon Porter wrote: I'm trying to put together a simple msi that will install a bunch of fontsthat I can then deploy using active directory. The problem I'm gettingthough is when I run the setup program it complains that it couldn'tregister the fonts and to check I have sufficient permissions. I amcurrently logged on as the local admin and domain admin. The log contains this message too: Cannot get the font title for LT_50255.ttf. The doc is kinda ambiguous but it does say: Font name. It is recommended that you leave this column null for TrueType Fonts and TrueType Collections because the installer can register the font after reading the correct font title from the font file. If the font name is entered, it must be identical to font title from the font file. You must specify a title for fonts that do not have embedded names, such as .fon files. So not being able to read the font title is probably a genuine error condition. -- sig://boBhttp://bobs.org - 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] WixUI_Minimal without license agreement
This is for a product we hope to release in the next month, so we are using wix 2.0 right now. Is there any way to do this with wix 2.0? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Derek Cicerone Sent: Thursday, August 03, 2006 2:58 PM To: 'Brian Beaudet'; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WixUI_Minimal without license agreement Im surprised Bob hasnt responded to this yet J Im not sure how it works in WiX 2.0, but in 3.0, doing something like this should be very easy since we moved all the dialog flow into one file apiece for each of the dialog packs (mondo, minimal, etc). You can just take the single file for a pack that is closest to what you want, copy it to your setup sources, tweak it as necessary, then link call light with -ext WixUIExtension like normal and be done. You dont need to set various properties, re-compile the library or anything like that. It should be exceedingly simple for 3.0. Derek From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Beaudet Sent: Thursday, August 03, 2006 11:51 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WixUI_Minimal without license agreement Scott, I have the same concern except that I'm referencing the WixUI_FeatureTree. I should say that I'm still working my way through the tutorial so the answer may be in there but I'd sure like to hit the easy button and find a way to make the license screen disappear. My installer is for our field techs who can't agree on anything much less whether or not to accept some licensing terms. ;) Brian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam Sent: Thursday, August 03, 2006 1:12 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WixUI_Minimal without license agreement I want to use the Minimal wixui because I want the user to be able to just click next and have the install go, but I dont want eula in it. Is there any way to use the regular welcomeDlg in place of the WelcomeEulaDlg. I get an error 2803 when I click the next button when I tried just changing the dialogRef. What am I missing? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Thursday, August 03, 2006 10:57 AM To: Simon Porter Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] installing fonts via msi Simon Porter wrote: I'm trying to put together a simple msi that will install a bunch of fontsthat I can then deploy using active directory. The problem I'm gettingthough is when I run the setup program it complains that it couldn'tregister the fonts and to check I have sufficient permissions. I amcurrently logged on as the local admin and domain admin. The log contains this message too: Cannot get the font title for LT_50255.ttf. The doc is kinda ambiguous but it does say: Font name. It is recommended that you leave this column null for TrueType Fonts and TrueType Collections because the installer can register the font after reading the correct font title from the font file. If the font name is entered, it must be identical to font title from the font file. You must specify a title for fonts that do not have embedded names, such as .fon files. So not being able to read the font title is probably a genuine error condition. -- sig://boBhttp://bobs.org - 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] ScrollableText Control type
OK I've been having a really bad time with this. For some reason it won't display anything. I want it to display information form a .txt file since its a lot smaller than a .rtf I have'nt really seen anywhere that says this won't work and in all the other controls it works just fine. Is there something I'm missing? I've even tried using Orca and replacing the what goes in here and it say that .txt is a proper format. -- View this message in context: http://www.nabble.com/ScrollableText-Control-type-tf2048066.html#a5640741 Sent from the wix-users forum 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
Re: [WiX-users] rfc: Package element changes
Title: RE: [WiX-users] rfc: Package element changes Thanks for the feedback Jeremy. I think thats a valid concern, so the warning idea is definitely out. So it sounds like the decision is basically between using * or lots of question marks. If people feel that the star syntax is clearly better, then I agree its a good idea. But if theres no clear consensus on it being a win then we might just leave it alone since everyone is already familiar with the current syntax. Derek From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Farrell Sent: Thursday, August 03, 2006 3:52 PM To: WiX-users Subject: Re: [WiX-users] rfc: Package element changes From: Bob Arnson Sent: Wed 8/2/2006 8:44 AM Derek Cicerone wrote: I've done some more thinking about this. I think Rob's main objection with making Product/@Id optional was that someone might accidentally forget to specify it. However, what if we displayed a warning to the user whenever they omitted the Property/@Id attribute informing them that doing so is non-standard and would result in generating a new ProductCode for each build - thus making it impossible to do anything other than major upgrades. Why should that be a warning? I agree totally. As far as I'm concerned this is a useful feature. I want to be sure the ProductCode changes every time, to ensure that it is impossible to do anything other than major upgrades. This may be an unusual requirement, but it's a valid one and I shouldn't like to see a warning for it. I'm sure mine isn't the only environment where warnings are forbidden in production builds. If this were to generate a warning, the warning ought to be very specific to this case, and it should be possible to suppress this one warning from the command line. Even that's messy though - I'd far rather there not be a warning for this. - 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] WixUI_Minimal without license agreement
Scott Sam wrote: I want to use the Minimal wixui because I want the user to be able to just click next and have the install go, but I dont want eula in it. Is there any way to use the regular welcomeDlg in place of the WelcomeEulaDlg. I get an error 2803 when I click the next button when I tried just changing the dialogRef. What am I missing? How about a low-tech solution? Put a simple readme in License.rtf and set the LicenseAccepted property to '1' -- that enables the Install button. Otherwise, you'll need to create a new dialog; the existing WelcomeDlg is designed to be the first page in a wizard, not the last. -- sig://boB http://bobs.org - 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] ScrollableText Control type
Magus wrote: OK I've been having a really bad time with this. For some reason it won't display anything. I want it to display information form a .txt file since its a lot smaller than a .rtf I have'nt really seen anywhere that says this won't work and in all the other controls it works just fine. Is there something I'm missing? I've even tried using Orca and replacing the what goes in here and it say that .txt is a proper format. The doc for the ScrollableText control says: Enter the RTF text string into the Text column of the Control table. There's nothing that says it will work, so you can't assume it supports plain text. -- sig://boB http://bobs.org - 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] group policy
Please keep wix-users on the thread so everyone can participate. Standa Kunc wrote: There are no dialogs in my setups so I suppose they support silent installation. Or is there anything else needed to create silent installation? Some checklist for silent installation? If you use standard Windows Installer actions, you get silent-install support for free. If you use custom actions, you have to ensure you code them correctly to work with different UI levels. Feature Id='MyFeature' Title='My 1st Feature' Level='1' AllowAdvertise='yes' TypicalDefault='advertise' I'm not a Group Policy expert, so I'm not sure what's wrong, but my first guess would be that you're assigning an advertised feature. The product is present but without something to engage the advertisement, no features are actually installed. -- sig://boB http://bobs.org - 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] rfc: Package element changes
Jeremy Farrell wrote: I agree totally. As far as I'm concerned this is a useful feature. I want to be sure the ProductCode changes every time, to ensure that it is impossible to do anything other than major upgrades. This may be an unusual requirement, but it's a valid one and I shouldn't like to see a warning for it. Not sure it's that unusual. Major upgrades are by far the easiest and most user friendly way to ship msi files. Tony - 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] ScrollableText Control type
http://blogs.msdn.com/robmen/archive/2006/05/30/610950.aspx From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Thursday, August 03, 2006 4:19 PM To: Magus Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] ScrollableText Control type Magus wrote: OK I've been having a really bad time with this. For some reason it won'tdisplay anything. I want it to display information form a .txt file sinceits a lot smaller than a .rtf I have'nt really seen anywhere that says thiswon't work and in all the other controls it works just fine. Is theresomething I'm missing? I've even tried using Orca and replacing the whatgoes in here and it say that .txt is a proper format. The doc for the ScrollableText control says: Enter the RTF text string into the Text column of the Control table. There's nothing that says it will work, so you can't assume it supports plain text. -- sig://boBhttp://bobs.org - 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] Temporary Directory
What I need done is to have Dsetup.exe to run. But it requires dsetup.dll and some .cab's. I keep getting an erro saying it doens't know where the dsetup.dll is. I thought of must making them components and just running a cleanup and deleting them after I used them but I am required not to do it that way. -- View this message in context: http://www.nabble.com/Temporary-Directory-tf2048729.html#a5643844 Sent from the wix-users forum 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
