[WiX-users] 64 bit version of MS build cannot find the WIX toolset
I know there is probably a posting somewhere out on the web describing the issue I am having, but I am not able to find it at the present moment. The problem I am current having is that the 64 bit version of MS build does not properly evaluate the build variables and is not able to find WIX tools. The 32 bit version works correctly and everything is happy, but when I switch MS Build targets everything goes to pot. Does anyone have a way around this issue or a link to the documentation on why I am seeing this? Thank you in advance, Mat Skildum -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset
I am using WIX 3.8 (build 3.8.708). The build system is using the GA version of WIX 3.7. I am havine issues on both systems. -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: Tuesday, August 27, 2013 10:37 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset Which version of WiX are you running? There was a bug a ways back about that. From: mathew.skil...@aspect.com To: wix-users@lists.sourceforge.net Date: Tue, 27 Aug 2013 14:54:30 + Subject: [WiX-users] 64 bit version of MS build cannot find the WIX toolset I know there is probably a posting somewhere out on the web describing the issue I am having, but I am not able to find it at the present moment. The problem I am current having is that the 64 bit version of MS build does not properly evaluate the build variables and is not able to find WIX tools. The 32 bit version works correctly and everything is happy, but when I switch MS Build targets everything goes to pot. Does anyone have a way around this issue or a link to the documentation on why I am seeing this? Thank you in advance, Mat Skildum -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset
All of the WIX projects in question have those lines in place: WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND '$(MSBuildExtensionsPath32)' != '' $(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targets/WixTargetsPath WixTargetsPath Condition= '$(WixTargetsPath)' == '' $(MSBuildExtensionsPath)\Microsoft\WiX\v3.x\Wix.targets/WixTargetsPath I just realized that forgot to mention I was using the .Net 4.0 version of MS Build. MAT SKILDUM SR PRINCIPAL ENGINEER +1 (630) 227.8534 WORK +1 (847) 909.9921 MOBILE mathew.skil...@aspect.com aspect.com -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Tuesday, August 27, 2013 11:05 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset How far back do you wixproj files go? Modern ones should have something like: lt;WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND '$(MSBuildExtensionsPath32)' != '' gt;$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targetslt;/WixTargetsPathgt; lt;WixTargetsPath Condition= '$(WixTargetsPath)' == '' gt;$(MSBuildExtensionsPath)\Microsoft\WiX\v3.x\Wix.targetslt;/WixTargetsPathgt; Older files don't have both lines causing things to fail on x64 systems. -- John Merryweather Cooper Build Install Engineer -- ESA Jack Henry Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] Sent: Tuesday, August 27, 2013 10:44 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset I am using WIX 3.8 (build 3.8.708). The build system is using the GA version of WIX 3.7. I am havine issues on both systems. -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: Tuesday, August 27, 2013 10:37 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset Which version of WiX are you running? There was a bug a ways back about that. From: mathew.skil...@aspect.com To: wix-users@lists.sourceforge.net Date: Tue, 27 Aug 2013 14:54:30 + Subject: [WiX-users] 64 bit version of MS build cannot find the WIX toolset I know there is probably a posting somewhere out on the web describing the issue I am having, but I am not able to find it at the present moment. The problem I am current having is that the 64 bit version of MS build does not properly evaluate the build variables and is not able to find WIX tools. The 32 bit version works correctly and everything is happy, but when I switch MS Build targets everything goes to pot. Does anyone have a way around this issue or a link to the documentation on why I am seeing this? Thank you in advance, Mat Skildum -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly
Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset
WIX was installed through the released installed and the installation path is C:\Program Files (x86)\WiX Toolset v3.7. Here is an example of the build errors: CustomAction.cs(4,17): error CS0234: The type or namespace name 'Deployment' does not exist in the namespace 'Microsoft' (are you missing an assembly refere nce?) CustomAction.cs(12,58): error CS0246: The type or namespace name 'Session' co uld not be found (are you missing a using directive or an assembly reference?) CustomAction.cs(12,23): error CS0246: The type or namespace name 'ActionResul t' could not be found (are you missing a using directive or an assembly referen ce?) Mat Skildum -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Tuesday, August 27, 2013 11:55 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset Ok. So the proj files are modern. What is the path of WiX on the build server and how was it installed there? What is the specific message from the build logs? -- John Merryweather Cooper Build Install Engineer -- ESA Jack Henry Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] Sent: Tuesday, August 27, 2013 11:38 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset All of the WIX projects in question have those lines in place: WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND '$(MSBuildExtensionsPath32)' != '' $(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targets/WixTargetsPath WixTargetsPath Condition= '$(WixTargetsPath)' == '' $(MSBuildExtensionsPath)\Microsoft\WiX\v3.x\Wix.targets/WixTargetsPath I just realized that forgot to mention I was using the .Net 4.0 version of MS Build. MAT SKILDUM SR PRINCIPAL ENGINEER +1 (630) 227.8534 WORK +1 (847) 909.9921 MOBILE mathew.skil...@aspect.com aspect.com -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Tuesday, August 27, 2013 11:05 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset How far back do you wixproj files go? Modern ones should have something like: lt;WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND '$(MSBuildExtensionsPath32)' != '' gt;$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targetslt;/WixTargetsPathgt; lt;WixTargetsPath Condition= '$(WixTargetsPath)' == '' gt;$(MSBuildExtensionsPath)\Microsoft\WiX\v3.x\Wix.targetslt;/WixTargetsPathgt; Older files don't have both lines causing things to fail on x64 systems. -- John Merryweather Cooper Build Install Engineer -- ESA Jack Henry Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] Sent: Tuesday, August 27, 2013 10:44 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset I am using WIX 3.8 (build 3.8.708). The build system is using the GA version of WIX 3.7. I am havine issues on both systems. -Original Message- From: Blair Murri [mailto:os...@live.com] Sent: Tuesday, August 27, 2013 10:37 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset Which version of WiX are you running? There was a bug a ways back about that. From: mathew.skil...@aspect.com To: wix-users@lists.sourceforge.net Date: Tue, 27 Aug 2013 14:54:30 + Subject: [WiX-users] 64 bit version of MS build cannot find the WIX toolset I know there is probably a posting somewhere out on the web describing the issue I am having, but I am not able to find it at the present moment. The problem I am current having is that the 64 bit version of MS build does not properly evaluate the build variables and is not able to find WIX tools. The 32 bit version works correctly and everything is happy, but when I switch MS Build targets everything goes to pot. Does anyone have a way around this issue or a link to the documentation on why I am seeing this? Thank you in advance, Mat Skildum -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users
Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset
All hint paths are correct as everything build correctly in Visual Studio (2010 and 2012). The only time it fails is when I use the 64 bit version of MS Build. Mat Skildum -Original Message- From: Edwin Castro [mailto:0ptikgh...@gmx.us] Sent: Tuesday, August 27, 2013 12:54 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset On 8/27/13 10:05 AM, Skildum, Mathew wrote: Here is an example of the build errors: CustomAction.cs(4,17): error CS0234: The type or namespace name 'Deployment' does not exist in the namespace 'Microsoft' (are you missing an assembly refere nce?) CustomAction.cs(12,58): error CS0246: The type or namespace name 'Session' co uld not be found (are you missing a using directive or an assembly reference?) CustomAction.cs(12,23): error CS0246: The type or namespace name 'ActionResul t' could not be found (are you missing a using directive or an assembly referen ce?) These are C# compile errors. It appears you might be missing a reference to a DTF assembly. Or perhaps the assembly reference you already has an incorrect HintPath and can't be found...? -- Edwin G. Castro -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset
The Microsoft.Deployment.WindowsInstaller assembly is located in the default installation location. No customization has been done to the system or the projects. Here is the project file section that lists the above assembly refference: ItemGroup Reference Include=System / Reference Include=System.Core RequiredTargetFramework3.5/RequiredTargetFramework /Reference Reference Include=System.Management.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL SpecificVersionFalse/SpecificVersion HintPath..\..\Assemblies\Powershell\System.Management.Automation.dll/HintPath PrivateTrue/Private /Reference Reference Include=System.Windows.Forms / Reference Include=Microsoft.Deployment.WindowsInstaller / /ItemGroup Mat Skildum -Original Message- From: Edwin Castro [mailto:0ptikgh...@gmx.us] Sent: Tuesday, August 27, 2013 1:13 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset On 8/27/13 11:03 AM, Skildum, Mathew wrote: All hint paths are correct as everything build correctly in Visual Studio (2010 and 2012). The only time it fails is when I use the 64 bit version of MS Build. Can you provide the reference XML from the project file? I assume you have not modified them manually, correct? -- Edwin G. Castro -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] General question about patching multi-instance MSI installs
I am currently working on implementing a multiple instance MSI base installation using WIX and am trying to validate that patching will work correctly before I go any further. I have been able to create a patch that updates all instances exactly as I would suspect, but when I try to install a second patch, I get a 1642 error that the product to be updated is not installed. If I uninstall the existing patch the new patch will install just fine so I am thinking that the issue might be version related since the patches are all cumulative. I checked the installation logs and they do not tell me anything about what the issue might be and I am hoping someone else has hit a similar situation and can tell me what settings in the PCP file I need to check for this to work. Thank you in advance, Mat Skildum -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] General question about patching multi-instance MSI installs
Thank you for the information. I have reviewed this and a few other post and worked through all of them. The problem it seems is in the custom application I built to generate patches. When I modified it to use the parts of the WIX SDK, I broke something and all patches now break. I am going to have to revert back to the original source and do the conversion at a much slower pace until I figure out where I introduced the issue. MAT SKILDUM -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Tuesday, July 02, 2013 10:25 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] General question about patching multi-instance MSI installs You might want to have a read over at http://stackoverflow.com/questions/14814014/msi-multi-instance-installation-with-patches. Multi-Instance installs are tricky enough to get right, adding the patching on top of it can become real confusing rather quickly. Other than that, there isn't much we could do without the command line / logs from when you are trying to apply the second patch (the failing one). -Original Message- From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] Sent: Tuesday, July 02, 2013 7:55 AM To: General discussion for Windows Installer XML toolset. (wix-users@lists.sourceforge.net) Subject: [WiX-users] General question about patching multi-instance MSI installs I am currently working on implementing a multiple instance MSI base installation using WIX and am trying to validate that patching will work correctly before I go any further. I have been able to create a patch that updates all instances exactly as I would suspect, but when I try to install a second patch, I get a 1642 error that the product to be updated is not installed. If I uninstall the existing patch the new patch will install just fine so I am thinking that the issue might be version related since the patches are all cumulative. I checked the installation logs and they do not tell me anything about what the issue might be and I am hoping someone else has hit a similar situation and can tell me what settings in the PCP file I need to check for this to work. Thank you in advance, Mat Skildum -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Extracting transforms from the _storages table
Does anyone have a way to extract embedded transforms from the _storages table in MSI? I know you can do it with Msidb.exe, and I have read you can do it through OLE structured storage APIs but have not found any examples on this method as of yet. Any pointers in the right direction would be great. Thank you in advance, Mat Skildum -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Upgrading a multiple instance install
Everyone, I have a multiple instance install that I am working on and ran into an issue doing upgrade testing. It looks like all instances are removed when one of the instances is upgraded. This looks to be because WIX does not allow for the UpgradeCode to be modified in the instance element. I found the following discussion that hints that there is a feature request to add this support but I have not been able to find the reference as of yet. http://sourceforge.net/mailarchive/message.php?msg_id=28034637 To support this it looks like I am going to have to get the build process to manually generate the required instance transforms. Does anyone have any incite on a better way to get instance transforms working correctly without a lot of workarounds? Thank you, MAT SKILDUM SR PPRINCIPAL ENGINEER mathew.skil...@aspect.commailto:mathew.skil...@aspect.com aspect.comhttp://www.aspect.com/ -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hide/blank out Passwords in MSI log file
This method only hides the value of the property when it is directly printed in the log file. If you pass the property to a deferred custom action, it will be visible in plain text once again in the custom action data property. You either need to mark all custom action data properties as hidden, which makes debugging very difficult. With this solution you would need to print each custom action data value to the log file by hand and hide the password when you process the value. If you do not want to do that, you could encrypt the password and pass the encrypted password to the deferred custom actions. With this method you need to decrypt the value when needed. This is a very nasty situation and no solution is very nice, Mat Skildum -Original Message- From: Chad Petersen [mailto:chad.peter...@harlandfs.com] Sent: Thursday, May 02, 2013 4:54 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Hide/blank out Passwords in MSI log file If possible paste in a snippet of your log file around where the password is seen. I tried for a long time to hide passwords using the same method. But it was some built-in custom actions that were logging my passwords rather than code I'd written myself. Property Id=ConfigureIIsExec Hidden=yes/ Property Id=ExecuteSqlStrings Hidden=yes/ These were two entries that I made to make those extensions hide the data passed to them, such as my password. -Original Message- From: Jeremiahf [mailto:jeremi...@gmail.com] Sent: Thursday, May 02, 2013 2:38 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Hide/blank out Passwords in MSI log file I have tried that and no luck. My MSI is installed via command line. I've even tried to give the property Id a value in case I missed something and still doesn't work. Property Id=PASSWORD Value=password Hidden=yes Secure=yes / My test system is running Server 2003 R2 SP 2 windows installer version 4.5 6001.22159 I've upgraded from WIX 3.6 TO 3.7 in case it was a bug as I have found in hundreds of blogs online but every time I see that a fix was submitted, I can't tell what version it was submitted in. (sorry for the run on sentence.) J On Thu, May 2, 2013 at 4:24 PM, Steven Ogilvie steven.ogil...@titus.comwrote: I declare the property: Property Id=WEBAPPPOOL_PASSWORD Hidden=yes Secure=yes/ This is how I use my password controls: Control Id=textBoxPassword Type=Edit Height=15 Width=177 X=180 Y=152 Property=WEBAPPPOOL_PASSWORD Password=yes TabSkip=no / Logfile: MSI (c) (70:1C) [14:50:59:778]: PROPERTY CHANGE: Adding WEBAPPPOOL_PASSWORD property. Its value is '**' -Original Message- From: Jeremiahf [mailto:jeremi...@gmail.com] Sent: May-02-13 5:08 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Hide/blank out Passwords in MSI log file Has anyone had luck with this? I have tried using Hidden, HideTarget and I still see the password in my logs. Is this still a bug in windows installer? Thanks in advance, -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- They may forget what you said but they will never forget how you made them feel. -- Anonymous -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to
Re: [WiX-users] Wildcards
This process will not generate the same GUIDs and other identifiers you need for patching. It will only generate a unique usable WIX fragment you can include. You can use this for upgrades as you do not use component GUIDs as much in the upgrade process, but if you want to support patches you will need to keep the fragment around to preserve the needed identifiers. -Original Message- From: Gareth Williams [mailto:gar...@trinitydigital.co.uk] Sent: Wednesday, April 10, 2013 7:26 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wildcards Is it smart enough to always generate the same guid in the face of the same file for 'upgrades' etc.? Seems I have a lot more learning to do. Thanks Best regards Mr. Gareth Williams Trinity Digital -Original Message- From: ptr [mailto:ptrajku...@gmail.com] Sent: 10 April 2013 13:09 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wildcards You can easily use a HeatDirectory task to achieve what you want. Basically it will walk the directory tree and create a wix file that you can use in your project. On Wed, Apr 10, 2013 at 2:44 AM, Gareth Williams gar...@trinitydigital.co.uk wrote: Hello All. Considering using WiX to build an installation system for a clients product. However their file set can change quite dramatically depending on the customer for whom the installation is meant for - installs are specific to a customer. They propose to manage this by simply copying only the customer specific folder data to the 'installation file set' and then building the install image. There can be hundreds of files per customer and many customers world wide - so an installation system per customer is not practical either. Okay so every file for every customer could be included but there is a risk that it exposes the customer base - one customer could install files specific to another customer. Can WiX support wildcards to allow 'inclusion of a folder / its subfolders'? My guess is not from reading the tutorials - every file has to be given a unique xml entry and guid? Best regards Mr. Gareth Williams Trinity Digital -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Best way to choose Windows Auth vs. SQL Auth
I do this by presenting a dialog to the user and they can choose which option they want. I then have a single action on the back end that sets up the correct ADO.Net connection string based on the users choices. By doing this you are not duplicating code, you just have a minor detour is SQL authentication is selected as that requires a few more option in the connection string. Mat Skildum -Original Message- From: George Fleming [mailto:gef...@microsoft.com] Sent: Monday, January 28, 2013 1:22 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Best way to choose Windows Auth vs. SQL Auth I need to create a database, and let user choose Windows Auth or SQL Auth. It looks like you could do it with two different components, and two separate conditions, but that doesn't seem very elegant and creates duplicate code. I see old threads such as this that seem like a better solution, but I don't know if it's ever been implemented. http://www.mail-archive.com/wix-devs@lists.sourceforge.net/msg01154.html Anyone has example on the current (and elegant) way to choose the SQL authentication mode? How do I create a null util:user? -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Removing a component during a minor upgrade
You can remove a component during a minor update, but it is not recommended as you are orphaning the file(s) when the product is uninstalled. I have done this when it is absolutely necessary, it just takes adding the correct remove file entries to clean things up correctly. As with any change, testing is the key as some changes will force a patch to be non-removable. Mat Skildum -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Thursday, November 01, 2012 2:04 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Removing a component during a minor upgrade Is it possible to remove a component during a minor upgrade? I know http://msdn.microsoft.com/en-us/library/Aa367850 indicates that removing a component requires the product code to be changed (which would force a major upgrade). But from http://msdn.microsoft.com/en-us/library/aa370093.aspx, Windows Installer 4.5 and later: The component can be removed correctly using Windows Installer 4.5 and later by setting the msidbComponentAttributesUninstallOnSupersedence attribute in the Component Table or by setting the MSIUNINSTALLSUPERSEDEDCOMPONENTS property. I also found http://sourceforge.net/p/wix/bugs/1193/ which seems to indicate that this isn't possible. Thanks, Jacob -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Occasional rundll32 error with OLE .NET custom actions
I have multiple custom actions the access SQL server through OLE .NET and occasionally I will get a rundll32 error that pops up on the screen. The popup looks to come from Ole .Net process running the SQL scripts and not directly from the install itself. The actual error code is RUNDLL32 returned error code: 255. Does anyone have any idea on how to debug these situations or to trap these errors? Since the issue cannot be easily reproduced, I am looking to ways to better log the situation to see what may be going on. Any help would be great, Mat Skildum -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Outcurve License question
I know this may be covering the same ground as previous discussions, but I just had the legal team of my company look at the license that is shipped with the WIX 3.6 tool set. According to the way the license reads you must ship the source for DTF along with every installation that uses this part of WIX. The part of the license that states this is as follows: 3. Conditions and Limitations (A) Reciprocal Grants- For any file you distribute that contains code from the software (in source code or binary format), you must provide recipients the source code to that file along with a copy of this license, which license will govern that file. You may license other files that are entirely your own work and do not contain code from the software under any terms you choose. Even though the DTF assemblies are embedded in the installation, they are technically shipped to customers thus making this clause active. This means that we have to include with our products the source code for DFT or any other WIX assembly you may use. If the phrase in source code or binary format was just in source code then this would not be required. Does anyone have anyone have any other insight into this requirement? How are some of other companies handling this? Thank you, Mat Skildum Sr. Principal Engineer Aspect Software mathew.skil...@aspect.com -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Add/remove Programs
You may want to check the values in the Upgrade table. It sounds as though the existing values do not cover the installation you are trying to upgrade. Pay specific attention to the listed upgrade codes and the version settings. Mat Skildum -Original Message- From: Ian Brooke [mailto:ianbro...@hotmail.com] Sent: Tuesday, May 08, 2012 8:22 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Add/remove Programs Thanks for your reply Neil, I'm not aware of a Package Code in Installshield, however the Product Code has changed and the Version number has changed (from 7.0.2 to 7.0.4) and the Upgrade Code has remained the same so I have no idea what's going on. Sounds as though it's an Installshield problem though rather than one with the Windows Installer. Looks like I'm going to have to spend the time to switch it to WiX, not something I wanted to do at this moment in time :( Ian -Original Message- From: Neil Sleightholm Sent: Tuesday, May 08, 2012 12:26 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Add/remove Programs That is supported by Windows Installer and shouldn't be happening if your MSI is setup correctly even in Installshield. For a major upgrade you need to change the Package code, Product code and version and leave the Upgrade code the same. WiX 3.5 makes this easy to setup http://wix.sourceforge.net/manual-wix3/major_upgrade.htm, http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/ Here is the setup for v3 http://neilsleightholm.blogspot.co.uk/2009/01/wix-script-for-major-upgrades.html Neil -Original Message- From: Ian Brooke [mailto:ianbro...@hotmail.com] Sent: 08 May 2012 01:38 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Add/remove Programs I hope you don't mind this slightly unusual question! We have a product currently installed by Installshield (Express 2012) which we are considering switching to WiX but don't really want to spend the time doing that if it doesn't solve our problem. What I really need to determine is if this is standard Windows Installer behaviour or, if I can stop it happening by switching to WiX. Here's the problem - We are creating an msi embedded exe which is intended to either upgrade an existing version if one exists on the target computer otherwise do a full install. The upgrade has a new Product Code but the existing Upgrade Code. Both the upgrade and install appear to work fine, except Problem 1. After an upgrade if we check Add/Remove Programs there are 2 entries, one for the old version and one for the new one. Problem 2. After an upgrade I can use the old version uninstall entry and that works Ok and leaves the new version Ok. However, if I then uninstall the new version it leaves an empty application folder (which was originally created by the old version install) under Program Files(x86). I'd really like to stop both of these happening. Thanks for any advise. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will
Re: [WiX-users] WiX 3.5 patch: newly added feature is automaticallyinstalled
By default when a new sub feature is added it is automatically enabled if the parent is enabled. This is the way MSI has always functioned in my experience. I do not know where this functionality is documented. It is always best to add new files to existing features so that you do not have to deal with this, or you issue a updated install (new MSI) as the update to get the functionality you want. You could also try writing a custom action to turn the feature back off, that that would be difficult in my opinion especially if your patches are all cumulative. From: Zlatko Lovcevic [zlatko9...@yahoo.com] Sent: Friday, April 20, 2012 5:53 AM To: Peter Shirtcliffe; General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WiX 3.5 patch: newly added feature is automaticallyinstalled I have also a new subfeature consisting of new components only and that feature also gets automatically installed. From: Peter Shirtcliffe pshirtcli...@sdl.com To: Zlatko Lovcevic zlatko9...@yahoo.com; General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Thursday, April 19, 2012 10:52 AM Subject: RE: [WiX-users] WiX 3.5 patch: newly added feature is automaticallyinstalled In a patch (small/minor update), you cannot add existing components to a new feature or move components between features. That's not valid. There's a summary here http://kb.flexerasoftware.com/doc/Helpnet/installshield12helplib/MajorMinorSm all.htm -Original Message- From: Zlatko Lovcevic [mailto:zlatko9...@yahoo.com] Sent: 19 April 2012 08:28 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] WiX 3.5 patch: newly added feature is automaticallyinstalled What causes newly added (not top level) feature using purely WiX (3.5) to be automatically installed? I added new feature which contained both existing and new components and it was way above the INSTALLLEVEL and patch installation installed it automatically. I've checked the verbose installation log and all I found was this: PROPERTY CHANGE: Adding ADDLOCAL property. Its value is 'NewFeature'. Feature: NewFeature; Installed: Absent; Request: Local; Action: Local - - For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Disable Next Button When TextBox is Empty
MSI does not support directly support what you are trying to do with text boxes. You can do this sort of thing with radio buttons and check boxes as they cause the MSI engine to evaluate the dialog when used. A text box or other text controls do not cause this behavior so your button will remain disabled until the dialog is refreshed (hitting the back or cancel buttons). You will need to leave the next button active and put a custom action on the next button that will validate that the text box if filled properly. You then control moving forward in the installation by setting a property if all is well. You can then use this property to control the forward movement of the install. On a side note, if you have seen this behavior it was probably a wrapper over the install. You can do this type of action in C# or other programming languages, but not directly in MSI. Mat Skildum From: Ravi Raj [raviraj.callin...@gmail.com] Sent: Monday, January 23, 2012 1:18 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Disable Next Button When TextBox is Empty Hi, I am implementing a textbox control having value fetched from registry (after LicenseAggrement dialog). When registry has some value, the control works fine but when delete the text in the textbox, the Next button does not disable. But when I click on some other button (like back or cancel), the control works then. Same thing happens when I enter some text in textbox, Next remains disabled till I click some other button. How can I make this work correctly in real time? Code for Next Button is here: *Control Id=Next Type=PushButton X=236 Y=243 Width=56 Height=17 Default=yes Text=!(loc.ButtonText_Next)Condition Action=disable![CDATA[SDK_MACHINE = ]]/ConditionCondition Action=enableSDK_MACHINE lt;gt; /ConditionPublish Event=NewDialog Value=VirtualizationDlg1/Publish/Control* and for textbox is: *Control Id=MSNameEdit Type=Edit X=25 Y=105 Width=220 Height=18 Property=SDK_MACHINE /* SDK_MACHINE property: Property Id=SDK_MACHINE Secure=yes RegistrySearch Id=sdk_Machine Root=HKCU Key=Software\.\.\. Name=MachineName Type=raw //Property -- Thanks and Regards, Ravi Raj -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Custom UI examples for Dark
I recently started looking into Dark and how it functions, but I cannot find any examples of how to do custom UIs except for the WIX 3.6 install. I have downloaded the WIX 3.6 source code and am in the process of working though how the UI works in this case. Are there any other good examples of custom Dark installation UIs available on the web? Thank you in advance, Mat Skildum -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom UI examples for Burn
I just realized that I put the wrong product in my request. I am looking for examples of custom UIs for the WIX bootstrapper (Burn). Again, sorry for the confusion. Mat Skildum Sr. Principal Engineer Aspect Software direct: 630.227.8534 mobile: 847.909.9921 mathew.skil...@aspect.com -Original Message- From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] Sent: Tuesday, December 27, 2011 7:12 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Custom UI examples for Dark I recently started looking into Dark and how it functions, but I cannot find any examples of how to do custom UIs except for the WIX 3.6 install. I have downloaded the WIX 3.6 source code and am in the process of working though how the UI works in this case. Are there any other good examples of custom Dark installation UIs available on the web? Thank you in advance, Mat Skildum -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] What happend to minor upgrade using wix
The main problem I see here is your versioning scheme. MSI only supports the first three places in the version number (X.X.X) and ignores the fourth position. Any version changes need to take place in the first three positions for MSI to recognize a version change. For more information please refer to the MSI, and Microsoft, documentation on versions and use of versioning. You cannot compare what you do in legacy InstallShield (InstallScript) and MSI as they are two different install engines. InstallScript based installs use all four places in the version when it does version compares. When moving from InstallScript to MSI (WIX), or any install engine for that matter, you must be aware of the behavior differences and adjust your development rules accordingly. Mat Skildum -Original Message- From: thomas.debo...@rohde-schwarz.com [mailto:thomas.debo...@rohde-schwarz.com] Sent: Friday, November 04, 2011 8:33 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] What happend to minor upgrade using wix Hi, I'm trying to get my installers to support minor upgrades. I will not change the productcode and also will not support major upgrades so I don't want to add an upgradecode which seams to break minor upgrades. But if I have installed version 1.0.0.1 with msiexec /i I neet to launch the version 1.0.0.2 with REINSTALL=ALL and REINSTALLMODE. :-( If I create a new release like 1.1.0.0 or 2.0.0.0 I will change the productcode but will not allow an upgrade from 1.0.*.* as these versions should be installed side by side. Creating setups with InstallShield in the past I was able to launch version 1.0.0.2 without these properties and the setup came up with a messagebox if I would like to upgrade. I feel confused. Is it now really needed to write a bootstrapper? If yes, is there an example somewhere? Cheers, Thomas -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] patch not patching registry
Registry entries in the MSI are only updated when the file they are linked with are updated. The easiest way to handle this situation is to have a custom action that updates the targeted registry value when the patch is run. Mat Skildum -Original Message- From: Michael Tissington [mailto:michael_tissing...@ciqual.com] Sent: Thursday, September 15, 2011 8:54 AM To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] patch not patching registry I have created a patch based on two admin installs using candle, light and msimsp. In the install I write the version number to a specified registry location. However when I apply the patch, it is not updating the registry to the new value. How do I make a patch that also applies any registry changes too? -- Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problem incorporating merge modules for Crystal Reports for VS2010
I had similar issues using the Crystal merge modules. This problem is because the dependencies the Crystal runtime DLLs have on the Microsoft MFC framework for the targeted version of Visual Studio. You need to make sure that the needed runtime is installed ahead of time, so that when the Crystal DLLS are registered the dependencies can be found. Unfortunately, including the Microsoft runtime merge modules does not work in this case. The Microsoft MFC runtimes must be installed ahead of time for everything to function. Mat Skildum -Original Message- From: Jagdish S. Khedekar [mailto:jagdish.khede...@kpitcummins.com] Sent: Thursday, September 15, 2011 4:50 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Problem incorporating merge modules for Crystal Reports for VS2010 Hi All, I need to incorporate merge modules for Crystal Reports For Visual Studio 2010 into my existing WiX project. I have already followed the standard steps for adding 'Merge Id' and 'MergeRef' elements and initially it seems working properly. But while using my installed application, I get various errors related to Crystal Report which are being caused by not finding proper dlls, or some registration issues. I tried to google on related information, where most of the recommendation says not to use merge modules. I also tried to modify the 'InstallExecuteSequence' and to have some 'EnsureTable Id' elements, but couldn't help much with it. Please let me know if anybody on the list have faced similar issue and could get resolution on it. Also please let me know if there are any alternatives to resolve this issue. Note: There are some warning I am getting while building my WiX project as below - warning LGHT1056 : The Directory table contains a row with primary key(s) 'DesktopFolder' which cannot be merged from the merge module 'C:\CRforVS_MergeModules_13_0_1\CRRuntime_13_0_1.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module. warning LGHT1055 : The InstallExecuteSequence table contains an action 'SetIISNET2VIEWERDIR' which cannot be merged from the merge module 'C:\\CRforVS_MergeModules_13_0_1\CRRuntime_13_0_1_es.msm'. This action is likely colliding with an action in the database that is being created. The colliding action may have been authored in the database or merged in from another merge module. If this is a standard action, it is likely colliding due to a difference in the condition for the action in the database and merge module. If this is a custom action, it should only be declared in the database or one merge module. Thanks and best regards, Jagdish. -- Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Simpler Update possible?
You can do this yourself by using the upgrade table and to check for the product version you are looking for and only set the property. You can then use this property to set an installation condition to display a message that the pervious product must be manually removed before continuing. Please keep in mind this has nothing to do with WIX. As stated many times in this forum, WIX is only method used to create the resulting MSI. For further instructions on using the upgrade table, please refer to the MSI documentation on how the Upgrade table works. You can then use this information to get WIX to create the table the way you need it. Mat Skildum -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problem with Win7
Is the problem on a 32 bit or 64 bit system? Make sure the registry search matches the bit level that was set for component containing the initial registry write. -Original Message- From: yheip p [mailto:zyhp...@gmail.com] Sent: Tuesday, July 05, 2011 5:51 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Problem with Win7 Upon uninstallation, I have a RegistrySearch to get the installation path that I stored during install . And this path is than used for searching a file with directorySearch. This works find in XP but in Win 7 the registrySearch seems failed because it get nothing. I have set the InstallPrivilege attribute to elevated and InstallScope to perMachine Does any know what's wrong ?? Thanks !! -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Rollback custom action not working when Microsoft.Deployment.WindowsInstaller.InstallCanceledException is received
I have run into an interesting issue with some of my rollback custom actions. I usually test this support by canceling the install at a set point and normally my actions fire with not error. But today I ran into an issue where my action enters but it catches the Microsoft.Deployment.WindowsInstaller.InstallCanceledException exception and does not run. This issue only happens when I am preforming a silent repair. When I perform a repair through the full UI everything functions as it should. I cannot seem figure out why there is a difference other than UI and not UI. Does anyone have any ideas or possible solutions as to how to get around this. Mat Skildum Aspect Software direct: 630.227.8534 mobile: 847.909.9921 mathew.skil...@aspect.com -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to cache msi for Modify/Repair to use
As mentioned, this is triggered by the Resolve source action and there are multiple reason why this is needed and there are multiple ways to help reduce the need. The largest cause is when uninstalling a patch. I personally use full file replacement when building patches as it significantly reduce the time it takes to build a patch. Due to this, whenever a patch is uninstalled you need to that the original source available to put the original file back into place. You will also find that having the original source cached is useful when doing any kind of install maintenance in general. If your install has multiple user selectable features, they can modify the install without having to find the original media. If your install ever has to repair, through advertized shortcuts or through add/remove programs, again the original source is ready and available for put what ever files made be needed back into place. If your installs never install to any location but your install folder, you never install shared third party controls, and you do not allow your patches to be uninstalled, you may never have a need for this. From: Peter Shirtcliffe [pshirtcli...@sdl.com] Sent: Wednesday, May 18, 2011 4:49 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to cache msi for Modify/Repair to use I can think of some: Advertising. Use of the resolve source action without a condition to prevent it after first time installation. Binary delta patching where the original file is not available, perhaps because it's been overwritten Since we avoid all of those, we've never had the problem either. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: 18 May 2011 10:43 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to cache msi for Modify/Repair to use I'm curious as to why people encounter issues with this. I've never had to do anything special for Windows Installer to do this automatically for our packages. Unfortunately I have run across situations where upgrade or uninstall of someone else's product prompts Windows Installer to request the MSI so it'd be interesting to know what causes it. Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Wang, Miaohsi [mailto:miaohsi.w...@invensys.com] Sent: 17 May 2011 17:51 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to cache msi for Modify/Repair to use Hi Mat, Thanks a lot for the very useful information. If you can, please also share with us your merge module code. Thank you, Miaohsi -Original Message- From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] Sent: Tuesday, May 17, 2011 8:58 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to cache msi for Modify/Repair to use There is no generic way to do this, You will basically have to write your own custom actions that does this task and updates the source list for the MSI package. I personally created a merge module with a set of actions that cache the MSI in a set location and handle any cleanup and registration that is required. Mat Skildum -Original Message- From: Wang, Miaohsi [mailto:miaohsi.w...@invensys.com] Sent: Tuesday, May 17, 2011 10:44 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] How to cache msi for Modify/Repair to use Dear All, After installing our product, doing Modify/Repair from the Add Remove Programs window requires the original install package to be in the same location where the product is installed from. Does anyone know how to cache msi locally such that Modify/Repair the product via Add Remove Programs window will not require this? Your help will be much appreciated. Thanks a lot, Miaohsi *** 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
Re: [WiX-users] How to cache msi for Modify/Repair to use
There is no generic way to do this, You will basically have to write your own custom actions that does this task and updates the source list for the MSI package. I personally created a merge module with a set of actions that cache the MSI in a set location and handle any cleanup and registration that is required. Mat Skildum -Original Message- From: Wang, Miaohsi [mailto:miaohsi.w...@invensys.com] Sent: Tuesday, May 17, 2011 10:44 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] How to cache msi for Modify/Repair to use Dear All, After installing our product, doing Modify/Repair from the Add Remove Programs window requires the original install package to be in the same location where the product is installed from. Does anyone know how to cache msi locally such that Modify/Repair the product via Add Remove Programs window will not require this? Your help will be much appreciated. Thanks a lot, Miaohsi *** 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). -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] InstallUtil.exe alternatives
There is no runtime or build time solution to replace installutil.exe. The only options are to extract the registry entries that are created and include them in the project or running installutil.exe at runtime. The best option is to extract the registry either by having InstallUtil create a registry file or use the WIX tools. Mat Skildum -Original Message- From: Srivatson Tirumalai [mailto:srivatson.tiruma...@citrix.com] Sent: Tuesday, May 10, 2011 2:00 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] InstallUtil.exe alternatives Hi, Is there a good alternative for installutil.exe in general available in Wix? We have a number of places in our installers where we have to invoke installutil.exe via a custom action for running the installer components in the assembly. One of the main problems in invoking InstallUtil.exe via a custom action is that it results in the ugly DOS windows appearing in the middle of setup. I do not want to use heat/tallow etc. I am looking for some kind of Wix extension. Is there any good solution available in Wix for this? Thanks, -Srivatson -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Registering a WMI interface
Currently I am having problems registering a WMI interface during a product upgrade. Currently I am using a custom action to directly access the exported functions in the file InstallUtilLib.dll. Everything functions as expected on a new install but when the product is upgraded but the wrong version the interface is getting registered. The screwy thing is that if you run a repair on the install, the registration process goes through and completes correctly and the correct files get copied into place and the interface functions. Right now I have no idea where the WMI interface is getting the older version and why the new version is not being copied correctly. Right now the DLLs that control the custom WMI interface are installed in the products target folder. No files are copied into the GAC by any process in the install. The registration process for the WMI interface is run against the file in the installation folder. A coworker and I have both hunted the web for any information on how WMI interfaces are registered and also for possible alternatives to using InstallUtilLib.dll. We have not been able to any alternative and this is not like COM interop where you can just put the registry values into in place and everything is happy. Does anyone have any incite as to what happens during WMI registration? Is there a better way than using InstallUtilLib.dll? Any help would be greatly appreciated, Mat Skildum -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Ensure a Windows Feature is enabled?
The best way to do this is to query the Win23_ServerFeature namespace through WMI in a DTF custom action. Every Windows feature has its own ID that can be searched for. The only restriction I have found with this method is when UAC is enabled. The install must be running with elevated privileges or the logged on use may not have authority to access the WMI namespace. Mat Skildum -Original Message- From: John Thornborrow [mailto:j...@pinesoft.co.uk] Sent: Tuesday, April 19, 2011 7:17 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Ensure a Windows Feature is enabled? Hi Guys, One of our products has a dependency on a Windows Feature (specifically the .NET - WCF - Non-HTTP Activation feature, amongst a few others). Is there a manageable way to ensure that the machine has these features installed/enabled within WiX? Thanks for any info! Regards, J. This email is from Pinesoft Limited. Its contents are confidential to the intended recipient(s) at the email address(es) to which it has been addressed. It may not be disclosed to or used by anyone other than the addressee(s), nor may it be copied in anyway. If received in error, please contact the sender, then delete it from your system. Although this email and attachments are believed to be free of virus, or any other defect which might affect any computer or IT system into which they are received and opened, it is the responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by Pinesoft for any loss or damage arising in any way from receipt or use thereof. Pinesoft Limited are registered in England, Registered number: 2914825. Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA ? Consider your responsibility to the environment - think before you print! -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] XP Install as admin
The is achieved by enabling the install to support elevation. MSI does this by default when UAC is enabled and you are targeting the 4.0 or higher MSI engine. There are two things you need be aware of when using custom actions: 1. All immediate custom actions run in the current users context. 2. Only deferred custom actions can be configured to run in the system context (elevation). Mat Skildum -Original Message- From: Michael Tissington [mailto:michael_tissing...@ciqual.com] Sent: Tuesday, April 12, 2011 4:40 AM To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] XP Install as admin I'm a little confused ... I have seen some installs running on an XP box as a regular user display a dialog that prompts for admin user credentials to run the install as an admin user. How is this achieved? -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ICE03 and version number
No you cannot. You must use a valid version string for the file versions. MSI requires this to be able to do a version compare when needed. You can put this information into the Product version file of the file assembly, but not into the File Version. Mat Skildum -Original Message- From: Michael Tissington [mailto:michael_tissing...@ciqual.com] Sent: Wednesday, April 06, 2011 9:48 AM To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] ICE03 and version number My understanding is that the 4th position in the version number is not used by anything when checking version number. Upgrade, etc ... I see some version numbers on products use the 4th position as free formatted. However when I try to build a package with a number like 1.2.3.123-56-ab-334 I get a candle error that it does not conform to n.n.n.n format. Can I use the version number like this ? Thanks -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installation success or error status: 1603
This is a generic failure error. You need to hunt through the log an find the exact place the install failed. Usually it is a result of custom action failure. Mat Skildum -Original Message- From: swapna.rachako...@thomsonreuters.com [mailto:swapna.rachako...@thomsonreuters.com] Sent: Tuesday, April 05, 2011 8:27 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Installation success or error status: 1603 When I run verbose for .msi . I am getting following error in log, Installation success or error status: 1603 I don't know what it means. -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Query about use of UAC shield on Install button
This is actually a function of MSI not WIX. WIX is just the mechanism to build the MSI where the rules are enforced. MSI does follow these guidelines as far as I know. When you put the UAC shield on a button that does not mean the elevation request will happen right away. MSI does this request in the execute sequence before the any files are copied or deferred actions are run as this is the time when elevation is required. Mat Skildum -Original Message- From: Bruce Cran [mailto:br...@cran.org.uk] Sent: Thursday, March 24, 2011 6:30 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Query about use of UAC shield on Install button Hi, I have a question about the use of the UAC shield icon on the Install button when InstallPrivileges=elevated. According to http://msdn.microsoft.com/en-us/library/aa511445.aspx, Tasks that require immediate elevation when UAC is fully enabled have entry points marked with the UAC shield. In this case, users should expect to see an Elevation UI immediately after clicking such commands But after clicking on Install the wizard moves onto the next page and it can take several seconds for the elevation prompt to appear. I'm wondering if WiX is going against the UI guidelines, or if they instead mean immediate in terms of workflow, not time - i.e. users aren't allowed to interact with the UI between clicking the button and getting the elevation prompt, though the UI can update? -- Bruce Cran -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Query about use of UAC shield on Install button
Using the UAC shield is completely up to you not WIX. Since WIX is just the development environment, the job of following guidelines falls to the user. The WIX compiler can try to guide you down the right path, but it should not force you to do any one thing. The Button control XML has an option called ElevationShield which needs to be enabled to show the icon. It is always best to enable this when you require elevated rights as this is the key indicator to the user the install makes changes to protected areas of the OS. Mat Skildum -Original Message- From: Bruce Cran [mailto:br...@cran.org.uk] Sent: Thursday, March 24, 2011 8:19 AM To: General discussion for Windows Installer XML toolset. Cc: Skildum, Mathew Subject: Re: [WiX-users] Query about use of UAC shield on Install button On Thu, 24 Mar 2011 13:07:30 + Skildum, Mathew mathew.skil...@aspect.com wrote: This is actually a function of MSI not WIX. WIX is just the mechanism to build the MSI where the rules are enforced. MSI does follow these guidelines as far as I know. When you put the UAC shield on a button that does not mean the elevation request will happen right away. MSI does this request in the execute sequence before the any files are copied or deferred actions are run as this is the time when elevation is required. But as I understand it, it's WiX that controls whether or not the button has the shield icon: I'm wondering if it should use the shield icon on the button at all if the elevation request doesn't happen straight away. I'm tending towards yes, since it's a sign that the action that will occur will need to run as Administrator. -- Bruce Cran -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Query about use of UAC shield on Install button
Just because WIX ships a set of UI dialogs does not mean you need to use them. I do not use any of the WIX dialogs and have create my own. This allows me to enable and modify the UI whenever I wish. Due to this the choice is completely yours, if you use the standard dialogs you get what is there or you can modify these to meet your needs. The choice is completely yours. Mat Skildum Aspect Software direct: 630.227.8534 mobile: 847.909.9921 mathew.skil...@aspect.com -Original Message- From: Bruce Cran [mailto:br...@cran.org.uk] Sent: Thursday, March 24, 2011 8:40 AM To: Skildum, Mathew Cc: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Query about use of UAC shield on Install button On Thu, 24 Mar 2011 13:26:05 + Skildum, Mathew mathew.skil...@aspect.com wrote: Using the UAC shield is completely up to you not WIX. Since WIX is just the development environment, the job of following guidelines falls to the user. The WIX compiler can try to guide you down the right path, but it should not force you to do any one thing. The Button control XML has an option called ElevationShield which needs to be enabled to show the icon. It's not entirely up to the user since WiX ships with standard UIs such as WiXUI_Minimal which provides buttons with the ElevationShield property set. -- Bruce Cran -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 1923 upgrading a service
You should set Remove=Both in your service control entry. This will help in the cleanup and if any other service happens to share the same name, you remove it. Mat Skildum Aspect Software direct: 630.227.8534 mobile: 847.909.9921 mathew.skil...@aspect.com -Original Message- From: Matthew Dodkins [mailto:matthew.dodk...@gmail.com] Sent: Thursday, March 24, 2011 12:22 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Error 1923 upgrading a service When I use the word 'upgrade', I'm simply referring to running a new MSI that is installing the same service (re-installing). Does it matter if I haven't changed the version number? The verbose log doesn't seem to give much more information, it fails with 1923 on the line after Executing op: Service install. I did search up through the log from that point and didn't find any mention of an uninstall... is there something I need to do explicitly to get the installer to remove the previous version of the service first? Thanks, I appreciate the help. Matthew On Thu, Mar 24, 2011 at 4:57 PM, Chad Petersen chad.peter...@harlandfs.comwrote: Is this a major upgrade or a minor upgrade? Sounds like the uninstall of the older version might not be removing the service. Verbose log file might be helpful. You can also hit Cancel during an install to effectively pause it (then hit Resume to continue) to look at the state of the machine at certain discreet points along the way, like if the old product gets removed but new files aren't being copied yet, this can be a good point to pause the install and look in Services.msc to see the current situation. -Original Message- From: Matthew Dodkins [mailto:matthew.dodk...@gmail.com] Sent: Thursday, March 24, 2011 9:39 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Error 1923 upgrading a service Yes, it looks like this :- ServiceControl ID=StartService Name=My Service Name Start=Install Stop=Both Remove=Uninstall Wait=Yes / Thanks On Thu, Mar 24, 2011 at 3:54 PM, David Watson dwat...@sdl.com wrote: Do you have a ServiceControl element that stops the service on install? ServiceControl Name=My Service Name Stop=Both Wait=Yes ... / -Original Message- From: Matthew Dodkins [mailto:matthew.dodk...@gmail.com] Sent: 24 March 2011 10:33 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Error 1923 upgrading a service Hi there I'm having problems upgrading an existing service using my wix installer. i'm getting the 1923 error (Verify that you have sufficient privileges to install system services.). This doesn't happen the *first* time I install the service, but when I try to upgrade it. I've searched around and tried a few different things, but nothing has solved it so far. My ServiceInstall looks like this :- ServiceInstall Id=ServiceInstaller Type=ownProcess Vital=yes Name=My Service Name DisplayName=My Display Name Description=My description Start=auto Account=LocalSystem ErrorControl=ignore Interactive=no I'm logged in as a local administrator. I've tried logging in direct on the machine, not just from remote desktop. I've tried making sure the Name attribute in the ServiceInstall tag matches the service name in the service code. If I uninstall the service and run my MSI, it works fine. Any help would be greatly appreciated. Thanks! -- -- - - Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- -- -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today!
Re: [WiX-users] Get computer name??
You have to use a custom action to do what you are trying to do. For example: CustomAction Id=SetMACHINENAME Property=MACHINENAME Value=[ComputerName] / Mat Skildum -Original Message- From: kim [mailto:contactme...@gmail.com] Sent: Thursday, March 24, 2011 2:49 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Get computer name?? Following is code from my .wxs file: Code from my custom UI dialog When i execute msi, editMachineName control displays [ComputerName] instead of my machine name. Please let me know what am I doing wrong here. Thanks -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Get-computer-name-tp6205253p6205447.html Sent from the wix-users mailing list archive at Nabble.com. -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Shortcuts and Recent Programs list
Would the version of the MSI engine you are targeting play a part in what happens. If you are not targeting the 5.0 version of the engine, this may not function as expected. Mat Skildum -Original Message- From: Dick Van den Brink [mailto:d_vandenbr...@live.com] Sent: Tuesday, March 22, 2011 10:48 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Shortcuts and Recent Programs list That's weird, according to this: http://kb.flexerasoftware.com/doc/Helpnet/installshield16helplib_sp1/SettingShellShtctProp.htm and http://social.msdn.microsoft.com/Forums/en-US/winformssetup/thread/d8feae89-d5cd-44be-b21c-022a3c9a8a70 it should work. From: michael_tissing...@ciqual.com To: wix-users@lists.sourceforge.net Date: Tue, 22 Mar 2011 15:11:21 + Subject: Re: [WiX-users] Shortcuts and Recent Programs list Well I can confirm it does not cause an error on Windows XP However it does not appear to work for me on Windows 7 Name=$(var.ApplicationName) !(loc.Diagnostics) Target=[!diag] Value=1 / -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: 22 March 2011 14:34 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Shortcuts and Recent Programs list Yes, but the original question applied to Windows 7 which is MSI 5.0. --- 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: Michael Tissington To: General discussion for Windows Installer XML toolset. Sent: Tue, March 22, 2011 9:13:40 AM Subject: Re: [WiX-users] Shortcuts and Recent Programs list Hmm, WiX supports this but isn't this only supported with misexec 5.0 ? -Original Message- From: Michael Urman [mailto:mur...@gmail.com] Sent: 22 March 2011 13:56 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Shortcuts and Recent Programs list Or add a ShortcutProperty element with @Key='System.AppUserModel.ExcludeFromShowInNewInstall' and @Value='1' to your Shortcut element, assuming you're using a version of WiX that supports this element. On Tue, Mar 22, 2011 at 08:02, Pally Sandher wrote: Don't install on Windows 7? Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Michael Tissington [mailto:michael_tissing...@ciqual.com] Sent: 22 March 2011 12:35 To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] Shortcuts and Recent Programs list In my install I'm creating a number of shortcuts. They are also automatically appearing in the Start Menu list of recently opened programs. Is there a way to prevent them appearing on this list? -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- -- -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net
Re: [WiX-users] Windows 7 MSI privileges
You can also force a true Administrator check in you install (set the property MSIUSEREALADMINDETECTION) if you do not have time to work around UAC. Mat Skildum -Original Message- From: The Eligible Bachelors [mailto:theeligiblebachel...@yahoo.com] Sent: Tuesday, March 15, 2011 11:04 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Windows 7 MSI privileges This is mostly a MSI question and not too WiX specific. I am porting an old WiX (3.0) installer from XP to Windows 7. The installer needs to be run as an admin because makes several calls to external programs that need admin privileges (to register COM objects and such). Even when I am logged in as an admin, the calls to these external programs are failing and thus throwing an error at install time in my MSI. If I run an admin console and launch the MSI, these errors do not happen, since I guess I am more of an admin then. Googling around says this is a common problem in Win 7 and Vista and all the fixes seem cludgy (batch files, registry hacks). So my question is how do I get around this and why is this not a huge deal/common problem? It seems that any installer that needs admin privileges in Windows 7 has to go though hoops. Microsoft presumably has created this situation in an effort to increase security. So is there a new workflow I am supposed to be following to get the same thing done? And/or is there a known workaround for this in WiX? -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] C# Custom Action questions
In cases where you checking things like credentials you want the actions to return success so that the install does not fail. As it was said, you set a property if the call succeeded and check if the property is set. You use the other return values in those cases where you want the install to fail and not continue such as when updating configuration files or updating anything that the application requires to function. The basic rule of thumb is when in the UI sequence always have actions return success and set properties use in conditional statements. When the action is called in the Execute sequence and it is critical to the success of the product always have the action return success or failure so that the install can fail and rollback when needed. Mat Skildum -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 10, 2011 12:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions So CA's always return Success. What are the other return values used for? Thank you. For the tip. The problem that I am having now is that it doesn't appear that the CA is getting called. I look in the log and see the message indicated earlier in this thread indicating that the DLL could not be run. Any idea for this? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 10, 2011 12:03 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions You'll want to set a property that can be checked in a condition. 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 10, 2011 6:05 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions How does the custom action indicate that the credentials are incorrect? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Simon Dahlbacka [mailto:simon.dahlba...@gmail.com] Sent: Wednesday, March 09, 2011 11:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions You shouldn't return failure if the credentials are incorrect, if you do so you will get this error. been there, done that... On Mar 10, 2011 6:34 AM, Kevin Burton kev...@buyseasons.com wrote: I read that. Which of the four rules is this violating? I made the warning go away by making the C# CA 'immediate' thus I don't have to have another custom action to remember the property. So I have CustomAction Id=CA_CheckCredentials Return=check Execute=immediate BinaryKey=CustomActionsDLL DllEntry=CheckCredentials/ And the schedule InstallExecuteSequence Custom Action=CA_CheckCredentials After=InstallInitialize / /InstallExecuteSequence But in the verbose log I get: MSI (s) (B8:9C) [22:04:26:415]: Note: 1: 1723 2: CA_CheckCredentials 3: CheckCredentials 4: D:\WINDOWS\Installer\MSI410.tmp Action start 22:04:26: CA_CheckCredentials. MSI (s) (B8:9C) [22:04:26:415]: Product: Bsi WebServices -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action CA_CheckCredentials, entry: CheckCredentials, library: D:\WINDOWS\Installer\MSI410.tmp Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action CA_CheckCredentials, entry: CheckCredentials, library: D:\WINDOWS\Installer\MSI410.tmp The error says that the DLL cannot be run. Why? I believe I have followed the instructions for writing a managed CA to the tee (though there seems to be some disagreement between the online tutorial http://www.tramontana.co.hu/wix/ and this book). -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Wednesday, March 09, 2011 5:26 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions ICE63 - http://msdn.microsoft.com/en-us/library/aa369008.aspx 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: Kevin Burton
Re: [WiX-users] C# Custom Action questions
This is where you use the property that the action set. You do not allow the user off of the dialog until they enter credentials that work and the property is set to the value you expect. This way it is up to the installer to exit the install if they do not have the needed information, but you give them all the chances they need to get it right. Mat Skildum -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 10, 2011 12:38 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions But I want the install to fail. If it continues with the wrong credentials it will try to start services with the wrong credentials. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] Sent: Thursday, March 10, 2011 12:32 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions In cases where you checking things like credentials you want the actions to return success so that the install does not fail. As it was said, you set a property if the call succeeded and check if the property is set. You use the other return values in those cases where you want the install to fail and not continue such as when updating configuration files or updating anything that the application requires to function. The basic rule of thumb is when in the UI sequence always have actions return success and set properties use in conditional statements. When the action is called in the Execute sequence and it is critical to the success of the product always have the action return success or failure so that the install can fail and rollback when needed. Mat Skildum -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 10, 2011 12:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions So CA's always return Success. What are the other return values used for? Thank you. For the tip. The problem that I am having now is that it doesn't appear that the CA is getting called. I look in the log and see the message indicated earlier in this thread indicating that the DLL could not be run. Any idea for this? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, March 10, 2011 12:03 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions You'll want to set a property that can be checked in a condition. 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: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Thursday, March 10, 2011 6:05 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions How does the custom action indicate that the credentials are incorrect? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Simon Dahlbacka [mailto:simon.dahlba...@gmail.com] Sent: Wednesday, March 09, 2011 11:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] C# Custom Action questions You shouldn't return failure if the credentials are incorrect, if you do so you will get this error. been there, done that... On Mar 10, 2011 6:34 AM, Kevin Burton kev...@buyseasons.com wrote: I read that. Which of the four rules is this violating? I made the warning go away by making the C# CA 'immediate' thus I don't have to have another custom action to remember the property. So I have CustomAction Id=CA_CheckCredentials Return=check Execute=immediate BinaryKey=CustomActionsDLL DllEntry=CheckCredentials/ And the schedule InstallExecuteSequence Custom Action=CA_CheckCredentials After=InstallInitialize / /InstallExecuteSequence But in the verbose log I get: MSI (s) (B8:9C) [22:04:26:415]: Note: 1: 1723 2: CA_CheckCredentials 3: CheckCredentials 4: D:\WINDOWS\Installer\MSI410.tmp Action start 22:04:26: CA_CheckCredentials. MSI (s) (B8:9C) [22:04:26:415]: Product: Bsi WebServices -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action CA_CheckCredentials, entry: CheckCredentials, library: D:\WINDOWS\Installer\MSI410.tmp Error 1723. There is a problem with this Windows Installer package
Re: [WiX-users] msiexec redistributable
In those cases where you require a newer version of the MSI engine than what is installed, you will have to have a prerequisite installer in place to check for and install the required MSI engine. Mat Skildum Aspect Software direct: 630.227.8534 mobile: 847.909.9921 mathew.skil...@aspect.com -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, March 08, 2011 8:56 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] msiexec redistributable You don't. Its already present on all versions of Windows. -Original Message- From: Michael Tissington [mailto:michael_tissing...@ciqual.com] Sent: 08 March 2011 14:31 To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] msiexec redistributable How do I package msiexec with my wix ? - - What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Need to not use IIS 6 Scripting tools compatibility on IIS 7 machines.
Unfortunately there is a completely different set of APIs for working with IIS 7. Here is the link to the MSDN documentation on the ServerManager Namespace: http://msdn.microsoft.com/en-us/library/microsoft.web.administration.servermanager(v=vs.90).aspx Mat Skildum -Original Message- From: Uma Harano [mailto:uhar...@esri.com] Sent: Thursday, February 24, 2011 2:33 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Need to not use IIS 6 Scripting tools compatibility on IIS 7 machines. Hi, I am using WiX C # custom action template in Visual Studio 2008. The custom action I am writing is for listing all the websites on a machine and displaying it in a msi dialog. The code is very similar to what is found on this site: http://blog.torresdal.net/CommentView,guid,FE27427F-FF4F-4056-BC50-C98E23227C6D.aspx. On a windows server 2008 machine running IIS 7, I am finding that I need to turn on the IIS 6 Scripting tools feature of IIS 7 in order to get this managed custom action to display the websites. Is this expected behavior? Ideally, I would like to not use the II6 Scripting tools feature on my IIS 7 machine. I thought using managed code would help with this. Thanks! Uma -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] HOW to run the uninstallation/change as administrator from ARP panel?
For this to function you will need to make sure your install supports UAC and elevated privileges as the target OS would be Vista or higher to see this type of behavior. You need to make sure the all deferred custom actions have the value Impersonate=no set. This will force them to run at the administrator level. If you do not have this value set, all custom actions run with the logged on user privilege set and when UAC is enable this means standard user unless Run as administrator has been used. One thing to keep in mind is that immediate actions cannot be elevated, so you will need to make sure you are doing nothing outside the standard user ability in these or you will get a failure. Mat Skildum -Original Message- From: MYFLEX [mailto:shrinuen...@gmail.com] Sent: Wednesday, February 23, 2011 4:31 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] HOW to run the uninstallation/change as administrator from ARP panel? HOW to run the uninstallation/change as administrator from ARP panel? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/HOW-to-run-the-uninstallation-change-as-administrator-from-ARP-panel-tp6055847p6055847.html Sent from the wix-users mailing list archive at Nabble.com. -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
