Re: [WiX-users] RegistrySearch element
You could set the property's initial value to something like MY_DUMMY_VALUE and then check to see if the property is still equal to it after the registry searching. Rob On 26/09/2010 18:39, Sean Farrow wrote: Hi: I need to use the RegistrySearch element in a property. I need to look a key who's default key has no default value (regedit show value not set). What will the property be set to? I'll need to use this property in a launch condition. Should I do this or could I use a custom action to set the property, and do the registry look up myself. Any help appreciated. Sean. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Two CheckBoxes, Same Property
On 27-Sep-10 16:43, gapearce wrote: I have a reason to have a checkbox appear on a different place in the same dialog, based on a condition. I was trying to use propertyRef to allow both checkbox controls to use the same property, but I can't get that to work. That's what CheckBoxPropertyRef is for; did you try that? If so, how didn't it work? -- sig://boB http://joyofsetup.com/ -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Customize dialogs differently for each locale
On 28-Sep-10 01:26, akshi_gupta wrote: I can use .wxl file to localize the text for each dialog. But is it possible to customize the width or height of a dialog (or one of its control) differently for each locale? Yes, the X, Y, Width, and Height attributes can be set to localization strings. -- sig://boB http://joyofsetup.com/ -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] resource strings issue with wix 2.0
On 27-Sep-10 08:17, Naufal Basheer (Aditi) wrote: We have an installer for which we are using both built-in Wix and custom dialogs. Is there a way to use the existing WixUIExtension.dll resource file for build-in resource strings and use a separate resource file for our custom strings? We are running on WIX 2.0 and do not want to create a file which contains strings that are already a part of WixUIExtension.dll (WixUI_en-us.wxl). WiX v2.0 doesn't have WixUIExtension.dll. If you're moving to WiX v3.x, you don't have to do anything special to reference strings that ship in WixUIExtension.dll; WiX will use the first string it finds, unless overridden using the Overridable attribute on the String element. -- sig://boB http://joyofsetup.com/ -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Square brackets in variable value
On 27-Sep-10 12:55, John Fry wrote: The value that gets inserted into the MSI when we get the error is: [%CommonProgramFiles]\path\to\folder;[%CommonProgramFiles(x86)]\path\to\folder;[~] Which is correct -- it looks like MSI doesn't like the parentheses. And you're saying that an equivalent statement would be: [CommonFiles64Folder]\path\to\folder;[CommonFilesFolder]\path\to\folder;[~] Yes. -- sig://boB http://joyofsetup.com/ -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] unsubscrbe
-- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] how to stop msiserver after installation;
After my installer finishes, msiserver keeps running for long time. How can I stop it? Our top level installer package (not MSI based) waits for all the child processes launched by a specific installer to end/stop before it can proceed with the installation of other packages. How can I stop msiserver? Any help will be highly appreciated. Thanks. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Reading Assembly Information
Have you considered binder variables: http://wix.sourceforge.net/manual-wix3/light.htm (if your assembly is not in the GAC you will need set File/@AssemblyApplication). Neil -Original Message- From: pcristini [mailto:pcrist...@paretoplatform.com] Sent: 27 September 2010 21:24 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Reading Assembly Information I'm looking to read information about an assembly (version, culture, publickey, etc) from an assembly, and store those values in properties which will then be added to the application's config file. I'm going to be producing elements like this: Plugin name=UserManager assembly=Plugin.Users, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9d04a1dca2c654ed class=Plugin.Users.UserManagerPlugin enabled=true / Is there any solutions out there for this? I've searched around a bit but can't find anything even close to what I'm looking to do. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Reading-As sembly-Information-tp5576754p5576754.html Sent from the wix-users mailing list archive at Nabble.com. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] how to stop msiserver after installation;
After my installer finishes, msiserver keeps running for long time. How can I stop it? Our top level installer package (not MSI based) waits for all the child processes launched by a specific installer to end/stop before it can proceed with the installation of other packages. How can I stop msiserver? Any help will be highly appreciated. Thanks. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] how to stop msiserver after installation;
It sounds like you have a design that expects the Windows Installer service (or some number of processes called msiexec.exe?) to stop when a bunch of your installs have finished. The Windows Installer service isn't a child process! Like any other Windows service you stop it with the service APIs, but really, your design is just very very wrong. If those other installs are completely out of your control (and you can't install them yourself so you *know* when they complete) you'd be better off polling for the ProductCode of last one you launched to see when it is finally installed. Phil Wilson -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 12:05 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] how to stop msiserver after installation; After my installer finishes, msiserver keeps running for long time. How can I stop it? Our top level installer package (not MSI based) waits for all the child processes launched by a specific installer to end/stop before it can proceed with the installation of other packages. How can I stop msiserver? Any help will be highly appreciated. Thanks. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77nav_id=80prev_id=77. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Directory in Maintenance mode is not directory installed to
I'm using the WIXUI_INSTALLDIR functionality in my installer. When I install, it lets me change the install directory from the default path that I set to INSTALLLOCATION and it installs to that new directory perfectly fine. However, when I enter maintenance mode (by hitting Change in Add/Remove Programs or re-running the installer), and I try to add a feature that I hadn't yet installed, it will always install it to the default path, which is not where I installed the product to. Is there anything special I need to do to make that happen? Here's the code snippet of my installer: ?xml version='1.0'? !-- Copyright (c) Chase Paymentech Solutions, LLC. All rights reserved. -- Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:iis=http://schemas.microsoft.com/wix/IIsExtension; ?include Common\Config.wxi? ?include Common\PackageData.wxi? Product Id='*' Name='Chase Paymentech Spectrum SDK $(var.ProductVersion) for .Net $(var.NetVersion)' Language='1033' Version='$(var.ProductVersion)' Manufacturer='Chase Paymentech' UpgradeCode='$(var.UpgradeCode)' Package Description='Spectrum SDK for .Net $(var.NetVersion)' Comments='Installation of the Spectrum SDK for .Net $(var.NetVersion)' InstallerVersion='300' Compressed='yes' Platform='x86' / !-- To use the canned install sequence, but with a custom dialog -- Property Id=WIXUI_INSTALLDIR Value=INSTALLLOCATION/ UIRef Id=MyWixUI_InstallDir / Property Id=DOTNETVER Value=Net$(var.NetVersionShort) / Property Id=FRAMEWORKROOT RegistrySearch Id=FrameworkRootDir Root=HKLM Key=SOFTWARE\Microsoft\.NETFramework Type=directory Name=InstallRoot / /Property PropertyRef Id=NETFRAMEWORK$(var.NetVersionShort)/ Condition Message=The .NET Framework $(var.NetVersion) must be installed Installed OR NETFRAMEWORK$(var.NetVersionShort) /Condition Media Id='1' Cabinet='product.cab' EmbedCab='yes' / Directory Id='TARGETDIR' Name='SourceDir' Directory Id='ProgramFilesFolder' Name='PFiles' Directory Id='MyCompany' Name='My Company' Directory Id='INSTALLLOCATION' Name='MyProduct' ... /Directory /Directory /Directory /Directory Feature Id='Complete' Title='My Product' Description='The complete package.' TypicalDefault='install' Display='expand' Level='1' ConfigurableDirectory='INSTALLLOCATION' Feature Id='Core' Absent='disallow' Title='Core Software' Description='Core Runtime Components.' Level='1' ... /Feature Feature Id='Samples' Title='Sample Applications' Description='Sample Applications.' ConfigurableDirectory=INSTALLLOCATION Level='3' ... /Feature /Feature /Product /Wix Here is my InstallDir file Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment UI Id=MyWixUI_InstallDir TextStyle Id=WixUI_Font_Normal FaceName=Tahoma Size=8 / TextStyle Id=WixUI_Font_Bigger FaceName=Tahoma Size=12 / TextStyle Id=WixUI_Font_Title FaceName=Tahoma Size=9 Bold=yes / Property Id=DefaultUIFont Value=WixUI_Font_Normal / Property Id=WixUI_Mode Value=InstallDir / DialogRef Id=BrowseDlg / DialogRef Id=DiskCostDlg / DialogRef Id=ErrorDlg / DialogRef Id=FatalError / DialogRef Id=FilesInUse / DialogRef Id=MsiRMFilesInUse / DialogRef Id=PrepareDlg / DialogRef Id=ProgressDlg / DialogRef Id=ResumeDlg / DialogRef Id=UserExit / Publish Dialog=BrowseDlg Control=OK Event=DoAction Value=WixUIValidatePath Order=31/Publish Publish Dialog=BrowseDlg Control=OK Event=SpawnDialog Value=InvalidDirDlg Order=4![CDATA[WIXUI_INSTALLDIR_VALID1]]/Publish Publish Dialog=ExitDialog Control=Finish Event=EndDialog Value=Return Order=9991/Publish Publish Dialog=WelcomeDlg Control=Next Event=NewDialog Value=InstallDirDlg Order=11/Publish Publish Dialog=LicenseAgreementDlg Control=Back Event=NewDialog Value=WelcomeDlg1/Publish Publish Dialog=LicenseAgreementDlg Control=Next Event=NewDialog Value=InstallDirDlgLicenseAccepted = 1/Publish Publish Dialog=InstallDirDlg Control=Back Event=NewDialog Value=WelcomeDlg1/Publish Publish Dialog=InstallDirDlg Control=Next Order=1 Event=DoAction Value=FileExists1/Publish Publish Dialog=InstallDirDlg Control=Next Order=2 Event=SetTargetPath Value=[WIXUI_INSTALLDIR]1/Publish Publish Dialog=InstallDirDlg Control=Next Order=3 Event=DoAction Value=WixUIValidatePathNOT WIXUI_DONTVALIDATEPATH/Publish Publish Dialog=InstallDirDlg Control=Next Order=4 Event=SpawnDialog Value=InvalidDirDlg![CDATA[NOT WIXUI_DONTVALIDATEPATH AND WIXUI_INSTALLDIR_VALID1]]/Publish Publish Dialog=InstallDirDlg Control=Next Order=5 Event=NewDialog Value=MySetupTypeDlgFILE_EXISTS=0 AND (WIXUI_DONTVALIDATEPATH OR WIXUI_INSTALLDIR_VALID=1)/Publish Publish Dialog=InstallDirDlg
Re: [WiX-users] Two CheckBoxes, Same Property
Well... I was having trouble with PropertyRef on a checkbox control because you can't do that! I meant to use CheckBoxPropertyRef (which I just learned about in another post), and that works exactly as advertised. Ugh... But thanks Bob! And thanks to Christopher, too. Your suggestion gave me a whole new set of things to think about and exploit :) Thanks again everyone. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Two-CheckBoxes-Same-Property-tp5576848p5580975.html Sent from the wix-users mailing list archive at Nabble.com. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Reading Assembly Information
This will work perfectly! Thanks Neil. Chris your points are completely valid; unfortunately at this point in the application's life cycle it hasn't matured enough to have full-blown plugin management/detection and relies solely on entries in the app.config. This is planned to be fixed in the future. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Reading-Assembly-Information-tp5576754p5581121.html Sent from the wix-users mailing list archive at Nabble.com. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Reading Assembly Information
I also liked the CodePlex link that was provided earlier in this thread. I'm going to have to play with that some time soon. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: pcristini pcrist...@paretoplatform.com To: wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 3:41:02 PM Subject: Re: [WiX-users] Reading Assembly Information This will work perfectly! Thanks Neil. Chris your points are completely valid; unfortunately at this point in the application's life cycle it hasn't matured enough to have full-blown plugin management/detection and relies solely on entries in the app.config. This is planned to be fixed in the future. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Reading-Assembly-Information-tp5576754p5581121.html Sent from the wix-users mailing list archive at Nabble.com. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Microsoft retires Visual Studio Installer and announces InstallShield a choice solution
Just found out that Microsoft is retiring current installer and this quote: InstallShield 2011 should be an installation development environment of choice for Visual Studio users, ensuring that Visual Studio applications of any kind can be professionally installed and work with the latest Microsoft technologies and platforms. Jason Zander Corporate Vice President of Visual Studio - Microsoft I thought WiX would be a choice solution :( TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] how to stop msiserver after installation;
Thanks for responding. The top installer is not ours it is of our customer who takes software from us and several other vendors. Their top level installer expects our installer to stop all the processes that started for our installation and that includes msiserver.exe also. If I use service APIs what will be the id for the msiserver service? Can you please point me to a sample code. Thanks. - Original Message From: Wilson, Phil phil.wil...@invensys.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 12:33:08 PM Subject: Re: [WiX-users] how to stop msiserver after installation; It sounds like you have a design that expects the Windows Installer service (or some number of processes called msiexec.exe?) to stop when a bunch of your installs have finished. The Windows Installer service isn't a child process! Like any other Windows service you stop it with the service APIs, but really, your design is just very very wrong. If those other installs are completely out of your control (and you can't install them yourself so you *know* when they complete) you'd be better off polling for the ProductCode of last one you launched to see when it is finally installed. Phil Wilson -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 12:05 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] how to stop msiserver after installation; After my installer finishes, msiserver keeps running for long time. How can I stop it? Our top level installer package (not MSI based) waits for all the child processes launched by a specific installer to end/stop before it can proceed with the installation of other packages. How can I stop msiserver? Any help will be highly appreciated. Thanks. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77nav_id=80prev_id=77. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] how to stop msiserver after installation;
Your customer either has incorrect requirements or isn't communicating them clearly. First I want to point out that there is no such msiserver.exe. The client and server side processes both use msiexec.exe. There is no best practice way to terminate the msiservice from within a running msisession short of calling for a mandatory reboot. Their process is the process that called msiexec /i foo.msi and spun up your install and the service. It should be their job to shut it down if they are so inclined or they should realize that you didn't start it so it's not your problem to close it. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Bisht, Pradeep pradeep_bi...@yahoo.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 4:41:37 PM Subject: Re: [WiX-users] how to stop msiserver after installation; Thanks for responding. The top installer is not ours it is of our customer who takes software from us and several other vendors. Their top level installer expects our installer to stop all the processes that started for our installation and that includes msiserver.exe also. If I use service APIs what will be the id for the msiserver service? Can you please point me to a sample code. Thanks. - Original Message From: Wilson, Phil phil.wil...@invensys.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 12:33:08 PM Subject: Re: [WiX-users] how to stop msiserver after installation; It sounds like you have a design that expects the Windows Installer service (or some number of processes called msiexec.exe?) to stop when a bunch of your installs have finished. The Windows Installer service isn't a child process! Like any other Windows service you stop it with the service APIs, but really, your design is just very very wrong. If those other installs are completely out of your control (and you can't install them yourself so you *know* when they complete) you'd be better off polling for the ProductCode of last one you launched to see when it is finally installed. Phil Wilson -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 12:05 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] how to stop msiserver after installation; After my installer finishes, msiserver keeps running for long time. How can I stop it? Our top level installer package (not MSI based) waits for all the child processes launched by a specific installer to end/stop before it can proceed with the installation of other packages. How can I stop msiserver? Any help will be highly appreciated. Thanks. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77nav_id=80prev_id=77. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] how to stop msiserver after installation;
when our installer starts I see that: under processes msiexec.exe starts running and under services msiserver start running. Once our installer completes, msiexec is no longer visible in task manager while msiserver keeps running untill after 10 minutes and then its status changes to stopped. Customer's requirement is to stop msiserver immediately after our installation completes. All of our custom actions are synchronous return=check. - Original Message From: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 2:53:43 PM Subject: Re: [WiX-users] how to stop msiserver after installation; I don't think you should be trying to stop msiserver.exe. 1.) I don't know what msiserver.exe is. I would expect to see msiexec.exe but you certainly don't want to stop these process as one of them will be yourself. 2.) The Windows Installer architecture uses a client process and a server process. You really want the OS to determine when the server process is ready to die if at all. The client process should not be killed as that will kill yourself as I mentioned above. Seems to me like the requirement interpretation should be make sure you wait for any exe custom actions your spin up during your installation. WiX will let you wait for their completion already. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 2:42 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; Thanks for responding. The top installer is not ours it is of our customer who takes software from us and several other vendors. Their top level installer expects our installer to stop all the processes that started for our installation and that includes msiserver.exe also. If I use service APIs what will be the id for the msiserver service? Can you please point me to a sample code. Thanks. - Original Message From: Wilson, Phil phil.wil...@invensys.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 12:33:08 PM Subject: Re: [WiX-users] how to stop msiserver after installation; It sounds like you have a design that expects the Windows Installer service (or some number of processes called msiexec.exe?) to stop when a bunch of your installs have finished. The Windows Installer service isn't a child process! Like any other Windows service you stop it with the service APIs, but really, your design is just very very wrong. If those other installs are completely out of your control (and you can't install them yourself so you *know* when they complete) you'd be better off polling for the ProductCode of last one you launched to see when it is finally installed. Phil Wilson -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 12:05 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] how to stop msiserver after installation; After my installer finishes, msiserver keeps running for long time. How can I stop it? Our top level installer package (not MSI based) waits for all the child processes launched by a specific installer to end/stop before it can proceed with the installation of other packages. How can I stop msiserver? Any help will be highly appreciated. Thanks. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities
Re: [WiX-users] how to stop msiserver after installation;
Then the customer needs to speak to Microsoft and get them to change how their Windows package installation system works. The MSI service is part of the Operating System. It has nothing directly to do with your installation, in the sense that your installation doesn't control anything about it. It is up to the Operating System when it starts and stops this service. How do you know it isn't doing other things which have nothing to do with your package installation? -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 11:06 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; when our installer starts I see that: under processes msiexec.exe starts running and under services msiserver start running. Once our installer completes, msiexec is no longer visible in task manager while msiserver keeps running untill after 10 minutes and then its status changes to stopped. Customer's requirement is to stop msiserver immediately after our installation completes. All of our custom actions are synchronous return=check. - Original Message From: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 2:53:43 PM Subject: Re: [WiX-users] how to stop msiserver after installation; I don't think you should be trying to stop msiserver.exe. 1.) I don't know what msiserver.exe is. I would expect to see msiexec.exe but you certainly don't want to stop these process as one of them will be yourself. 2.) The Windows Installer architecture uses a client process and a server process. You really want the OS to determine when the server process is ready to die if at all. The client process should not be killed as that will kill yourself as I mentioned above. Seems to me like the requirement interpretation should be make sure you wait for any exe custom actions your spin up during your installation. WiX will let you wait for their completion already. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 2:42 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; Thanks for responding. The top installer is not ours it is of our customer who takes software from us and several other vendors. Their top level installer expects our installer to stop all the processes that started for our installation and that includes msiserver.exe also. If I use service APIs what will be the id for the msiserver service? Can you please point me to a sample code. Thanks. - Original Message From: Wilson, Phil phil.wil...@invensys.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 12:33:08 PM Subject: Re: [WiX-users] how to stop msiserver after installation; It sounds like you have a design that expects the Windows Installer service (or some number of processes called msiexec.exe?) to stop when a bunch of your installs have finished. The Windows Installer service isn't a child process! Like any other Windows service you stop it with the service APIs, but really, your design is just very very wrong. If those other installs are completely out of your control (and you can't install them yourself so you *know* when they complete) you'd be better off polling for the ProductCode of last one you launched to see when it is finally installed. Phil Wilson -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 12:05 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] how to stop msiserver after installation; After my installer finishes, msiserver keeps running for long time. How can I stop it? Our top level installer package (not MSI based) waits for all the child processes launched by a specific installer to end/stop before it can proceed with the installation of other packages. How can I stop msiserver? Any help will be highly appreciated. Thanks. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___
Re: [WiX-users] how to stop msiserver after installation;
Tell your customer that this is by design and if they have a problem with it they should call Microsoft. BTW, it looks like this was just covered on WiX-Dev. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/how-to-stop-msiserver-net-stop-msiserver-td5516817.html Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Bisht, Pradeep pradeep_bi...@yahoo.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 5:06:07 PM Subject: Re: [WiX-users] how to stop msiserver after installation; when our installer starts I see that: under processes msiexec.exe starts running and under services msiserver start running. Once our installer completes, msiexec is no longer visible in task manager while msiserver keeps running untill after 10 minutes and then its status changes to stopped. Customer's requirement is to stop msiserver immediately after our installation completes. All of our custom actions are synchronous return=check. - Original Message From: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 2:53:43 PM Subject: Re: [WiX-users] how to stop msiserver after installation; I don't think you should be trying to stop msiserver.exe. 1.) I don't know what msiserver.exe is. I would expect to see msiexec.exe but you certainly don't want to stop these process as one of them will be yourself. 2.) The Windows Installer architecture uses a client process and a server process. You really want the OS to determine when the server process is ready to die if at all. The client process should not be killed as that will kill yourself as I mentioned above. Seems to me like the requirement interpretation should be make sure you wait for any exe custom actions your spin up during your installation. WiX will let you wait for their completion already. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 2:42 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; Thanks for responding. The top installer is not ours it is of our customer who takes software from us and several other vendors. Their top level installer expects our installer to stop all the processes that started for our installation and that includes msiserver.exe also. If I use service APIs what will be the id for the msiserver service? Can you please point me to a sample code. Thanks. - Original Message From: Wilson, Phil phil.wil...@invensys.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 12:33:08 PM Subject: Re: [WiX-users] how to stop msiserver after installation; It sounds like you have a design that expects the Windows Installer service (or some number of processes called msiexec.exe?) to stop when a bunch of your installs have finished. The Windows Installer service isn't a child process! Like any other Windows service you stop it with the service APIs, but really, your design is just very very wrong. If those other installs are completely out of your control (and you can't install them yourself so you *know* when they complete) you'd be better off polling for the ProductCode of last one you launched to see when it is finally installed. Phil Wilson -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 12:05 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] how to stop msiserver after installation; After my installer finishes, msiserver keeps running for long time. How can I stop it? Our top level installer package (not MSI based) waits for all the child processes launched by a specific installer to end/stop before it can proceed with the installation of other packages. How can I stop msiserver? Any help will be highly appreciated. Thanks. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated
[WiX-users] BadImageFormatException, Microsoft.Deployment.WindowsInstaller - RESOLVED!
I previously posted that my .NET 4 project with .NET 4 custom actions had been failing. This has been resolved, thanks to a co-worker's good catch. I can now author a totally .NET 4 app from VS 2010 with WIX 3.5. The MSI log error was: System.BadImageFormatException: Could not load file or assembly 'CustomAction1' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. ... at Microsoft.Deployment.WindowsInstaller.CustomActionProxy.GetCustomActionMetho d(Session session, String assemblyName, String className, String methodName) The trick is to modify the default CustomAction.config file, included in a CA project when it is created with Visual Studio. Use these values: startup useLegacyV2RuntimeActivationPolicy=true supportedRuntime version=v4.0 / /startup In my case, I removed other values for supportedRuntime, but that may not have been necessary. Also, in the CA project, for CustomAction.config properties, set 'Copy To Output Directory' to 'Copy Always'. Also, you might see SFXCA: Failed to get requested CLR info. Error code 0x80131700. This is fixed by setting useLegacyV2RuntimeActivationPolicy to true. There, now I think I included all the keywords to help someone find this. Gary -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] how to stop msiserver after installation;
I have to agree with the others on this mailing list. You need to leave the server process alone. The requirement from your customer is wrong. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 3:06 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; when our installer starts I see that: under processes msiexec.exe starts running and under services msiserver start running. Once our installer completes, msiexec is no longer visible in task manager while msiserver keeps running untill after 10 minutes and then its status changes to stopped. Customer's requirement is to stop msiserver immediately after our installation completes. All of our custom actions are synchronous return=check. - Original Message From: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 2:53:43 PM Subject: Re: [WiX-users] how to stop msiserver after installation; I don't think you should be trying to stop msiserver.exe. 1.) I don't know what msiserver.exe is. I would expect to see msiexec.exe but you certainly don't want to stop these process as one of them will be yourself. 2.) The Windows Installer architecture uses a client process and a server process. You really want the OS to determine when the server process is ready to die if at all. The client process should not be killed as that will kill yourself as I mentioned above. Seems to me like the requirement interpretation should be make sure you wait for any exe custom actions your spin up during your installation. WiX will let you wait for their completion already. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 2:42 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; Thanks for responding. The top installer is not ours it is of our customer who takes software from us and several other vendors. Their top level installer expects our installer to stop all the processes that started for our installation and that includes msiserver.exe also. If I use service APIs what will be the id for the msiserver service? Can you please point me to a sample code. Thanks. - Original Message From: Wilson, Phil phil.wil...@invensys.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 12:33:08 PM Subject: Re: [WiX-users] how to stop msiserver after installation; It sounds like you have a design that expects the Windows Installer service (or some number of processes called msiexec.exe?) to stop when a bunch of your installs have finished. The Windows Installer service isn't a child process! Like any other Windows service you stop it with the service APIs, but really, your design is just very very wrong. If those other installs are completely out of your control (and you can't install them yourself so you *know* when they complete) you'd be better off polling for the ProductCode of last one you launched to see when it is finally installed. Phil Wilson -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 12:05 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] how to stop msiserver after installation; After my installer finishes, msiserver keeps running for long time. How can I stop it? Our top level installer package (not MSI based) waits for all the child processes launched by a specific installer to end/stop before it can proceed with the installation of other packages. How can I stop msiserver? Any help will be highly appreciated. Thanks. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended
Re: [WiX-users] BadImageFormatException, Microsoft.Deployment.WindowsInstaller - RESOLVED!
I haven't really played with DTF and 4.0 much yet. Is there a solution for writing a CLR 2.0 Custom Action and then have it work if you have either .NET 2-3.5 or .NET 4 installed? Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Gary Gocek g...@gocek.org To: wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 5:37:13 PM Subject: [WiX-users] BadImageFormatException, Microsoft.Deployment.WindowsInstaller - RESOLVED! I previously posted that my .NET 4 project with .NET 4 custom actions had been failing. This has been resolved, thanks to a co-worker's good catch. I can now author a totally .NET 4 app from VS 2010 with WIX 3.5. The MSI log error was: System.BadImageFormatException: Could not load file or assembly 'CustomAction1' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. ... at Microsoft.Deployment.WindowsInstaller.CustomActionProxy.GetCustomActionMetho d(Session session, String assemblyName, String className, String methodName) The trick is to modify the default CustomAction.config file, included in a CA project when it is created with Visual Studio. Use these values: startup useLegacyV2RuntimeActivationPolicy=true supportedRuntime version=v4.0 / /startup In my case, I removed other values for supportedRuntime, but that may not have been necessary. Also, in the CA project, for CustomAction.config properties, set 'Copy To Output Directory' to 'Copy Always'. Also, you might see SFXCA: Failed to get requested CLR info. Error code 0x80131700. This is fixed by setting useLegacyV2RuntimeActivationPolicy to true. There, now I think I included all the keywords to help someone find this. Gary -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] gui
SharpSetup uses embedded language transforms as well but also provides bootstrapper that allows you to choose language either in GUI or from command line. -- Regards, Tomasz Grobelny On Friday 24 September 2010 09:48:23 David Amey wrote: Thankyou for this, but it's not quite the solution I need. I need the option of the language selection, as the client needs different languages on different machines. Thankyou for your time! David -Original Message- From: Dave Brotherstone [mailto:dav...@pobox.com] Sent: 23 September 2010 17:29 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] gui David Amey da...@creative-engine.co.uk wrote: Does anyone know how I could create a drop down selection for languages, used to localise an install? Depending on your requirements, MSI can do this for you, selecting the language from the OS language settings - it involves embedding a transform named languageID.mst in your MSI - see http://www.installsite.org/pages/en/msi/articles/embeddedlang/index.htm for details. Note that it is (AFAIK) officially undocumented, but is used internally by instmsi.exe, so it's not quite so dangerous to use it. -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users --- --- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] how to detect that a anti virus or firewall is stopping from running a custom action
Hi, Sometimes when user has tight anti virus and firewall rules configured on his machine, our installer fails. Our installer has a dll having several custom actions definitions. How can I detect that anti virus or firewall is stopping the installer to run a custom action ? Please help me if any body have any idea. Regards, Sanjay Rao -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] how to detect that a anti virus or firewall is stopping from running a custom action
You should look at what the AV says in its logs. If it's at all reasonable it will tell you exactly what it prevented. Culprits tens to be writing to the Run or RunOnce registry keys and VBScript, *especially* use of FileSystemObject. Phil Wilson -Original Message- From: Sanjay Rao [mailto:s...@noida.interrasystems.com] Sent: Tuesday, September 28, 2010 4:57 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] how to detect that a anti virus or firewall is stopping from running a custom action Hi, Sometimes when user has tight anti virus and firewall rules configured on his machine, our installer fails. Our installer has a dll having several custom actions definitions. How can I detect that anti virus or firewall is stopping the installer to run a custom action ? Please help me if any body have any idea. Regards, Sanjay Rao -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77nav_id=80prev_id=77. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] how to stop msiserver after installation;
I'll add a comment here about that over-used word requirement and Edwin is completely correct. Too many times that word gets used to mean you must do this - it's a (deep breath) REQUIREMENT!!! and then it turns out to be some weird (especially in this case) piece of implementation. A real requirement is something like Edwin's. How can a requirement possibly be turn off Windows Installer when the install is complete? What are they thinking they can achieve with this? Phil Wilson -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Tuesday, September 28, 2010 3:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; I have to agree with the others on this mailing list. You need to leave the server process alone. The requirement from your customer is wrong. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 3:06 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; when our installer starts I see that: under processes msiexec.exe starts running and under services msiserver start running. Once our installer completes, msiexec is no longer visible in task manager while msiserver keeps running untill after 10 minutes and then its status changes to stopped. Customer's requirement is to stop msiserver immediately after our installation completes. All of our custom actions are synchronous return=check. - Original Message From: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 2:53:43 PM Subject: Re: [WiX-users] how to stop msiserver after installation; I don't think you should be trying to stop msiserver.exe. 1.) I don't know what msiserver.exe is. I would expect to see msiexec.exe but you certainly don't want to stop these process as one of them will be yourself. 2.) The Windows Installer architecture uses a client process and a server process. You really want the OS to determine when the server process is ready to die if at all. The client process should not be killed as that will kill yourself as I mentioned above. Seems to me like the requirement interpretation should be make sure you wait for any exe custom actions your spin up during your installation. WiX will let you wait for their completion already. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 2:42 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; Thanks for responding. The top installer is not ours it is of our customer who takes software from us and several other vendors. Their top level installer expects our installer to stop all the processes that started for our installation and that includes msiserver.exe also. If I use service APIs what will be the id for the msiserver service? Can you please point me to a sample code. Thanks. - Original Message From: Wilson, Phil phil.wil...@invensys.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 12:33:08 PM Subject: Re: [WiX-users] how to stop msiserver after installation; It sounds like you have a design that expects the Windows Installer service (or some number of processes called msiexec.exe?) to stop when a bunch of your installs have finished. The Windows Installer service isn't a child process! Like any other Windows service you stop it with the service APIs, but really, your design is just very very wrong. If those other installs are completely out of your control (and you can't install them yourself so you *know* when they complete) you'd be better off polling for the ProductCode of last one you launched to see when it is finally installed. Phil Wilson -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 12:05 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] how to stop msiserver after installation; After my installer finishes, msiserver keeps running for long time. How can I stop it? Our top level installer package (not MSI based) waits for all the child processes
Re: [WiX-users] how to stop msiserver after installation;
Sadly I see it all the time. Some Systems Engineer will come into my office and show me some Tech Memorandum that was supposedly incorporated into the contract and agreed to by the company and the customer and if I don't do all these crazy things ( read anti-pattern ) by tomorrow night we are going to be in breach of contract. Sometimes I feel like the dreaded bathtub curve never goes away. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Wilson, Phil phil.wil...@invensys.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 7:27:43 PM Subject: Re: [WiX-users] how to stop msiserver after installation; I'll add a comment here about that over-used word requirement and Edwin is completely correct. Too many times that word gets used to mean you must do this - it's a (deep breath) REQUIREMENT!!! and then it turns out to be some weird (especially in this case) piece of implementation. A real requirement is something like Edwin's. How can a requirement possibly be turn off Windows Installer when the install is complete? What are they thinking they can achieve with this? Phil Wilson -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Tuesday, September 28, 2010 3:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; I have to agree with the others on this mailing list. You need to leave the server process alone. The requirement from your customer is wrong. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 3:06 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; when our installer starts I see that: under processes msiexec.exe starts running and under services msiserver start running. Once our installer completes, msiexec is no longer visible in task manager while msiserver keeps running untill after 10 minutes and then its status changes to stopped. Customer's requirement is to stop msiserver immediately after our installation completes. All of our custom actions are synchronous return=check. - Original Message From: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 2:53:43 PM Subject: Re: [WiX-users] how to stop msiserver after installation; I don't think you should be trying to stop msiserver.exe. 1.) I don't know what msiserver.exe is. I would expect to see msiexec.exe but you certainly don't want to stop these process as one of them will be yourself. 2.) The Windows Installer architecture uses a client process and a server process. You really want the OS to determine when the server process is ready to die if at all. The client process should not be killed as that will kill yourself as I mentioned above. Seems to me like the requirement interpretation should be make sure you wait for any exe custom actions your spin up during your installation. WiX will let you wait for their completion already. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 2:42 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; Thanks for responding. The top installer is not ours it is of our customer who takes software from us and several other vendors. Their top level installer expects our installer to stop all the processes that started for our installation and that includes msiserver.exe also. If I use service APIs what will be the id for the msiserver service? Can you please point me to a sample code. Thanks. - Original Message From: Wilson, Phil phil.wil...@invensys.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 12:33:08 PM Subject: Re: [WiX-users] how to stop msiserver after installation; It sounds like you have a design that expects the Windows Installer service (or some number of processes called msiexec.exe?) to stop when a bunch of your installs have finished. The Windows
[WiX-users] Failed to build project with wix3.5 in vs2010
Hi, When I build one CustomAction project of Wix3.5, it is failed. I find the dlls (Microsoft.Deployment.WindowsInstaller.dll, system.dll) can't be referenced. It is so strange. Regards, GloverGao -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] how to stop msiserver after installation;
I'm lucky... I have never had to tell somebody that the contract has extraordinarily stupid... and that people with higher pay grades than I are apparently morons... My answer always is No, I don't care what the contract says, it's not my fault the contract writing people are idiots. I have certain amount of professional integrity and I don't let stupid people tell me what to do. But like I said before... I'm lucky. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Tuesday, September 28, 2010 6:24 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; Sadly I see it all the time. Some Systems Engineer will come into my office and show me some Tech Memorandum that was supposedly incorporated into the contract and agreed to by the company and the customer and if I don't do all these crazy things ( read anti-pattern ) by tomorrow night we are going to be in breach of contract. Sometimes I feel like the dreaded bathtub curve never goes away. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Wilson, Phil phil.wil...@invensys.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 7:27:43 PM Subject: Re: [WiX-users] how to stop msiserver after installation; I'll add a comment here about that over-used word requirement and Edwin is completely correct. Too many times that word gets used to mean you must do this - it's a (deep breath) REQUIREMENT!!! and then it turns out to be some weird (especially in this case) piece of implementation. A real requirement is something like Edwin's. How can a requirement possibly be turn off Windows Installer when the install is complete? What are they thinking they can achieve with this? Phil Wilson -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Tuesday, September 28, 2010 3:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; I have to agree with the others on this mailing list. You need to leave the server process alone. The requirement from your customer is wrong. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 3:06 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; when our installer starts I see that: under processes msiexec.exe starts running and under services msiserver start running. Once our installer completes, msiexec is no longer visible in task manager while msiserver keeps running untill after 10 minutes and then its status changes to stopped. Customer's requirement is to stop msiserver immediately after our installation completes. All of our custom actions are synchronous return=check. - Original Message From: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 2:53:43 PM Subject: Re: [WiX-users] how to stop msiserver after installation; I don't think you should be trying to stop msiserver.exe. 1.) I don't know what msiserver.exe is. I would expect to see msiexec.exe but you certainly don't want to stop these process as one of them will be yourself. 2.) The Windows Installer architecture uses a client process and a server process. You really want the OS to determine when the server process is ready to die if at all. The client process should not be killed as that will kill yourself as I mentioned above. Seems to me like the requirement interpretation should be make sure you wait for any exe custom actions your spin up during your installation. WiX will let you wait for their completion already. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 2:42 PM To: General discussion for Windows Installer XML
Re: [WiX-users] how to stop msiserver after installation;
I usually can hold then line or know when to pick my battles the other times. I've been known to fire more then a few employers over the years. It's been about two years since I last did this: http://blog.deploymentengineering.com/2008/10/user-data-log-files-best-practices.html I remember how 'brilliant' yet ignorant and stubborn the developers were at that place. I had to fight them so much to do the right things. One day the PM was sitting in a meeting telling me how happy the customer was with the deployment experience yet he acted suprised that it had gone so well as we had fought over the requirements several times a day. I didn't have the heart to tell him that he was an idiot, that I knew exactly what the customer needed to be successful and that I already had another job offer in my hand that I was mulling over. My current job has gone much better. I actually had an loose-canon architect admit to me the other day that the installs go much better when they don't force me to let them shoot themselves in the foot. This is a vast improvement over the last time I worked at this place when they were using thousands of VDPROJ merge modules and InstallUtil custom actions. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Castro, Edwin G. (Hillsboro) edwin.cas...@fiserv.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 9:29:58 PM Subject: Re: [WiX-users] how to stop msiserver after installation; I'm lucky... I have never had to tell somebody that the contract has extraordinarily stupid... and that people with higher pay grades than I are apparently morons... My answer always is No, I don't care what the contract says, it's not my fault the contract writing people are idiots. I have certain amount of professional integrity and I don't let stupid people tell me what to do. But like I said before... I'm lucky. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Tuesday, September 28, 2010 6:24 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; Sadly I see it all the time. Some Systems Engineer will come into my office and show me some Tech Memorandum that was supposedly incorporated into the contract and agreed to by the company and the customer and if I don't do all these crazy things ( read anti-pattern ) by tomorrow night we are going to be in breach of contract. Sometimes I feel like the dreaded bathtub curve never goes away. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Wilson, Phil phil.wil...@invensys.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tue, September 28, 2010 7:27:43 PM Subject: Re: [WiX-users] how to stop msiserver after installation; I'll add a comment here about that over-used word requirement and Edwin is completely correct. Too many times that word gets used to mean you must do this - it's a (deep breath) REQUIREMENT!!! and then it turns out to be some weird (especially in this case) piece of implementation. A real requirement is something like Edwin's. How can a requirement possibly be turn off Windows Installer when the install is complete? What are they thinking they can achieve with this? Phil Wilson -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Tuesday, September 28, 2010 3:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; I have to agree with the others on this mailing list. You need to leave the server process alone. The requirement from your customer is wrong. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Bisht, Pradeep [mailto:pradeep_bi...@yahoo.com] Sent: Tuesday, September 28, 2010 3:06 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] how to stop msiserver after installation; when our installer starts I see that: under processes msiexec.exe starts running and under services msiserver start running. Once our installer completes, msiexec is no longer visible in task
