Re: [WiX-users] External configuration vs CustomActions
Rob, I completely agree with you on static configuration belongs in the MSI, and application configuration should live inside of the app. In my post, I didn't make this clear distinction. Very well said. Thanx, Aaron On 6/5/07, Rob Mensching <[EMAIL PROTECTED]> wrote: I'd say it differently: 1. Static configuration should go in the install. That way repair will do the right thing. 2. Defaults for configuration should go in the app directly (a static configuration file) or in the install. That way repair will do the right thing. (the above two things are ideally 100% "per-machine" settings) 3. Dynamic configuration (stuff that you expect the user to change, aka per-user) should be updated using a configuration tool (or just the app itself, Tools -> Options…). Ideally, per-user configuration is only be written when it differs from the defaults. So it goes like this: static in the install, dynamic not in the install. Now, the part that really gets hard is when you do an upgrade and previous settings need to be migrated/upgraded/or otherwise modified. IMHO, first boot of the new application is the ideal place to do this. *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Aaron Feng *Sent:* Monday, June 04, 2007 7:40 PM *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] External configuration vs CustomActions I just wrote a post on external configuration vs CustomActions. I would like to get general feedback on this particular topic. If you are interested, the link is here: http://aaronfeng.com/articles/2007/06/04/how-should-your-application-be-configured Thanx in advance. Aaron - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] External configuration vs CustomActions
I just wrote a post on external configuration vs CustomActions. I would like to get general feedback on this particular topic. If you are interested, the link is here: http://aaronfeng.com/articles/2007/06/04/how-should-your-application-be-configured Thanx in advance. Aaron - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Ignore Custom Action on Repair
Mike, Thanks for the great explanation. Now I understand what Rob was talking about before now, it all makes sense. Just for clarity, action script is created in between InstallInitialize and InstallFinalize in InstallExecuteSequence table. Does the action script only contain actions that lives in between InstallInitialize and InstallFinalize or even contains the actions after InstallFinalize? When the action script is passed to the Windows Installer service it executes the action script when InstallExecute, InstallExecuteAgain, and InstallFinalize actions are executed. Does each of these action (InstallExecute, InstallExecuteAgain, and InstallFinalize) execute the whole action script or just part of it? If part of it, how does it know which one to execute in the action script? So for example, if I have an action (in the action script too) that runs an external executable, if it fails it will cause the msi to run the roll back script. I assume it doesn't actually roll back anything on this particular action since it doesn't know about the external executable. Basically, if I understand correctly, if I want to run a custom action I need to put it some where in between InstallInitialize and InstallFinalize in the InstallExecuteSequence table or should it live some where else? Thanks again, Aaron On 5/13/07, Mike Dimmick <[EMAIL PROTECTED]> wrote: Windows Installer does things in three (possibly two) distinct phases: - UI sequence - Install execute sequence - Script execution Normally (unless set to Basic or No UI) execution begins with the UI sequence. The actions listed in the UI sequence are performed in order – normally just presenting dialogs to modify options and any necessary custom actions to gather system state data – until the ExecuteAction action is reached. This causes the InstallExecuteSequence to be processed (for an INSTALL action) If Basic or No UI are used, the UI sequence is ignored and the execute sequence runs directly. This is why it's sometimes necessary to put custom actions which set properties in both sequences. The execute sequence is then executed. At the point that the InstallInitialize action is executed, Windows Installer starts writing a script. The actions listed in the execute sequence are processed and the actual file copy/registry write/etc actions are written to the action script, and the necessary information to undo those operations are written to the rollback script. The batched-up script is passed to the Windows Installer *service* when the InstallExecute, InstallExecuteAgain, and InstallFinalize actions are executed. If an error occurs in action script execution, the rollback script is executed and the installation aborts. Almost all actions between InstallInitialize and InstallFinalize are scripted; *immediate* custom actions are performed immediately, however, while *deferred* custom actions are written into the script (along with their custom action data) and actually executed in the correct position relative to the effects of the other actions. The UI sequence and execute sequence are processed in the *client* process (shown in the logs with *(c)*) while the script is processed by the * service* process (shown as *(s)*). The part of the execution sequence between InstallInitialize and InstallFinalize is what Rob's referring to as *the transaction*, because if an operation fails for whatever reason, the changes are rolled back. Also, only one Windows Installer package can be running in this region at a time. It's recommended that all actions that change the state of the system are performed as part of the transaction, i.e. that any custom actions that change system state are *deferred* and execute between InstallInitialize and InstallFinalize. -- Mike Dimmick -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Aaron Feng *Sent:* 13 May 2007 16:49 *To:* Rob Mensching *Cc:* wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] Ignore Custom Action on Repair Rob, I'm not sure if we are both on the same page. Please choose to ignore me if I sound like I'm smoking crack. :) By no means am I a msi expert, but I would like to understand best practices in a certain situation. I can provide extra context if it would help. Ignore everything I have said so far in this thread because I will explain the situation from the beginning to avoid any confusion. In our installer we pack an encryption tool with our application. The purpose of this encryption tool is to allow clients to encrypt or decrypt their configuration files. The configuration files should be encrypted at all times when the app is running (This is part of the business requirement). The reason the tool is deployed as part of the msi package it's because in some situations the client may want to temporary decrypt and encrypt the files fo
Re: [WiX-users] Ignore Custom Action on Repair
Rob, I'm not sure if we are both on the same page. Please choose to ignore me if I sound like I'm smoking crack. :) By no means am I a msi expert, but I would like to understand best practices in a certain situation. I can provide extra context if it would help. Ignore everything I have said so far in this thread because I will explain the situation from the beginning to avoid any confusion. In our installer we pack an encryption tool with our application. The purpose of this encryption tool is to allow clients to encrypt or decrypt their configuration files. The configuration files should be encrypted at all times when the app is running (This is part of the business requirement). The reason the tool is deployed as part of the msi package it's because in some situations the client may want to temporary decrypt and encrypt the files for debugging purposes. With that said, I would like the configuration files to be automatically encrypted during the installation process. Currently I'm running a custom action with ExeCommand to achieve this. It works fine, except I noticed, it would try to run the custom action during repair. I only want this custom action to run during the initial install. I tried various condition around the custom action such as NOT Installed, didn't seem to work for me. I'm not tied down to any specific solution, just want to under best solution for this problem. If what I'm doing is completely hacky and should be avoid, I will understand. In your first reply you said the following: After InstallFinalize? That isn't part of the transaction. What do you mean it's not part of the transaction? Thanx, Aaron On 5/12/07, Rob Mensching <[EMAIL PROTECTED]> wrote: Don't try to do what you are doing. I don't have enough context to provide any better suggestions than that. *From:* Aaron Feng [mailto:[EMAIL PROTECTED] *Sent:* Saturday, May 12, 2007 10:42 AM *To:* Rob Mensching *Cc:* wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] Ignore Custom Action on Repair I would also like to avoid any trickery. Do you have any suggestions for alternatives? Thanx, Aaron On 5/12/07, *Rob Mensching* < [EMAIL PROTECTED]> wrote: Note, this sort of design is generally very fragile and I always encourage people to rethink their need for this sort of trickiery during setup. -Original Message- From: Aaron Feng [mailto:[EMAIL PROTECTED] Sent: Friday, May 11, 2007 4:49 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Ignore Custom Action on Repair I have a custom action that runs a tool during install. I do not want this tool to run during repair, in fact I only want this custom action to run only during the inital install. Currently it will attempt to run the custom action during repair which causes an error from the tool. Aaron On 5/11/07, Rob Mensching < [EMAIL PROTECTED]> wrote: > > > > > After InstallFinalize? That isn't part of the transaction. What are you > trying to accomplish? > > > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] ] On Behalf > Of Aaron Feng > Sent: Friday, May 11, 2007 2:31 PM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Ignore Custom Action on Repair > > > > > I run a custom action during install which works fine, but I don't want to > run it during repair. I tried every possible way, but no luck. Here is an > example what I'm doing: > > > > > > > > > > > > > > Thanx, > > Aaron - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Aligning Custom UI
I'll give them a try. Thanx, Aaron On 5/12/07, Mike Dimmick <[EMAIL PROTECTED]> wrote: You can use the Visual C++ dialog editor to create a .rc file then use tallow's -r option to turn that into WiX script. WixEdit (http://wixedit.sourceforge.net/) includes a dialog editor. -- Mike Dimmick -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Aaron Feng *Sent:* 12 May 2007 06:11 *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] Aligning Custom UI What is the best way to line up controls in a custom UI? I usually make an initial guess on the location and size then make the adjustments from there. This approach is painful sometimes when you keep running the installer over and over just to see if everything is aligned correctly. Is there a better way? Thanx, Aaron - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error on uninstall? - FIXED
Yeah, that's what I thought, but I'm having trouble to getting it to work. Here is my original thread: http://sourceforge.net/mailarchive/forum.php?thread_name=4e3934860705121042n26c2fd46xf03549b3eff6fd3c%40mail.gmail.com&forum_name=wix-users Aaron On 5/12/07, Rob Mensching <[EMAIL PROTECTED]> wrote: "NOT Installed" means your action should only run when the install was not installed. -Original Message- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] On Behalf Of Aaron Feng Sent: Friday, May 11, 2007 5:00 PM To: Julie Campbell Cc: Bob Arnson; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Error on uninstall? - FIXED Julie, I assume your custom action does not run during repair, but only during install? I have a custom action that runs during install, but also runs during repair which causes an error. Can you show me your custom action with the conditional text that you used to achieve this? Thanx, Aaron On 5/11/07, Julie Campbell < [EMAIL PROTECTED]> wrote: > It seems I messed up the conditional text on a custom action that was only > to run during installation. It was running during uninstall too. As this > action creates a file, in a directory that was just removed ... bad things > happened. Anyway, all better now, thanks to everyone who spared this issue > some brainwaves. > > Julie Campbell > [EMAIL PROTECTED] > > -Original Message- > From: Bob Arnson [mailto:[EMAIL PROTECTED] > Sent: Friday, May 11, 2007 2:48 AM > To: Julie Campbell > Cc: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Error on uninstall? > > Julie Campbell wrote: > > Here's what seems to be the applicable part of the log. The user error is > > something like "one or more files needed for restoration cannot be found. > > Restoration is not possible." > > > > I haven't seen that error before but the log fragment below is part of > the rollback script; it's MSI cleaning up its private data. The error is > above it. > > > I don't know what "19C29D7B9D408814D8EF629B9E4E4D76" is, it isn't a GUID > I'm > > using. > > > > It's a "compressed GUID." See http://support.microsoft.com/kb/296067/ > for some examples of how they're built to convert to the "real GUID." > > -- > sig://boB > http://joyofsetup.com/ > > > > > _ > Scanned by IBM Email Security Management Services powered by MessageLabs. > For more information please visit http://www.ers.ibm.com > > _ > > > > _ > Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com > _ > > - > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Ignore Custom Action on Repair
I would also like to avoid any trickery. Do you have any suggestions for alternatives? Thanx, Aaron On 5/12/07, Rob Mensching <[EMAIL PROTECTED]> wrote: Note, this sort of design is generally very fragile and I always encourage people to rethink their need for this sort of trickiery during setup. -Original Message- From: Aaron Feng [mailto:[EMAIL PROTECTED] Sent: Friday, May 11, 2007 4:49 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Ignore Custom Action on Repair I have a custom action that runs a tool during install. I do not want this tool to run during repair, in fact I only want this custom action to run only during the inital install. Currently it will attempt to run the custom action during repair which causes an error from the tool. Aaron On 5/11/07, Rob Mensching <[EMAIL PROTECTED]> wrote: > > > > > After InstallFinalize? That isn't part of the transaction. What are you > trying to accomplish? > > > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Aaron Feng > Sent: Friday, May 11, 2007 2:31 PM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Ignore Custom Action on Repair > > > > > I run a custom action during install which works fine, but I don't want to > run it during repair. I tried every possible way, but no luck. Here is an > example what I'm doing: > > > > > > > > > > > > > > Thanx, > > Aaron - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Aligning Custom UI
What is the best way to line up controls in a custom UI? I usually make an initial guess on the location and size then make the adjustments from there. This approach is painful sometimes when you keep running the installer over and over just to see if everything is aligned correctly. Is there a better way? Thanx, Aaron - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error on uninstall? - FIXED
Julie, I assume your custom action does not run during repair, but only during install? I have a custom action that runs during install, but also runs during repair which causes an error. Can you show me your custom action with the conditional text that you used to achieve this? Thanx, Aaron On 5/11/07, Julie Campbell <[EMAIL PROTECTED]> wrote: > It seems I messed up the conditional text on a custom action that was only > to run during installation. It was running during uninstall too. As this > action creates a file, in a directory that was just removed ... bad things > happened. Anyway, all better now, thanks to everyone who spared this issue > some brainwaves. > > Julie Campbell > [EMAIL PROTECTED] > > -Original Message- > From: Bob Arnson [mailto:[EMAIL PROTECTED] > Sent: Friday, May 11, 2007 2:48 AM > To: Julie Campbell > Cc: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Error on uninstall? > > Julie Campbell wrote: > > Here's what seems to be the applicable part of the log. The user error is > > something like "one or more files needed for restoration cannot be found. > > Restoration is not possible." > > > > I haven't seen that error before but the log fragment below is part of > the rollback script; it's MSI cleaning up its private data. The error is > above it. > > > I don't know what "19C29D7B9D408814D8EF629B9E4E4D76" is, it isn't a GUID > I'm > > using. > > > > It's a "compressed GUID." See http://support.microsoft.com/kb/296067/ > for some examples of how they're built to convert to the "real GUID." > > -- > sig://boB > http://joyofsetup.com/ > > > > > _ > Scanned by IBM Email Security Management Services powered by MessageLabs. > For more information please visit http://www.ers.ibm.com > > _ > > > > _ > Scanned by IBM Email Security Management Services powered by MessageLabs. For > more information please visit http://www.ers.ibm.com > _ > > - > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Ignore Custom Action on Repair
I have a custom action that runs a tool during install. I do not want this tool to run during repair, in fact I only want this custom action to run only during the inital install. Currently it will attempt to run the custom action during repair which causes an error from the tool. Aaron On 5/11/07, Rob Mensching <[EMAIL PROTECTED]> wrote: > > > > > After InstallFinalize? That isn't part of the transaction. What are you > trying to accomplish? > > > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Aaron Feng > Sent: Friday, May 11, 2007 2:31 PM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Ignore Custom Action on Repair > > > > > I run a custom action during install which works fine, but I don't want to > run it during repair. I tried every possible way, but no luck. Here is an > example what I'm doing: > > > > > > > > > > > > > > Thanx, > > Aaron - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Ignore Custom Action on Repair
I run a custom action during install which works fine, but I don't want to run it during repair. I tried every possible way, but no luck. Here is an example what I'm doing: Thanx, Aaron - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditional Custom Action on Install
Thanx Rob, for anyone else that is interested the info can be found here: http://msdn2.microsoft.com/en-us/library/aa368012.aspx Here is the syntax from the doc: (&FeatureName=3) AND NOT(!FeatureName=3) The term "&FeatureName=3" means the action is to install the feature local. The term "NOT(!FeatureName=3)" means the feature is not installed local. Aaron On 5/10/07, Rob Mensching <[EMAIL PROTECTED]> wrote: Custom elements can be conditionalized by putting the condition as the text() of the element. The Condition Syntax topic in the MSI SDK has information about how to do what you want. *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Aaron Feng *Sent:* Thursday, May 10, 2007 8:17 PM *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] Conditional Custom Action on Install I would like to run a custom action only on install and when a specific feature is being installed. If someone could point me toward the right direction that would be great. Thanx, Aaron - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditional Custom Action on Install
I would like to run a custom action only on install and when a specific feature is being installed. If someone could point me toward the right direction that would be great. Thanx, Aaron - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] More on GenerateBootstrapper task
Yes, I found the SDK pretty useful to build a custom boostrapper. It has a nice UI to build the boostrapper's manifest. Aaron On 1/7/07, David Thielen <[EMAIL PROTECTED]> wrote: The root problem is I need info from Microsoft on what to look for to see if the 3 hotfixes need to be installed. There is no information as to what registry settings or ??? to look for. Also, the actual install files are not on Microsoft's website so they must always be copied to the directory the bootstrapper is in - so no optional download. thanks - dave ------ *From:* Aaron Feng [mailto:[EMAIL PROTECTED] *Sent:* Sat 1/6/2007 7:56 PM *To:* David Thielen; wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] More on GenerateBootstrapper task David, After fishing around I was able to build a custom bootstrap for the prerequsites I need which is not part of VS 2005. What kind of problem are you having, maybe I can help? Cheers, Aaron On 1/6/07, David Thielen <[EMAIL PROTECTED]> wrote: > > And having been fighting this for over 3 weeks now and having used a > support incident and Microsoft techs (I'm on number 4 now) have been working > this for 2 weeks - if there is not an example somewhere for the product you > want - give up. > > It is not documented and no one seems to know how to use it. I have > spent so much time talking to MS techs on this I think it would have been > less of my time just to write my own bootstrapper - and I still don't have a > solution. And this is for http://support.microsoft.com/kb/908002 which > is supposedly all set up to use as a pre-req. > > good luck - dave > > > -- > *From:* [EMAIL PROTECTED] on behalf of Aaron Feng > *Sent:* Fri 1/5/2007 9:29 PM > *To:* wix-users@lists.sourceforge.net > *Subject: *[WiX-users] More on GenerateBootstrapper task > > Someone might have already asked this question, but I don't think > anyone really answered it. For the BootstrapperFile element, where do I > find all prerequisites values I can use inside of the Include attribute? > I'm really interested in follow prerequisites: .NET 3.0, ReportViewer, > and ADAM. > > I would like to generate a bootstrapper using the GenerateBootstrapper > task, but I want to ship with all the prerequisites with my package. In > deployment environment, during an install the machine will not have Internet > access. If someone can show me an example how to accomplish this or point > me to the right direction would be great. > > Thanx, > > Aaron > > > - > 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.php&p=sourceforge&CID=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.php&p=sourceforge&CID=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.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] More on GenerateBootstrapper task
David, After fishing around I was able to build a custom bootstrap for the prerequsites I need which is not part of VS 2005. What kind of problem are you having, maybe I can help? Cheers, Aaron On 1/6/07, David Thielen <[EMAIL PROTECTED]> wrote: And having been fighting this for over 3 weeks now and having used a support incident and Microsoft techs (I'm on number 4 now) have been working this for 2 weeks - if there is not an example somewhere for the product you want - give up. It is not documented and no one seems to know how to use it. I have spent so much time talking to MS techs on this I think it would have been less of my time just to write my own bootstrapper - and I still don't have a solution. And this is for http://support.microsoft.com/kb/908002 which is supposedly all set up to use as a pre-req. good luck - dave -- *From:* [EMAIL PROTECTED] on behalf of Aaron Feng *Sent:* Fri 1/5/2007 9:29 PM *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] More on GenerateBootstrapper task Someone might have already asked this question, but I don't think anyone really answered it. For the BootstrapperFile element, where do I find all prerequisites values I can use inside of the Include attribute? I'm really interested in follow prerequisites: .NET 3.0, ReportViewer, and ADAM. I would like to generate a bootstrapper using the GenerateBootstrapper task, but I want to ship with all the prerequisites with my package. In deployment environment, during an install the machine will not have Internet access. If someone can show me an example how to accomplish this or point me to the right direction would be great. Thanx, Aaron - 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.php&p=sourceforge&CID=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.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] More on GenerateBootstrapper task
I think I just figured out the answer to my 2nd question which is set ComponentsLocation="Relative". Aaron On 1/5/07, Aaron Feng <[EMAIL PROTECTED]> wrote: Someone might have already asked this question, but I don't think anyone really answered it. For the BootstrapperFile element, where do I find all prerequisites values I can use inside of the Include attribute? I'm really interested in follow prerequisites: .NET 3.0, ReportViewer, and ADAM. I would like to generate a bootstrapper using the GenerateBootstrapper task, but I want to ship with all the prerequisites with my package. In deployment environment, during an install the machine will not have Internet access. If someone can show me an example how to accomplish this or point me to the right direction would be great. Thanx, Aaron - 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.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] More on GenerateBootstrapper task
Someone might have already asked this question, but I don't think anyone really answered it. For the BootstrapperFile element, where do I find all prerequisites values I can use inside of the Include attribute? I'm really interested in follow prerequisites: .NET 3.0, ReportViewer, and ADAM. I would like to generate a bootstrapper using the GenerateBootstrapper task, but I want to ship with all the prerequisites with my package. In deployment environment, during an install the machine will not have Internet access. If someone can show me an example how to accomplish this or point me to the right direction would be great. Thanx, Aaron - 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.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrading not doing anything
Rob, Yes I have noticed that. Just read your post on small or minor update, it was very helpful, however, I think I would have to do a major upgrade every time. Since my MSI automation violates every minor upgrade rule. Our Continues Integration server builds a MSI and runs all units tests every time when someone checks in. So our code is always packaged up at any time. However, components are changing all the time, which breaks the minor upgrade. Aaron On 1/4/07, Rob Mensching <[EMAIL PROTECTED]> wrote: Automated generation of MSI files is a very dangerous thing to do. You probably have to do a major upgrade, the slowest major upgrade that removes the previous product before installing the later product. This is why we (Bob and I) are constantly reminding people to be very careful when creating their Components. *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Aaron Feng *Sent:* Thursday, January 04, 2007 07:47 *To:* Bob Arnson; wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] Upgrading not doing anything Bob, I'm having a lot of problems trying to do minor upgrade. Partly the MSI is automated using a custom in house tool I wrote, so I have less control over it. I might just have to do a major upgrade every time. Is there any side effect by doing so? Thanx, Aaron On 1/4/07, *Bob Arnson* <[EMAIL PROTECTED]> wrote: Aaron Feng wrote: > Just for my understanding, what does Featuring marked as advertised mean? The MSI SDK talks about it starting at http://msdn2.microsoft.com/en-us/library/aa367548.aspx . -- 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.php&p=sourceforge&CID=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.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrading not doing anything
Bob, I'm having a lot of problems trying to do minor upgrade. Partly the MSI is automated using a custom in house tool I wrote, so I have less control over it. I might just have to do a major upgrade every time. Is there any side effect by doing so? Thanx, Aaron On 1/4/07, Bob Arnson <[EMAIL PROTECTED]> wrote: Aaron Feng wrote: > Just for my understanding, what does Featuring marked as advertised mean? The MSI SDK talks about it starting at http://msdn2.microsoft.com/en-us/library/aa367548.aspx. -- 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.php&p=sourceforge&CID=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.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrading not doing anything
Bob, Just for my understanding, what does Featuring marked as advertised mean? Thanx, Aaron On 1/4/07, Bob Arnson <[EMAIL PROTECTED]> wrote: Aaron Feng wrote: > MSI (s) (80:D4) [09:18:15:862]: Feature: Client; Installed: > Advertise; Request: Reinstall; Action: Reinstall This indicates what is probably the root of the problem. Features marked as advertised aren't actually installed on the machine so an upgrade doesn't do anything. So the question becomes: Why is the feature advertised? A common cause is a feature that had components removed -- that's not supported except via a major upgrade. -- 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.php&p=sourceforge&CID=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.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrade doesn't install one component
Thanx Stefan for the fast reply. Aaron On 1/4/07, Stefan Pavlik <[EMAIL PROTECTED]> wrote: Hi 1 is equal to 1 0 is equal to 0 3 is less than 20 and thus 1.0.3 is less than 1.0.20 regards stefan Aaron Feng wrote: > John, > > Can you plain to me why 1.0.3 is not newer than 1.0.20? > > Thanx, > > Aaron > > On 10/30/06, *John Lalande* < [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > I thought I had addressed the version issue, however, I have to > remind myself that versions are not decimal and 1.0.3 is not a newer > version than 1.0.20. But 1.0.21 *is* newer and that solves the > problem. Thanks Rob! > > > On 10/30/06, *Rob Mensching* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Somewhere in the log it should explain why the Component was > turned off. Usually, it's because the Condition is false. If > you don't' have a condition, often it is because the KeyPath was > not new enough (or it is unversioned and the existing file was > modified). > > > > *From:* [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > [mailto:[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>] *On Behalf Of > *John Lalande > *Sent:* Monday, October 30, 2006 18:51 > *To:* wix-users@lists.sourceforge.net > <mailto:wix-users@lists.sourceforge.net> > *Subject:* [WiX-users] Upgrade doesn't install one component > > > > I have successfully convinced my employer to migrate our > installers from InstallShield to WiX. > > However, one of our products, when upgrading from the > IS-authored previous version, neglects to install one of the > components (the component does get installed on a fresh > install). When the application is launched after the upgrade, > it appears to do a Repair and then the application starts. When > I look into installation directory, I can see that the > component's KeyPath (which is a file) has now been installed. > > I have logged the upgrade and did a search for the component > name in the log and found the log entry: > MSI (s) (0C:CC) [20:24:58:633]: Component: ClientAPIProxy_dll; > Installed: Absent; Request: Local; Action: Null > > What I notice unusual is that all the other component log > entries have the value "Action:" field set to "Local". > > Does this log entry indicate anything that could point me to the > problem? > > > > - > 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=lnk&kid=120709&bid=263057&dat=121642 > < http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642> > > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > <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.php&p=sourceforge&CID=DEVDEV > > > > > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- 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.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrade doesn't install one component
John, Can you plain to me why 1.0.3 is not newer than 1.0.20? Thanx, Aaron On 10/30/06, John Lalande <[EMAIL PROTECTED]> wrote: I thought I had addressed the version issue, however, I have to remind myself that versions are not decimal and 1.0.3 is not a newer version than 1.0.20. But 1.0.21 *is* newer and that solves the problem. Thanks Rob! On 10/30/06, Rob Mensching <[EMAIL PROTECTED]> wrote: > > Somewhere in the log it should explain why the Component was turned > off. Usually, it's because the Condition is false. If you don't' have a > condition, often it is because the KeyPath was not new enough (or it is > unversioned and the existing file was modified). > > > > *From:* [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] *On Behalf Of *John Lalande > *Sent:* Monday, October 30, 2006 18:51 > *To:* wix-users@lists.sourceforge.net > *Subject:* [WiX-users] Upgrade doesn't install one component > > > > I have successfully convinced my employer to migrate our installers from > InstallShield to WiX. > > However, one of our products, when upgrading from the IS-authored > previous version, neglects to install one of the components (the component > does get installed on a fresh install). When the application is launched > after the upgrade, it appears to do a Repair and then the application > starts. When I look into installation directory, I can see that the > component's KeyPath (which is a file) has now been installed. > > I have logged the upgrade and did a search for the component name in the > log and found the log entry: > MSI (s) (0C:CC) [20:24:58:633]: Component: ClientAPIProxy_dll; > Installed: Absent; Request: Local; Action: Null > > What I notice unusual is that all the other component log entries have > the value "Action:" field set to "Local". > > Does this log entry indicate anything that could point me to the > problem? > - 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=lnk&kid=120709&bid=263057&dat=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.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrading not doing anything
Null; Action: Null MSI (s) (80:D4) [09:18:15:862]: Component: component39; Installed: Absent; Request: Null; Action: Null MSI (s) (80:D4) [09:18:15:862]: Component: component40; Installed: Absent; Request: Null; Action: Null MSI (s) (80:D4) [09:18:15:862]: Component: component41; Installed: Absent; Request: Null; Action: Null MSI (s) (80:D4) [09:18:15:862]: Component: component42; Installed: Absent; Request: Null; Action: Null MSI (s) (80:D4) [09:18:15:862]: Component: component43; Installed: Absent; Request: Null; Action: Null MSI (s) (80:D4) [09:18:15:862]: Component: component44; Installed: Absent; Request: Null; Action: Null MSI (s) (80:D4) [09:18:15:862]: Component: component45; Installed: Absent; Request: Null; Action: Null MSI (s) (80:D4) [09:18:15:862]: Component: component46; Installed: Absent; Request: Null; Action: Null MSI (s) (80:D4) [09:18:15:862]: Component: component47; Installed: Absent; Request: Null; Action: Null MSI (s) (80:D4) [09:18:15:862]: Component: component48; Installed: Absent; Request: Null; Action: Null MSI (s) (80:D4) [09:18:15:862]: Component: component49; Installed: Absent; Request: Null; Action: Null MSI (s) (80:D4) [09:18:15:862]: Component: component50; Installed: Absent; Request: Null; Action: Null MSI (s) (80:D4) [09:18:15:862]: Component: __ClientConfig65; Installed: Null; Request: Null; Action: Null MSI (s) (80:D4) [09:18:15:862]: Note: 1: 2205 2: 3: Registry MSI (s) (80:D4) [09:18:15:862]: Note: 1: 2205 2: 3: BindImage MSI (s) (80:D4) [09:18:15:862]: Note: 1: 2205 2: 3: ProgId MSI (s) (80:D4) [09:18:15:862]: Note: 1: 2205 2: 3: PublishComponent MSI (s) (80:D4) [09:18:15:862]: Note: 1: 2205 2: 3: SelfReg MSI (s) (80:D4) [09:18:15:862]: Note: 1: 2205 2: 3: Extension MSI (s) (80:D4) [09:18:15:862]: Note: 1: 2205 2: 3: Font MSI (s) (80:D4) [09:18:15:862]: Note: 1: 2205 2: 3: Class MSI (s) (80:D4) [09:18:15:878]: PROPERTY CHANGE: Modifying CostingComplete property. Its current value is '0'. Its new value: '1'. MSI (s) (80:D4) [09:18:15:878]: Note: 1: 2205 2: 3: Registry MSI (s) (80:D4) [09:18:15:878]: Note: 1: 2205 2: 3: BindImage MSI (s) (80:D4) [09:18:15:878]: Note: 1: 2205 2: 3: ProgId MSI (s) (80:D4) [09:18:15:878]: Note: 1: 2205 2: 3: PublishComponent MSI (s) (80:D4) [09:18:15:878]: Note: 1: 2205 2: 3: SelfReg MSI (s) (80:D4) [09:18:15:878]: Note: 1: 2205 2: 3: Extension MSI (s) (80:D4) [09:18:15:878]: Note: 1: 2205 2: 3: Font MSI (s) (80:D4) [09:18:15:878]: Note: 1: 2205 2: 3: Class MSI (s) (80:D4) [09:18:15:878]: Note: 1: 2727 2: MSI (s) (80:D4) [09:18:15:878]: Note: 1: 2727 2: Action ended 9:18:15: InstallValidate. Return value 1. - Start of InstallFiles --- MSI (s) (80:D4) [09:18:18:237]: Doing action: InstallFiles MSI (s) (80:D4) [09:18:18:237]: Note: 1: 2205 2: 3: ActionText Action 9:18:18: InstallFiles. Copying new files Action start 9:18:18: InstallFiles. MSI (s) (80:D4) [09:18:18:237]: Note: 1: 2205 2: 3: Patch MSI (s) (80:D4) [09:18:18:237]: Note: 1: 2228 2: 3: Patch 4: SELECT `Patch`.`File_`, `Patch`.`Header`, `Patch`.`Attributes`, `Patch`.`Sequence`, `Patch`.`StreamRef_` FROM `Patch` WHERE `Patch`.`File_` = ? AND `Patch`.`#_MsiActive`=? ORDER BY `Patch`.`Sequence` MSI (s) (80:D4) [09:18:18:237]: Note: 1: 2205 2: 3: MsiSFCBypass MSI (s) (80:D4) [09:18:18:237]: Note: 1: 2228 2: 3: MsiSFCBypass 4: SELECT `File_` FROM `MsiSFCBypass` WHERE `File_` = ? MSI (s) (80:D4) [09:18:18:237]: Note: 1: 2205 2: 3: MsiPatchHeaders MSI (s) (80:D4) [09:18:18:237]: Note: 1: 2228 2: 3: MsiPatchHeaders 4: SELECT `Header` FROM `MsiPatchHeaders` WHERE `StreamRef` = ? MSI (s) (80:D4) [09:18:18:237]: Note: 1: 2205 2: 3: ActionText MSI (s) (80:D4) [09:18:18:237]: Note: 1: 2205 2: 3: ActionText MSI (s) (80:D4) [09:18:18:237]: Note: 1: 2205 2: 3: ActionText Action 9:18:18: GenerateScript. Generating script operations for action: GenerateScript: Copying new files Action ended 9:18:18: InstallFiles. Return value 1. Thanx, Aaron On 1/4/07, Bob Arnson <[EMAIL PROTECTED]> wrote: Aaron Feng wrote: > I'm not sure what information I need to provide here, since I'm not > getting any error messages. General info: The command lines you're using to install and upgrade. Excerpts from verbose logs, especially around InstallValidate (as Michael points out). -- 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -
Re: [WiX-users] Upgrading not doing anything
Phil, I did everything you said. I don't know what going on either. I found out the hard way that I need to change the version of the file in order for the minor upgrade to work. I even try to do vamus instead of vomus, but still no luck. I even wrote a program to retrieve the file version, just to make sure the version of the files are different. The weird part is, nothing happens, no errors during an upgrade. Each MSI work indepenently of each other, but I can't upgrade from one version to the next. Aaron On 1/3/07, Wilson, Phil <[EMAIL PROTECTED]> wrote: I can't tell what's actually going on with those versions either. Changing file versions is a requirement for a minor upgrade to be useful, so I wonder what Aaron did. You're supposed to update versions of files that have changed, build an MSI file with a new PackageCode but the same ProductCode (and an incremented ProductVersion usually) and then install with: msiexec /i REINSTALL=ALL REINSTALLMODE=vomus where that 'o' is "replace older versions with newer versions of files". So if you don't change file versions there won't be any code files updated. Phil Wilson -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Michael Osmond *Sent:* Wednesday, January 03, 2007 4:57 PM *To:* Aaron Feng; wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] Upgrading not doing anything Aaron, Have you tried logging the upgrade process, the command line option I use is /lv* (which is just about everything). Then look at two things: 1. The InstallValidate action - this should show what the installer is planning to do to each component. 2. Then look for the actual InstallFiles action. It should show what the installer is doing to each file - it may say why it won't change a file. The only other thing is do all of your components have a GUID? I've seen something like this when I forgot them. Michael -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Aaron Feng *Sent:* Thursday, 4 January 2007 8:26 AM *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] Upgrading not doing anything I'm having trouble doing a minor upgrade for an existing MSI. The new upgrading MSI run without errors, however, it does nothing. I checked the log file during an upgrade, nothing seems particularly interesting. If I run the new MSI by itself (installing in this case), it works just fine. I tried to play with the REINSTALLMODE, and changing the version number on my assemblies. Nothing seems to work. I also noticed after an upgrade (didn't actually work), uninstalling the application doesn't actually do anything. It uninstalls without any errors, but no files are actually removed from the disk. I'm not sure what information I need to provide here, since I'm not getting any error messages. I basically followed the instructions in the WiX tutorial lesson 4 ( http://www.tramontana.co.hu/wix/lesson4.php). Thanx, Aaron - 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.php&p=sourceforge&CID=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.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrading not doing anything
Michael, I checked the log file, and I didn't see anything interesting, however, I didn't check the InstallValidate and InstallFiles action closely. I didn't use the /lv* switch on the log file, I just used the default. I can try it again when I get back to work. Yes, all my components have GUID. Aaron On 1/3/07, Michael Osmond <[EMAIL PROTECTED]> wrote: Aaron, Have you tried logging the upgrade process, the command line option I use is /lv* (which is just about everything). Then look at two things: 1. The InstallValidate action - this should show what the installer is planning to do to each component. 2. Then look for the actual InstallFiles action. It should show what the installer is doing to each file - it may say why it won't change a file. The only other thing is do all of your components have a GUID? I've seen something like this when I forgot them. Michael -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Aaron Feng *Sent:* Thursday, 4 January 2007 8:26 AM *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] Upgrading not doing anything I'm having trouble doing a minor upgrade for an existing MSI. The new upgrading MSI run without errors, however, it does nothing. I checked the log file during an upgrade, nothing seems particularly interesting. If I run the new MSI by itself (installing in this case), it works just fine. I tried to play with the REINSTALLMODE, and changing the version number on my assemblies. Nothing seems to work. I also noticed after an upgrade (didn't actually work), uninstalling the application doesn't actually do anything. It uninstalls without any errors, but no files are actually removed from the disk. I'm not sure what information I need to provide here, since I'm not getting any error messages. I basically followed the instructions in the WiX tutorial lesson 4 ( http://www.tramontana.co.hu/wix/lesson4.php). Thanx, Aaron - 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.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Upgrading not doing anything
I'm having trouble doing a minor upgrade for an existing MSI. The new upgrading MSI run without errors, however, it does nothing. I checked the log file during an upgrade, nothing seems particularly interesting. If I run the new MSI by itself (installing in this case), it works just fine. I tried to play with the REINSTALLMODE, and changing the version number on my assemblies. Nothing seems to work. I also noticed after an upgrade (didn't actually work), uninstalling the application doesn't actually do anything. It uninstalls without any errors, but no files are actually removed from the disk. I'm not sure what information I need to provide here, since I'm not getting any error messages. I basically followed the instructions in the WiX tutorial lesson 4 (http://www.tramontana.co.hu/wix/lesson4.php). Thanx, Aaron - 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.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Retrieve hostname during an installation.
Thanks, It worked great.AaronOn 7/17/06, Derek Cicerone <[EMAIL PROTECTED]> wrote: That's not a good idea – replying upon certain system registry values is an invitation for application compatibility issues for future versions of the OS. Instead, just use the built-in ComputerName property: ComputerName Property The ComputerName property is the computer name of the current system. The installer sets this property by a system call to GetComputerName. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ] On Behalf Of Darren Kulp Sent: Monday, July 17, 2006 12:46 PM To: Aaron Feng; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Retrieve hostname during an installation. Perhaps you could do a RegistrySearch on HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerName ? Wix-users, please correct me if there is a built-in or better way to do this. --kulp From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ] On Behalf Of Aaron Feng Sent: Monday 17 July 2006 14:34 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Retrieve hostname during an installation. Is there an easy way to retrieve the hostname of the computer during an install without writing an custom action? Thanks, Aaron - 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.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Retrieve hostname during an installation.
Is there an easy way to retrieve the hostname of the computer during an install without writing an custom action?Thanks,Aaron - 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.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] UIRef WiXUI_Common Problem
I'm following lesson 2 (User Interface) on the WiX tutorial, and I noticed the tutorial seemed to be out of date because some of the examples did not seems to work correctly. I poked around and finally got almost everything to work except for the Bitmaps are not showing up in my msi. The reason it is not showing up is because I had to comment out in WixUI_Mondo.wxs. If I don't comment it out, I get an error when I run light. The error is listed below: error CNDL0132 : Schema validation failed with the following error: The element 'Fragment' has invalid content.My WixUI_Monodo.wxs looks like this: http://schemas.microsoft.com/wix/2003/01/wi"> Here is what I did to create the WixUI_Mondo.wixlib with the custom UI.candle.exe wixui\mondo\WixUI_Mondo.wxs wixui\*.wxslit.exe -out WixUI_Mondo.wixlib *.wixobjI'm using the latest stable version of WiX. This is really weird because I think is in the right place. Like I said before, I can get the custom UI to work if I removed the , but I don't get the Bitmaps. Thanx in advance,Aaronhttp://aaronfeng.blogspot.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] UIRef WiXUI_Common Problem
For some reason, the problem went away when I copied everything into one directory.AaronOn 6/3/06, Aaron Feng < [EMAIL PROTECTED]> wrote:I'm following lesson 2 (User Interface) on the WiX tutorial, and I noticed the tutorial seemed to be out of date because some of the examples did not seems to work correctly. I poked around and finally got almost everything to work except for the Bitmaps are not showing up in my msi. The reason it is not showing up is because I had to comment out in WixUI_Mondo.wxs. If I don't comment it out, I get an error when I run light. The error is listed below: error CNDL0132 : Schema validation failed with the following error: The element 'Fragment' has invalid content.My WixUI_Monodo.wxs looks like this: http://schemas.microsoft.com/wix/2003/01/wi"> Here is what I did to create the WixUI_Mondo.wixlib with the custom UI.candle.exe wixui\mondo\WixUI_Mondo.wxs wixui\*.wxslit.exe -out WixUI_Mondo.wixlib *.wixobjI'm using the latest stable version of WiX. This is really weird because I think is in the right place. Like I said before, I can get the custom UI to work if I removed the , but I don't get the Bitmaps. Thanx in advance,Aaronhttp://aaronfeng.blogspot.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
