Re: [WiX-users] Uninstall - questions
Thanks for the all replies! I have tested my installation on a clear VM and uninstallation was complete. Seems my development machine is dirty and that was the reason of incomplete uninstall. Best regards, Peter G. Sakhno C-MAP RUSSIA Ltd http://www.c-map.ru/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix Versions
We're using v2.0.3719.0 right now and have no problems so far which require us to update. We will eventually use WiX 3.0, but not in production this year. We currently use Votive v2 just to have intellisense for editing WiX files. I haven't tried Votive v3 yet. The core v2 toolset and UI lib are stable enough to think of it as final or at least RC. I'm not sure about the CAs, we're not using them right now. Regards, Martin -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Frederik Carlier Sent: Dienstag, 13. Juni 2006 19:47 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix Versions [This message is BCC'd to wix-devs for those who are not subscribed to wix-users, but I think it is worth keeping the discussion on wix-users only] Hi, Text quoted from Derek Cicerone (Re: [WiX-users] Localized version of License.rtf): The other option is to move to WiX 3.0. Work on the core of 3.0 is very near completion, however, I'm still nervous about groups using 3.0 that are shipping anytime in 2006. It's not a matter of us churning the schema so much anymore as just a general issue of 3.0 needing some bake time to ensure the major bugs are fleshed out. I'd like to take this comment as a starting point to have a discussion about the versions of WiX. About 10 days ago, I sent out an e-mail asking people about experiences with the latest weekly builds to decide if they can be pushed to SourceForge. Only a single person replied. I take this that many, many people are very happy with the version of WiX 2.0 they have installed and that makes me conclude that WiX 2.0 is pretty stable. The fact that some pretty big software ships with setups made with WiX only confirms that. Exceptions are the add-ons: the CA's have their know limitations and Votive and WixUI do pop up with enhancements on a regular basis). [It would be interesting to find out which builds of v2.0 people are using - maybe we should do a poll one day :)] And, work on Wix 3.0 seems to have advanced quite a bit and can show off with some compelling and working features. Quite often, the response is this works better in v3.0, we won't be porting back the change, though. I get the impression that Wix 3.0 is really worth trying out - at an early beta stage, let's say. That, thus, leads me to believe that v2.0 is finished and rather stable. So, maybe it is about time to come out with that and start thinking about talking in terms of release candidates or final versions? All this would result in v2.0's stability being confirmed and the vast improvements in v3.0 being acknowledged, so that the adventurous people can star playing with v3.0 (so that it gets more attention, and that the major bugs can be fleshed out)... Of course, that's just my opinion, but I would love to hear feedback on this. Frederik. ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] RFC: Moving Wix 3.0 to use the .NET Framework 2.0
I think its very nice that candle/light/etc now run on either. We too develop apps that must run on either so we have some dev boxes that only have 1.1 on them. Naturally this includes the automated build servers which only have 1.1 and VS2003 on them to ensure no code references 2.0 classes. Perhaps if you itemized a few pros/cons it would help make the descision clearer. eg. the impetus is these x proposed features would be significantly easier to develop using these y new 2.0 framework classes. Cant say because Im very new to wix and havent even looked at the source yet but just in thinking of what these tools do its not obvious where new 2.0 classes would be of great benefit. I dont think as a dev tool we can really say that perf is an issue and hence probably not generics either. Id have to say if there are truly time/pain saving use cases for new 2.0 framework classes then Id be open to taking the pain of having to build the installer on a 2.0 box. However if its just because of the pain having VS2003 around or the pain having to set up B to enable targeting 1.1 from VS2005 then Id lean against it. Managed plugin api wise I could certainly see how future versions of votive could only target VS2005. I think it would be a fair tradeoff to say if you want to use VS2003 youre stuck with votive 3.0 or less but thats because theres a big distinction between an authoring tool and a building tool. exactly two cents worth J, -john From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Rockwood Sent: Wednesday, June 14, 2006 1:20 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] RFC: Moving Wix 3.0 to use the .NET Framework 2.0 There has been some talk on the core team about moving Wix 3.0 over to use the .NET Framework 2.0 instead of 1.1. We wanted to know how many people this would affect and in what ways. If you have any concerns about using .NET 2.0, please respond to this email and let us know. Conversely, if moving to .NET 2.0 would help you, please let us know that as well. Thanks, Justin ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Registry key or value localization problem
Works like a champ now! I believe I just needed the encoding and codepage set in all the WXS files in the project for this to work. I did take out the explicit setting of SummaryCodepage per your recommendation also. Your help and expertise is much appreciated Derek! Jon From: Derek Cicerone [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 14, 2006 11:16 AM To: 'Watkins, Jon'; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Registry key or value localization problem That looks fine to me - have you tried just performing the install to see if it works? Sometimes Orca has problems with different languages but that doesn't necessarily mean the msi itself is wrong. Be sure to merge the module into an msi with the proper codepage set as well. (please note - the SummaryCodepage defaults to 1252, so you don't need to set it explicitly) Derek From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Watkins, Jon Sent: Wednesday, June 14, 2006 9:01 AM To: '[EMAIL PROTECTED]'; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Registry key or value localization problem I think I narrowed down the problem I'm seeing. The code below works from a Product/ WiX file but not from a merge Module/ WiX file. Component Id='AppFRA' Guid='73EF5301-BEEC-40b0-9A38-5AB812C1897D' Registry Id='ReceiveProtocolsFRA' Action='write' Root='HKLM' Key=SOFTWARE\Company\Tasks\Histoire de séance d'entraînement de Recieve\Protocols Name='1' Value=Histoire de séance d'entraînement de Recieve Type='string' / /Component I'm setting the Codepage='1252' and the SummaryCodepage='1252'. ?xml version='1.0' encoding='Windows-1252'? Wix xmlns='http://schemas.microsoft.com/wix/2003/01/wi' Module Id='TrainingAppModule' Guid='6E51C103-AF1B-4952-B5AD-958BD96B9EA3' Language='1033' Version='3.0.0.0' Codepage='1252' Package Id='----' Description='Training App Merge Module' Comments= 'Training Merge Module' Manufacturer='My Company' InstallerVersion='100' Compressed='yes' SummaryCodepage='1252' / Thanks for your help. It's much appreciated! -Jon From: Derek Cicerone [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 3:06 PM To: 'Watkins, Jon'; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Registry key or value localization problem What codepage are you setting for the package? Please show the exact authoring being used because there are two codepages in an msi package - one for the summary information and one for the package itself. We need to ensure the proper one is being set. Derek From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Watkins, Jon Sent: Monday, June 12, 2006 11:50 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Registry key or value localization problem I'm having some problems with WiX jumbling some of my translated strings (some non English characters) that go into my registry key names and values. Please let me know if anyone else has seen this before and if there's a fix known. If I manually edit the MSI after the build to correct the mixed up text then the registry keys / values install the way I want them to be. The WiX build is changing Histoire de séance d'entraînement de Recieve into Histoire de s?ance d'entra?nement de Recieve when I view in Orca. If I manually edit the MSI to correct the string to Histoire de séance d'entraînement de Recieve then the value installs correctly. Registry Id='ReceiveHistoryDEU' Action='createKeyAndRemoveKeyOnUninstall' Root='HKLM' Key=SOFTWARE\Garmin\Tasks\Histoire de séance d'entraînement de Recieve\Launch Permission User=Administrators GenericAll=yes/ Permission User=Everyone GenericExecute=yes GenericRead=yes/ /Registry Registry Id='ReceiveProtocolsFRA' Action='write' Root='HKLM' Key='SOFTWARE\Garmin\Tasks\Histoire\Protocols' Name='1' Value=Histoire de séance d'entraînement de Recieve Type='string' / Any help would be much appreciated! Best Regards, -Jon - This e-mail and any attachments may contain confidential material for the sole use of the intended recipient. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you have received this e-mail in error, please contact the sender and delete all copies. Thank you for your cooperation ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] What makes ClickThrough per-user?
i've created a one file ClickThrough install and generated the wix file associated with it. i'm wondering... what exactly makes this a per-user install? i was unable to run the ClickThrough install due to compile errors but the wix file came out fine. __ Don Tasanasanta VIACK Corporation 425-605-7423 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] What makes ClickThrough per-user?
Right now, Rob is fixing the warnings that make ClickThrough really painful to use. These were a result of recent schema changes. Its some pretty exciting changes because ClickThrough will utilize the same infrastructure as Heat. I expect the innovation in this area to flourish once all the tools use the same underlying infrastructure because it allows improvements to be distributed to all tools built on top automatically (whereas previously tallow and ClickThrough used completely separate codebases). ClickThrough is per-user because it installs to per-user locations (I believe it installs to the users app data folder). It doesnt install to any per-machine locations (like Program Files) which would require elevated privileges. This means that users without administrative privileges can install the app since it wont impact anyone but themselves. But the really exciting part of ClickThrough is that its super-easy to create a simple installation that has the ability to automatically retrieve updates from the internet whenever the user runs your application. Derek From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Don Tasanasanta Sent: Thursday, June 15, 2006 2:58 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] What makes ClickThrough per-user? i've created a one file ClickThrough install and generated the wix file associated with it. i'm wondering... what exactly makes this a per-user install? i was unable to run the ClickThrough install due to compile errors but the wix file came out fine. __ Don Tasanasanta VIACK Corporation 425-605-7423 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] What makes ClickThrough per-user?
i have tried creating a simple one file install that installs to appdata only and has no registry entries but i can't get it to install with user only access. i keep getting the same error: "This installation is forbidden by system policy. Contact your system administrator." so iwas wondering what elements/tags in the clickthrough project allow it to install with user access only. __ Don Tasanasanta VIACK Corporation 425-605-7423 From: Derek Cicerone [mailto:[EMAIL PROTECTED] Sent: Thursday, June 15, 2006 3:16 PMTo: Don Tasanasanta; wix-users@lists.sourceforge.netSubject: RE: [WiX-users] What makes ClickThrough per-user? Right now, Rob is fixing the warnings that make ClickThrough really painful to use. These were a result of recent schema changes. Its some pretty exciting changes because ClickThrough will utilize the same infrastructure as Heat. I expect the innovation in this area to flourish once all the tools use the same underlying infrastructure because it allows improvements to be distributed to all tools built on top automatically (whereas previously tallow and ClickThrough used completely separate codebases). ClickThrough is per-user because it installs to per-user locations (I believe it installs to the users app data folder). It doesnt install to any per-machine locations (like Program Files) which would require elevated privileges. This means that users without administrative privileges can install the app since it wont impact anyone but themselves. But the really exciting part of ClickThrough is that its super-easy to create a simple installation that has the ability to automatically retrieve updates from the internet whenever the user runs your application. Derek From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Don TasanasantaSent: Thursday, June 15, 2006 2:58 PMTo: wix-users@lists.sourceforge.netSubject: [WiX-users] What makes ClickThrough per-user? i've created a one file ClickThrough install and generated the wix file associated with it. i'm wondering... what exactly makes this a per-user install? i was unable to run the ClickThrough install due to compile errors but the wix file came out fine. __ Don Tasanasanta VIACK Corporation 425-605-7423 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Determine if in rollback mode from non-deferred custom action.
How do I check from a non-deferred custom action that an install/uninstall was rolled back? Thanks, --Leo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Determine if in rollback mode from non-deferred customaction.
How do I rollback an immediate (not deferred) custom action? Thanks, ---Leo From: "dangle123 ..." [EMAIL PROTECTED]To: wix-users@lists.sourceforge.netSubject: [WiX-users] Determine if in rollback mode from non-deferred customaction.Date: Thu, 15 Jun 2006 17:34:10 -0700MIME-Version: 1.0X-Originating-IP: [131.107.0.71]X-Originating-Email: [EMAIL PROTECTED]X-Sender: [EMAIL PROTECTED]Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by bay0-mc1-f6.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Thu, 15 Jun 2006 17:35:00 -0700Received: from sc8-sf-list1-new.sourceforge.net (unknown [10.3.1.93])by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTPid 31CED12B82; Thu, 15 Jun 2006 17:34:59 -0700 (PDT)Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]helo=mail.sourceforge.net)by sc8-sf-list1-new.sourceforge.net with esmtp (Exim 4.43)id 1Fr2Ib-0001yM-QXfor wix-users@lists.sourceforge.net; Thu, 15 Jun 2006 17:34:57 -0700Received: from bay106-f10.bay106.hotmail.com ([65.54.161.20] helo=hotmail.com)by mail.sourceforge.net with esmtp (Exim 4.44) id 1Fr2Ia-0001tJ-K0for wix-users@lists.sourceforge.net; Thu, 15 Jun 2006 17:34:57 -0700Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;Thu, 15 Jun 2006 17:34:11 -0700Received: from 65.54.161.200 by by106fd.bay106.hotmail.msn.com with HTTP;Fri, 16 Jun 2006 00:34:10 GMT How do I check from a non-deferred custom action that an install/uninstall was rolled back? Thanks, --Leo ___WiX-users mailing listWiX-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wix-users ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX Consultant Available?
I have posted this before on the WiX-users list before, but got only one response and it was from Rob M. who basically said that he'd like to do it but didn't think he could. Is there anyone who is or knows of a consultant that my group can hire to review my setup design? This is the first MSI based install that we have done (all previous installs were InstallScript based), and my tail is basically on the line. I have an InstallShield MSI training course under my belt, but no real world MSI experience except for the RD I have done on WiX. Our project has to use WiX because of the requirements, and the only consultants I can find for setup work at from Macrovision. I'm pretty certain that they might not enjoy being consultants for a project where we are going to be using an open source competitor to their InstallShield product. The job is in Nashville, TN. We may be able to work out remoting if you don't live in this area. My manager has asked me about this again and I'd really like to get someone good in here who can review my design before our remote team does the implementation. Thanks, Joseph Barkley Software Engineer Square D Company La Vergne, TN ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] What makes ClickThrough per-user?
Don Tasanasanta wrote: i have tried creating a simple one file install that installs to appdata only and has no registry entries but i can't get it to install with user only access. i keep getting the same error: "This installation is forbidden by system policy. Contact your system administrator." Does a verbose log have more details? so iwas wondering what elements/tags in the clickthrough project allow it to install with user access only. Per-user installs don't require any magic -- they're the MSI default, actually. I tested it on XP with a limited-user account. ?xml version="1.0" encoding="UTF-8"? Wix xmlns="http://schemas.microsoft.com/wix/2003/01/wi" Product Id="000C1109---C000-0046" Name="TestFileProduct" Language="1033" Version="0.0.0.0" UpgradeCode="5942F3FD-1C1A-48D2-9C92-E360ECC235FF" Manufacturer="Microsoft Corporation" Package Id="----" Description="Test File in a Product" Comments="Test from: wix\examples\test\assembly\product.wxs" InstallerVersion="200" Compressed="yes" / Media Id="1" Cabinet="product.cab" EmbedCab="yes" / Directory Id="TARGETDIR" Name="SourceDir" Directory Id="AppDataFolder" Name="AppData" Directory Id="TESTFILEPRODUCTDIRECTORY" Name="testassm" LongName="Test File" Component Id="TestFileProductComponent" Guid="00030829---C000-0046" DiskId="1" File Id="TestFileProductFile" Name="test.txt" Source=".\test.txt" KeyPath="yes" / /Component /Directory /Directory /Directory Feature Id="TestFileProductFeature" Title="Test File Product Feature" Level="1" ConfigurableDirectory="TESTFILEPRODUCTDIRECTORY" ComponentRef Id="TestFileProductComponent" / /Feature UIRef Id="WixUI_FeatureTree" / /Product /Wix -- sig://boB http://bobs.org ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Determine if in rollback mode from non-deferred customaction.
dangle123 ... wrote: How do I rollback an immediate (not deferred) custom action? You don't. Immediate CAs shouldn't change the system, so there's nothing to roll back. -- sig://boB http://bobs.org ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
