[WiX-users] Issue in Adding reference to WixUIExtension.dll
Hi, Am trying to add reference to WixUIExtension.dll from VS 2008 I have attached the error screen shot. Kindly let me know how to proceed further Thanks and Regards Ravi -- 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_d2d_mar___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch
Still having the same problem. Tried different stuff: Changing the AssemblyFileVersion of my compiled assemblies - didn't help. Not adding new files in the patch - didn’t help. Raising the PatchFamily Version attribute between patches - I'm not sure, in consistent... Removing the Supersede='yes' - didn't help. Still having the same problem - first patch installs, all files are replaces as desired, installing the second patch doesn't overwrite the assemblies but does add new files, the second patch is shown in the add/remove updates. Please give me directions to test, I'm working on solving this for 2 weeks now... no luck, it seems random, sometimes working other times not. Thanks. -Original Message- From: Tomer Cohen [mailto:tome...@qualisystems.com] Sent: יום ה 14 מרץ 2013 08:50 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch Thanks for the prompt reply. Here is the log snippet: Machine policy value 'EnforceUpgradeComponentRules' is 0 SELMGR: New components have been added to feature 'ProductFeature' SELMGR: Component 'QsTeamServer.x86.exe.config' is a new component added to feature 'ProductFeature' SELMGR: Component 'QsTeamServer.x86.exe' is a new component added to feature 'ProductFeature' And then again later on: Machine policy value 'EnforceUpgradeComponentRules' is 0 SELMGR: New components have been added to feature 'ProductFeature' SELMGR: Component 'QsTeamServer.x86.exe.config' is a new component added to feature 'ProductFeature' SELMGR: Component 'QsTeamServer.x86.exe' is a new component added to feature 'ProductFeature' Got lots of: File: C:\Program Files\Qualisystems\TestShell Server\QS.Contracts.dll; Overwrite; Won't patch;REINSTALLMODE specifies all files to be overwritten For all the files in the patch... even though the log specifies it's gonna overwrite... it dones't. -Original Message- From: Phil Wilson [mailto:phil.wil...@mvps.org] Sent: יום ד 13 מרץ 2013 18:33 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch ...and to exapand on that, look for your files in the log. There should be a FileCopy that will say something like Won't Overwrite;Won't patch; and give you a reason. If your patch is incorrect because of component rules, look for SELMGR in the log and any remarks about removing components not supported. Phil -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, March 13, 2013 8:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch What does the action state for the *Components* show? That's what the Windows Installer is basing it's decision on. It would root cause the issue. It very likely could be the version of the files not changing but it would be best to *know* what fixed it, right? On Wed, Mar 13, 2013 at 8:18 AM, Tomer Cohen tome...@qualisystems.comwrote: Hi, Thanks for the reply. I have this in my log, this is the log of the second patch installation. The MSP itself has all assemblies, but only installs those files below. Patch Modified Files List: MSI (s) (C4:04) [15:51:46:984]: File = QualiSystems.ResourceManagement.Service.Plugin.config: Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = MRV_MCC_4640.exe: Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = MRV_MCC_4840.exe: Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = ONPATH_HorizON_0204.exe: Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = ONPATH_HorizON_0204_RuntimeConfig.xml: Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = SNMP_Manager.tslib: Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = TestShell_API.tslib: Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = ONPATH_HorizON_0244_RuntimeConfig.xml: Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = ONPATH_HorizON_0244.exe: Final State = Install I'll give the AssemblyFileVersion increment a chance. Thanks. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: יום ד 13 מרץ 2013 17:06 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch What does the verbose log file in the patch say the action states for the Components that you expect to be installed? Also, look at the File install log lines, those usually have quite a bit information about when the file is being applied and whether it is being patched. On Wed, Mar 13, 2013 at 7:19 AM, Tomer Cohen tome...@qualisystems.com wrote: Just to be clear, the files don't have a newer version, but they are different in size and binary...
[WiX-users] Question about browsedialog
Hi, i tried to build an installer using the mondo dialogs. When I start the installer the directory browse button is always disabled. I tried diferent things but I cannot enable it. could anybody tell me about the dependency? Here is my wxs source: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; Product Id=* Name=Sebam_Quantitativ Language=1033 Version=1.0.0.0 UpgradeCode=b6adaf91-47f8-4ed5-b522-6b498399cd09 Package InstallerVersion=200 Compressed=yes InstallScope=perMachine / MajorUpgrade DowngradeErrorMessage=A newer version of [ProductName] is already installed. / Media Id=1 Cabinet=sebamquantitativ.cab EmbedCab=yes / Feature Id=ProductFeature Title=Sebam Quantitativ Level=1 ComponentRef Id=MSXML3.DLL / /Feature UI / UIRef Id=WixUI_Advanced / Icon Id=DesktopIcon.exe SourceFile=Dateien\Sebam\SEBAM quantitativ\SEBAMquantitativ.exe / Icon Id=StartMenuIcon.exe SourceFile=Dateien\Sebam\SEBAM quantitativ\SEBAMquantitativ.exe / /Product Fragment Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Directory Name=Sebam Id=INSTALLDIR Component Id=MSXML3.DLL DiskId=1 Guid=18532527-38AB-458E-BA43-C7E4E0ABF9AB File Id=MSXML3.DLL Name=msxml3.dll Source=Dateien\Sebam\SEBAM quantitativ\msxml3.dll / /Component /Directory /Directory /Directory /Fragment /Wix Thanks for your help, Georg -- 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Building Wix 3.6
On 13/03/2013 20:13, jeamis wrote: So how do I enlist to the Mercurial repository? All I want to do is compile burn. I want to confirm our static analysis and debugging. Any direction is appreciated. Clone https://hg.codeplex.com/wix : hg clone https://hg.codeplex.com/wix -b wix38 To create a build that can be installed on different machines you'll need Visual Studio 2008, 2010 and 2012 along with the Visual Studio 2008, 2010 and 2012 SDKs from the Extensibility Center. You also need HTML Help SDK from http://msdn.microsoft.com/en-gb/library/windows/desktop/ms670169(v=vs.85).aspx, Sandcastle and Sandcastle Help File Builder from http://shfb.codeplex.com/ . Create a strong name keypair: sn -k wix.snk sn -p wix.snk wix.pub sn -tp wix.pub Copy the public key and add new InternalsVisibleTo lines in: src\Votive\sconce\Properties\AssemblyInfo.cs src\Votive\sdk_vs2010\common\source\csharp\project\AssemblyInfo.cs src\Votive\sdk_vs2010\common\source\csharp\project\attributes.cs Then run: msbuild /p:VisualStudioVersion=11.0 /p:OFFICIAL_WIX_BUILD=path_to_wix.snk The binaries will be put in build\debug. You should also be able to open src\Burn.sln and build the projects individually. -- Bruce Cran -- 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Building Wix 3.6
On 19/03/2013 12:31, Bruce Cran wrote: Clone https://hg.codeplex.com/wix : hg clone https://hg.codeplex.com/wix -b wix38 Sorry ignore most of that - those instructions are for WiX 3.8 not 3.6. To get 3.6 you just need to use -b wix36 when cloning and follow the instructions in the documentation. -- Bruce Cran -- 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Modify Public property from VBScript CustomAction
Hi everyone. I try to modify public property from VBScript CustomAction but without any success: CustomAction Id=ProcessPath Script=vbscript ![CDATA[ pathToProcess = Session.Property(PREVIOUS_PATH) pathToProcess = Replace(pathToProcess, /, \) Session.SetProperty PREVIOUS_PATH, pathToProcess ]] /CustomAction I tried Session[PREVIOUS_PATH] = pathToProcess but it didn't work. Is it possible to modify property values from script custom action? The real problem is legacy application saves pathes with / slashes and when installing new version Installer should copy files to directory with those slahes (from registry) or default folder. But the path C:/dir1/ is interpreted as network location and with C:\dir1\ works perfectly. SetProperty Id=FilesPath Value=[PREVIOUS_PATH] After=CostInitialize PREVIOUS_PATH/SetProperty FilePath is a Directory element. PREVIOUS_PATH is initialized with RegistrySearch element. Thank you! -- Best Wishes, Vladimir -- 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Modify Public property from VBScript CustomAction
This works for me, but I'm not doing any VBScript. CustomAction Id=myCAId Property=myPropertyName Value=myNewPropertyValue / ... InstallExecuteSequence Custom Action=myCAId After=CostInitialize /Custom /InstallExecuteSequence Alain -Original Message- From: Vladimir Yelnikov [mailto:vladimir.yelni...@gmail.com] Sent: March 19, 2013 10:59 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Modify Public property from VBScript CustomAction Hi everyone. I try to modify public property from VBScript CustomAction but without any success: CustomAction Id=ProcessPath Script=vbscript ![CDATA[ pathToProcess = Session.Property(PREVIOUS_PATH) pathToProcess = Replace(pathToProcess, /, \) Session.SetProperty PREVIOUS_PATH, pathToProcess ]] /CustomAction I tried Session[PREVIOUS_PATH] = pathToProcess but it didn't work. Is it possible to modify property values from script custom action? The real problem is legacy application saves pathes with / slashes and when installing new version Installer should copy files to directory with those slahes (from registry) or default folder. But the path C:/dir1/ is interpreted as network location and with C:\dir1\ works perfectly. SetProperty Id=FilesPath Value=[PREVIOUS_PATH] After=CostInitialize PREVIOUS_PATH/SetProperty FilePath is a Directory element. PREVIOUS_PATH is initialized with RegistrySearch element. Thank you! -- Best Wishes, Vladimir -- 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_d2d_mar ___ 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Modify Public property from VBScript CustomAction
You want: Session.Property(PREVIOUS_PATH) = pathToProcess But honestly, Script Custom Actions are very fragile. Consider C++ or C# instead. From: Vladimir Yelnikov vladimir.yelni...@gmail.com Sent: Tuesday, March 19, 2013 10:05 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Modify Public property from VBScript CustomAction Hi everyone. I try to modify public property from VBScript CustomAction but without any success: CustomAction Id=ProcessPath Script=vbscript ![CDATA[ pathToProcess = Session.Property(PREVIOUS_PATH) pathToProcess = Replace(pathToProcess, /, \) Session.SetProperty PREVIOUS_PATH, pathToProcess ]] /CustomAction I tried Session[PREVIOUS_PATH] = pathToProcess but it didn't work. Is it possible to modify property values from script custom action? The real problem is legacy application saves pathes with / slashes and when installing new version Installer should copy files to directory with those slahes (from registry) or default folder. But the path C:/dir1/ is interpreted as network location and with C:\dir1\ works perfectly. SetProperty Id=FilesPath Value=[PREVIOUS_PATH] After=CostInitialize PREVIOUS_PATH/SetProperty FilePath is a Directory element. PREVIOUS_PATH is initialized with RegistrySearch element. Thank you! -- Best Wishes, Vladimir -- 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_d2d_mar ___ 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Referencing project properties with dots
Hi, if the referenced project has a dot in its name, how can I reference its properties in the Wix files? Like $(var.My.Project.TargetDir) for My.Project reference... Thanks! Jan -- 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Referencing project properties with dots
Take a look at the build command-line. IIRC, the . is changed to _. On Tue, Mar 19, 2013 at 10:10 AM, Jan Kucera t-j...@microsoft.com wrote: Hi, if the referenced project has a dot in its name, how can I reference its properties in the Wix files? Like $(var.My.Project.TargetDir) for My.Project reference... Thanks! Jan -- 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_d2d_mar ___ 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch
What about the log search results previously referred to? For completeness:
1) The component and features state for components installing patched files
should say something about whether they are to be installed. Examples:
MSI (s) (80:58) [16:44:49:982]: Feature: Setup; Installed: Local; Request:
Reinstall; Action: Reinstall
MSI (s) (80:58) [16:44:50:001]: Component: IniFile; Installed: Local;
Request: Local; Action: Local; Client State: Local
2) Check for component guids that refer to skipping or disallowing.
Examples:
MSI (c) (FC:18) [16:44:30:270]: skipping installation of assembly component:
{6C1B1CC2-C582-4CF0-BB1C-8B725D11AF78} since the assembly already exists
MSI (c) (FC:18) [16:44:30:749]: Disallowing installation of component:
{BCCE1657-D30B-498A-9EDA-D90FD2B858C2} since the same component with higher
versioned keyfile exists
3) Look for file activitity that says it's not being installed. Example:
MSI (s) (80:58) [16:45:21:077]: File: path to file ; Won't Overwrite;
Won't patch;Existing file is of an equal version
4) I didn't mention adding files, not sure why you mentioned it, but if you
change or remove components in a patch you will see SELMGR entries in the
log.
Do the install with MSIENFORCEUPGRADECOMPONENTRULES set to find out if you
are violating component rules.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370093(v=vs.85).as
px
The reason this matters is that removing components doesn't by default tell
you that something is wrong. The patch process will go into 'advertised'
state for the affected feature and files will not be patched.
Phil
-Original Message-
From: Tomer Cohen [mailto:tome...@qualisystems.com]
Sent: Tuesday, March 19, 2013 2:48 AM
To: General discussion for Windows Installer XML toolset.
Cc: Alex Abugov
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
supersede first Patch
Still having the same problem.
Tried different stuff:
Changing the AssemblyFileVersion of my compiled assemblies - didn't help.
Not adding new files in the patch - didn’t help.
Raising the PatchFamily Version attribute between patches - I'm not sure, in
consistent...
Removing the Supersede='yes' - didn't help.
Still having the same problem - first patch installs, all files are replaces
as desired, installing the second patch doesn't overwrite the assemblies but
does add new files, the second patch is shown in the add/remove updates.
Please give me directions to test, I'm working on solving this for 2 weeks
now... no luck, it seems random, sometimes working other times not.
Thanks.
-Original Message-
From: Tomer Cohen [mailto:tome...@qualisystems.com]
Sent: יום ה 14 מרץ 2013 08:50
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
supersede first Patch
Thanks for the prompt reply.
Here is the log snippet:
Machine policy value 'EnforceUpgradeComponentRules' is 0
SELMGR: New components have been added to feature 'ProductFeature'
SELMGR: Component 'QsTeamServer.x86.exe.config' is a new component added to
feature 'ProductFeature'
SELMGR: Component 'QsTeamServer.x86.exe' is a new component added to feature
'ProductFeature'
And then again later on:
Machine policy value 'EnforceUpgradeComponentRules' is 0
SELMGR: New components have been added to feature 'ProductFeature'
SELMGR: Component 'QsTeamServer.x86.exe.config' is a new component added to
feature 'ProductFeature'
SELMGR: Component 'QsTeamServer.x86.exe' is a new component added to feature
'ProductFeature'
Got lots of:
File: C:\Program Files\Qualisystems\TestShell Server\QS.Contracts.dll;
Overwrite; Won't patch;REINSTALLMODE specifies all files to be
overwritten
For all the files in the patch... even though the log specifies it's gonna
overwrite... it dones't.
-Original Message-
From: Phil Wilson [mailto:phil.wil...@mvps.org]
Sent: יום ד 13 מרץ 2013 18:33
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
supersede first Patch
...and to exapand on that, look for your files in the log. There should be a
FileCopy that will say something like Won't Overwrite;Won't patch;
and give you a reason.
If your patch is incorrect because of component rules, look for SELMGR in
the log and any remarks about removing components not supported.
Phil
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, March 13, 2013 8:24 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
supersede first Patch
What does the action state for the *Components* show? That's what the
Windows Installer is basing it's decision on. It would root cause the issue.
It very likely could be the version of the files not changing but it would
be best to *know* what fixed it, right?
On Wed, Mar 13,
Re: [WiX-users] Referencing project properties with dots
Okay, works as expected, sorry. It was picking the same path for two referenced projects with different names. Which I still believe should duplicate the properties anyway... Jan -Original Message- From: Jan Kucera [mailto:t-j...@microsoft.com] Sent: 19 March 2013 17:10 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Referencing project properties with dots Hi, if the referenced project has a dot in its name, how can I reference its properties in the Wix files? Like $(var.My.Project.TargetDir) for My.Project reference... Thanks! Jan -- 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_d2d_mar ___ 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Bundle install on Windows XP 32-bit
When I run my exe install on a Windows XP machine the bundle will launch itself after the install. So when the install completes I have two windows, one says close and the other has repair, uninstall and close This does not happen on Vista, Win7 or 8 Thank you, Michael Ogilvie -- 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bundle install on Windows XP 32-bit
What does the log file show? On Tue, Mar 19, 2013 at 11:49 AM, Michael Ogilvie michael.ogil...@pixelink.com wrote: When I run my exe install on a Windows XP machine the bundle will launch itself after the install. So when the install completes I have two windows, one says close and the other has repair, uninstall and close This does not happen on Vista, Win7 or 8 Thank you, Michael Ogilvie -- 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_d2d_mar ___ 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bundle install on Windows XP 32-bit
Nothing interesting in the logs.
Bundle1:
[0FBC:0498][2013-03-19T16:18:37]i001: Burn v3.7.1224.0, Windows v5.1 (Build
2600: Service Pack 3), path: C:\Documents and
Settings\mogilvie\Desktop\Camera_Kit.exe, cmdline: ''
[0FBC:0498][2013-03-19T16:18:37]i000: Initializing string variable
'InstallFolder' to value '[ProgramFilesFolder]PixeLINK'
[0FBC:0498][2013-03-19T16:18:37]i000: Initializing numeric variable
'MyCheckbox1' to value '1'
[0FBC:0498][2013-03-19T16:18:37]i000: Setting string variable 'WixBundleLog' to
value
'C:\DOCUME~1\mogilvie\LOCALS~1\Temp\PixeLINK_Camera_Kit_20130319161837.log'
[0FBC:0498][2013-03-19T16:18:37]i000: Setting string variable
'WixBundleOriginalSource' to value 'C:\Documents and
Settings\mogilvie\Desktop\Camera_Kit.exe'
[0FBC:0498][2013-03-19T16:18:37]i052: Condition 'VersionNT = v5.01' evaluates
to true.
[0FBC:0498][2013-03-19T16:18:37]i000: Setting string variable 'WixBundleName'
to value 'PixeLINK Camera Kit'
[0FBC:0498][2013-03-19T16:18:37]i100: Detect begin, 4 packages
[0FBC:0498][2013-03-19T16:18:37]i000: Setting numeric variable 'Netfx20Version'
to value 1
[0FBC:0498][2013-03-19T16:18:37]i000: Update location:
http://www.files.pixelink.com/update/Capture/index.php?version=8.7.0.0.
[0FBC:0D0C][2013-03-19T16:18:37]i000: Checking for update.
[0FBC:0498][2013-03-19T16:18:37]i052: Condition 'Netfx20Version AND
(Netfx20Version = v2.0.50727.5420)' evaluates to false.
[0FBC:0498][2013-03-19T16:18:37]w120: Detected partially cached package:
CameraKit, invalid payload: CameraKit, reason: 0x80070570
[0FBC:0498][2013-03-19T16:18:37]i101: Detected package: Netfx20, state: Absent,
cached: None
[0FBC:0498][2013-03-19T16:18:37]i101: Detected package: CameraKit, state:
Absent, cached: Partial
[0FBC:0498][2013-03-19T16:18:37]i101: Detected package: driver1, state: Absent,
cached: Complete
[0FBC:0498][2013-03-19T16:18:37]i101: Detected package: driver2, state: Absent,
cached: None
[0FBC:0498][2013-03-19T16:18:37]i199: Detect complete, result: 0x0
[0FBC:0D0C][2013-03-19T16:18:38]i000: No update available.
[0FBC:0A6C][2013-03-19T16:18:39]i000: Setting numeric variable
'EulaAcceptCheckbox' to value 1
[0FBC:0498][2013-03-19T16:18:39]i200: Plan begin, 4 packages, action: Install
[0FBC:0498][2013-03-19T16:18:39]i052: Condition 'NOT Netfx20Version OR
(Netfx20Version v2.0.50727.5420)' evaluates to false.
[0FBC:0498][2013-03-19T16:18:39]w321: Skipping dependency registration on
package with no dependency providers: Netfx20
[0FBC:0498][2013-03-19T16:18:39]i000: Setting string variable
'WixBundleRollbackLog_CameraKit' to value
'C:\DOCUME~1\mogilvie\LOCALS~1\Temp\PixeLINK_Camera_Kit_20130319161837_0_CameraKit_rollback.log'
[0FBC:0498][2013-03-19T16:18:39]i000: Setting string variable
'WixBundleLog_CameraKit' to value
'C:\DOCUME~1\mogilvie\LOCALS~1\Temp\PixeLINK_Camera_Kit_20130319161837_0_CameraKit.log'
[0FBC:0498][2013-03-19T16:18:39]i052: Condition 'Not VersionNT64' evaluates to
true.
[0FBC:0498][2013-03-19T16:18:39]i000: Setting string variable
'WixBundleRollbackLog_driver1' to value
'C:\DOCUME~1\mogilvie\LOCALS~1\Temp\PixeLINK_Camera_Kit_20130319161837_1_driver1_rollback.log'
[0FBC:0498][2013-03-19T16:18:39]i000: Setting string variable
'WixBundleLog_driver1' to value
'C:\DOCUME~1\mogilvie\LOCALS~1\Temp\PixeLINK_Camera_Kit_20130319161837_1_driver1.log'
[0FBC:0498][2013-03-19T16:18:39]i052: Condition 'VersionNT64' evaluates to
false.
[0FBC:0498][2013-03-19T16:18:39]i201: Planned package: Netfx20, state: Absent,
default requested: Absent, ba requested: Absent, execute: None, rollback: None,
cache: No, uncache: No, dependency: None
[0FBC:0498][2013-03-19T16:18:39]i201: Planned package: CameraKit, state:
Absent, default requested: Present, ba requested: Present, execute: Install,
rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[0FBC:0498][2013-03-19T16:18:39]i201: Planned package: driver1, state: Absent,
default requested: Present, ba requested: Present, execute: Install, rollback:
Uninstall, cache: No, uncache: No, dependency: Register
[0FBC:0498][2013-03-19T16:18:39]i201: Planned package: driver2, state: Absent,
default requested: Absent, ba requested: Absent, execute: None, rollback: None,
cache: No, uncache: No, dependency: None
[0FBC:0498][2013-03-19T16:18:39]i299: Plan complete, result: 0x0
[0FBC:0498][2013-03-19T16:18:39]i300: Apply begin
[0FDC:020C][2013-03-19T16:18:39]i360: Creating a system restore point.
[0FDC:020C][2013-03-19T16:18:42]i361: Created a system restore point.
[0FDC:020C][2013-03-19T16:18:42]i000: Caching bundle from:
'C:\DOCUME~1\mogilvie\LOCALS~1\Temp\{c8bf0f56-0e51-4e58-8661-74b72e39feca}\.be\Camera_Kit.exe'
to: 'C:\Documents and Settings\All Users\Application Data\Package
Cache\{c8bf0f56-0e51-4e58-8661-74b72e39feca}\Camera_Kit.exe'
[0FDC:020C][2013-03-19T16:18:42]i320: Registering bundle dependency provider:
{c8bf0f56-0e51-4e58-8661-74b72e39feca}, version: 8.7.0.0
[0FDC:0C48][2013-03-19T16:18:42]i305: Verified
[WiX-users] Uninstall
Why would some files be left after the uninstall?? Thank you, Michael Ogilvie Application Support Specialist | PixeLINK 1900 City Park Drive, Suite 410. Ottawa, Ontario K1J 1A3 tel: 613.247.1211 Ext. 242 | cell: 613.302.9844 | fax: 613.247.2001 | skype: pixelink.mogilvie skype://pixelink.mogilvie/?call www.pixelink.com blocked::http://www.pixelink.com/ -- 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall
Many reasons, one of which is because they were created by the application as it was running on the client machine, and weren't a part of the original installation package. We'd need more details to help much more. Alain -Original Message- From: Michael Ogilvie [mailto:michael.ogil...@pixelink.com] Sent: March 19, 2013 15:58 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Uninstall Why would some files be left after the uninstall?? Thank you, Michael Ogilvie Application Support Specialist | PixeLINK 1900 City Park Drive, Suite 410. Ottawa, Ontario K1J 1A3 tel: 613.247.1211 Ext. 242 | cell: 613.302.9844 | fax: 613.247.2001 | skype: pixelink.mogilvie skype://pixelink.mogilvie/?call www.pixelink.com blocked::http://www.pixelink.com/ -- 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_d2d_mar ___ 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Translated shortcuts only in one msi
Hi, I have been asked to create a setup msi that has the workflow explained below: The setup will install the help resources for 14 languages (without using msts, just one msi file). One of the dialogs in the setup will ask the user to select a language in a drop down list box. If the user selects Italian (for example), the shortcut to help will be created in the Program menu pointing to the Italian help installed on the machine. The name of the shortcut will be translated in Italian. I plan to do this by having 14 components (that contain only the help shortcut) in the setup which get installed based on the user input. Is it possible to do this? Note, some of the 14 languages installed will not be code page 1252. SO not sure if I can do this without using msts. Is it possible to have one msi file contain Arabic, Japanese, Chinese, and other strings? Thanks! Uma- -- 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall
I remove all files then do a fresh clean install of the bundle and then a uninstall of the bundle and some of the files are left. This only happens on Windows XP, Windows 8 cleans up everything Thank you, Michael Ogilvie -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: Tuesday, March 19, 2013 4:01 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Uninstall Many reasons, one of which is because they were created by the application as it was running on the client machine, and weren't a part of the original installation package. We'd need more details to help much more. Alain -Original Message- From: Michael Ogilvie [mailto:michael.ogil...@pixelink.com] Sent: March 19, 2013 15:58 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Uninstall Why would some files be left after the uninstall?? Thank you, Michael Ogilvie Application Support Specialist | PixeLINK 1900 City Park Drive, Suite 410. Ottawa, Ontario K1J 1A3 tel: 613.247.1211 Ext. 242 | cell: 613.302.9844 | fax: 613.247.2001 | skype: pixelink.mogilvie skype://pixelink.mogilvie/?call www.pixelink.com blocked::http://www.pixelink.com/ -- 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_d2d_mar ___ 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_d2d_mar ___ 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall
Are unique Guids set for each installed file, particularly the ones that aren't being uninstalled? That might not explain why it works on one OS and not another though. Alain -Original Message- From: Michael Ogilvie [mailto:michael.ogil...@pixelink.com] Sent: March 19, 2013 16:17 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] Uninstall I remove all files then do a fresh clean install of the bundle and then a uninstall of the bundle and some of the files are left. This only happens on Windows XP, Windows 8 cleans up everything Thank you, Michael Ogilvie -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: Tuesday, March 19, 2013 4:01 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Uninstall Many reasons, one of which is because they were created by the application as it was running on the client machine, and weren't a part of the original installation package. We'd need more details to help much more. Alain -Original Message- From: Michael Ogilvie [mailto:michael.ogil...@pixelink.com] Sent: March 19, 2013 15:58 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Uninstall Why would some files be left after the uninstall?? Thank you, Michael Ogilvie Application Support Specialist | PixeLINK 1900 City Park Drive, Suite 410. Ottawa, Ontario K1J 1A3 tel: 613.247.1211 Ext. 242 | cell: 613.302.9844 | fax: 613.247.2001 | skype: pixelink.mogilvie skype://pixelink.mogilvie/?call www.pixelink.com blocked::http://www.pixelink.com/ -- 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_d2d_mar ___ 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_d2d_mar ___ 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall
Thought of that, I created new GUID for those components and tried the install again. Still an issue on Windows XP WIX 3.6 and 3.7 Thank you, Michael Ogilvie Application Support Specialist | PixeLINK 1900 City Park Drive, Suite 410. Ottawa, Ontario K1J 1A3 tel: 613.247.1211 Ext. 242 | cell: 613.302.9844 | fax: 613.247.2001 | skype: pixelink.mogilvie www.pixelink.com -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: Tuesday, March 19, 2013 4:20 PM To: Michael Ogilvie; 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] Uninstall Are unique Guids set for each installed file, particularly the ones that aren't being uninstalled? That might not explain why it works on one OS and not another though. Alain -Original Message- From: Michael Ogilvie [mailto:michael.ogil...@pixelink.com] Sent: March 19, 2013 16:17 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] Uninstall I remove all files then do a fresh clean install of the bundle and then a uninstall of the bundle and some of the files are left. This only happens on Windows XP, Windows 8 cleans up everything Thank you, Michael Ogilvie -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: Tuesday, March 19, 2013 4:01 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Uninstall Many reasons, one of which is because they were created by the application as it was running on the client machine, and weren't a part of the original installation package. We'd need more details to help much more. Alain -Original Message- From: Michael Ogilvie [mailto:michael.ogil...@pixelink.com] Sent: March 19, 2013 15:58 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Uninstall Why would some files be left after the uninstall?? Thank you, Michael Ogilvie Application Support Specialist | PixeLINK 1900 City Park Drive, Suite 410. Ottawa, Ontario K1J 1A3 tel: 613.247.1211 Ext. 242 | cell: 613.302.9844 | fax: 613.247.2001 | skype: pixelink.mogilvie skype://pixelink.mogilvie/?call www.pixelink.com blocked::http://www.pixelink.com/ -- 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_d2d_mar ___ 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_d2d_mar ___ 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bundle install on Windows XP 32-bit
This does not seem to happen with Wix 3.6 only 3.7 Thank you, -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Tuesday, March 19, 2013 3:13 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bundle install on Windows XP 32-bit What does the log file show? On Tue, Mar 19, 2013 at 11:49 AM, Michael Ogilvie michael.ogil...@pixelink.com wrote: When I run my exe install on a Windows XP machine the bundle will launch itself after the install. So when the install completes I have two windows, one says close and the other has repair, uninstall and close This does not happen on Vista, Win7 or 8 Thank you, Michael Ogilvie -- 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_d2d_mar ___ 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_d2d_mar ___ 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] COM+ registration help
Hi Rob - Your 'nothing' is probably more than my nothing on this topic, so thanks in advance for any assistance and insight you can provide. Here's the relevant log segment: ** ComPlusInstallExecuteCommit: Entering ComPlusInstallExecuteCommit in C:\WINDOWS\Installer\MSI29.tmp, version 3.7.1224.0 MSI (s) (E0!50) [11:17:57:286]: Closing MSIHANDLE (859) of type 790531 for thread 3920 MSI (s) (E0!50) [11:17:57:286]: Creating MSIHANDLE (860) of type 790531 for thread 3920 MSI (s) (E0!50) [11:17:57:286]: Closing MSIHANDLE (860) of type 790531 for thread 3920 MSI (s) (E0!50) [11:17:57:426]: Creating MSIHANDLE (861) of type 790531 for thread 3920 MSI (s) (E0!50) [11:17:57:426]: Closing MSIHANDLE (861) of type 790531 for thread 3920 MSI (s) (E0!50) [11:17:57:426]: Creating MSIHANDLE (862) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: Registering assembly, key: myApp MSI (s) (E0!50) [11:17:57:426]: Closing MSIHANDLE (862) of type 790531 for thread 3920 MSI (s) (E0!50) [11:18:01:708]: Creating MSIHANDLE (863) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: ExceptionInfo: Code='0', Source='System.EnterpriseServices', Description='Failed to load assembly 'c:\program files (x86)\MyCompany\queue\13.0\vmsqueue.dll'.', HelpFile='', HelpContext='0' MSI (s) (E0!50) [11:18:01:708]: Closing MSIHANDLE (863) of type 790531 for thread 3920 MSI (s) (E0!50) [11:18:01:708]: Creating MSIHANDLE (864) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: Error 0x80020009: Failed to invoke RegistrationHelper.InstallAssembly() method MSI (s) (E0!50) [11:18:01:708]: Closing MSIHANDLE (864) of type 790531 for thread 3920 MSI (s) (E0!50) [11:18:01:708]: Creating MSIHANDLE (865) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: Error 0x80020009: Failed to register .NET assembly MSI (s) (E0!50) [11:18:01:708]: Closing MSIHANDLE (865) of type 790531 for thread 3920 MSI (s) (E0!50) [11:18:01:708]: Creating MSIHANDLE (866) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: Error 0x80020009: Failed to register assembly, key: myApp MSI (s) (E0!50) [11:18:01:708]: Closing MSIHANDLE (866) of type 790531 for thread 3920 MSI (s) (E0!50) [11:18:01:708]: Creating MSIHANDLE (867) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: Error 0x80020009: Failed to register assemblies MSI (s) (E0!50) [11:18:01:708]: Closing MSIHANDLE (867) of type 790531 for thread 3920 MSI (s) (E0:20) [11:18:01:708]: Closing MSIHANDLE (858) of type 790536 for thread 3360 ** Doesn't seem very helpful ... but that's what I've got ... If the assembly is re-based to target Framework v2 [2.0.50727, to be precise] ... then it installs just fine ... There is some uninstallation weirdness [but only on 1 system, not on a clean test box] - when uninstalling, the app remains in the Component Services control panel applet ... the installed files and folders [and ARP entry] get removed properly ... weird, huh? We're trying to move all of our code to Framework v4 ... so this is kind of a pain ... and as I've said already, any assistance / insights are greatly appreciated. Thanks, -dmm -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/COM-registration-help-tp7584402p7584465.html Sent from the wix-users mailing list archive at Nabble.com. -- 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] COM+ registration help
Does the .NET 4.0 component install to COM+ ok if you do it manually? -Original Message- From: DexterSinister [mailto:dma...@nt4hire.com] Sent: 19 March 2013 20:34 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] COM+ registration help Hi Rob - Your 'nothing' is probably more than my nothing on this topic, so thanks in advance for any assistance and insight you can provide. Here's the relevant log segment: ** ComPlusInstallExecuteCommit: Entering ComPlusInstallExecuteCommit in C:\WINDOWS\Installer\MSI29.tmp, version 3.7.1224.0 MSI (s) (E0!50) [11:17:57:286]: Closing MSIHANDLE (859) of type 790531 for thread 3920 MSI (s) (E0!50) [11:17:57:286]: Creating MSIHANDLE (860) of type 790531 for thread 3920 MSI (s) (E0!50) [11:17:57:286]: Closing MSIHANDLE (860) of type 790531 for thread 3920 MSI (s) (E0!50) [11:17:57:426]: Creating MSIHANDLE (861) of type 790531 for thread 3920 MSI (s) (E0!50) [11:17:57:426]: Closing MSIHANDLE (861) of type 790531 for thread 3920 MSI (s) (E0!50) [11:17:57:426]: Creating MSIHANDLE (862) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: Registering assembly, key: myApp MSI (s) (E0!50) [11:17:57:426]: Closing MSIHANDLE (862) of type 790531 for thread 3920 MSI (s) (E0!50) [11:18:01:708]: Creating MSIHANDLE (863) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: ExceptionInfo: Code='0', Source='System.EnterpriseServices', Description='Failed to load assembly 'c:\program files (x86)\MyCompany\queue\13.0\vmsqueue.dll'.', HelpFile='', HelpContext='0' MSI (s) (E0!50) [11:18:01:708]: Closing MSIHANDLE (863) of type 790531 for thread 3920 MSI (s) (E0!50) [11:18:01:708]: Creating MSIHANDLE (864) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: Error 0x80020009: Failed to invoke RegistrationHelper.InstallAssembly() method MSI (s) (E0!50) [11:18:01:708]: Closing MSIHANDLE (864) of type 790531 for thread 3920 MSI (s) (E0!50) [11:18:01:708]: Creating MSIHANDLE (865) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: Error 0x80020009: Failed to register .NET assembly MSI (s) (E0!50) [11:18:01:708]: Closing MSIHANDLE (865) of type 790531 for thread 3920 MSI (s) (E0!50) [11:18:01:708]: Creating MSIHANDLE (866) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: Error 0x80020009: Failed to register assembly, key: myApp MSI (s) (E0!50) [11:18:01:708]: Closing MSIHANDLE (866) of type 790531 for thread 3920 MSI (s) (E0!50) [11:18:01:708]: Creating MSIHANDLE (867) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: Error 0x80020009: Failed to register assemblies MSI (s) (E0!50) [11:18:01:708]: Closing MSIHANDLE (867) of type 790531 for thread 3920 MSI (s) (E0:20) [11:18:01:708]: Closing MSIHANDLE (858) of type 790536 for thread 3360 ** Doesn't seem very helpful ... but that's what I've got ... If the assembly is re-based to target Framework v2 [2.0.50727, to be precise] ... then it installs just fine ... There is some uninstallation weirdness [but only on 1 system, not on a clean test box] - when uninstalling, the app remains in the Component Services control panel applet ... the installed files and folders [and ARP entry] get removed properly ... weird, huh? We're trying to move all of our code to Framework v4 ... so this is kind of a pain ... and as I've said already, any assistance / insights are greatly appreciated. Thanks, -dmm -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/COM-registration-help-tp7584402p7584465.html Sent from the wix-users mailing list archive at Nabble.com. -- 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_d2d_mar ___ 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall
The file paths may be in the SharedDlls registry entries, HKLM\Software\Microsoft\CurrentVersion\SharedDlls. If you ever marked them shared or permanent and installed them, then they are stuck on the system. Changing the guid won't help if they're permanently on the system under another guid, or in SharedDlls. This is a common issue on dev systems used for testing (which should be done on VMs), and sometimes a misunderstanding of how these things work. Setting Permanent or Shared is not a nifty project setting that can be turned on and off. It is a system state as soon as a component/file is installed with these settings. A log might tell you more, maybe disallowing uninstall of file because another client exists, that kind of text. Phil -Original Message- From: Michael Ogilvie [mailto:michael.ogil...@pixelink.com] Sent: Tuesday, March 19, 2013 1:30 PM To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall Thought of that, I created new GUID for those components and tried the install again. Still an issue on Windows XP WIX 3.6 and 3.7ntries in the registry, Thank you, Michael Ogilvie Application Support Specialist | PixeLINK 1900 City Park Drive, Suite 410. Ottawa, Ontario K1J 1A3 tel: 613.247.1211 Ext. 242 | cell: 613.302.9844 | fax: 613.247.2001 | skype: pixelink.mogilvie www.pixelink.com -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: Tuesday, March 19, 2013 4:20 PM To: Michael Ogilvie; 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] Uninstall Are unique Guids set for each installed file, particularly the ones that aren't being uninstalled? That might not explain why it works on one OS and not another though. Alain -Original Message- From: Michael Ogilvie [mailto:michael.ogil...@pixelink.com] Sent: March 19, 2013 16:17 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] Uninstall I remove all files then do a fresh clean install of the bundle and then a uninstall of the bundle and some of the files are left. This only happens on Windows XP, Windows 8 cleans up everything Thank you, Michael Ogilvie -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: Tuesday, March 19, 2013 4:01 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Uninstall Many reasons, one of which is because they were created by the application as it was running on the client machine, and weren't a part of the original installation package. We'd need more details to help much more. Alain -Original Message- From: Michael Ogilvie [mailto:michael.ogil...@pixelink.com] Sent: March 19, 2013 15:58 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Uninstall Why would some files be left after the uninstall?? Thank you, Michael Ogilvie Application Support Specialist | PixeLINK 1900 City Park Drive, Suite 410. Ottawa, Ontario K1J 1A3 tel: 613.247.1211 Ext. 242 | cell: 613.302.9844 | fax: 613.247.2001 | skype: pixelink.mogilvie skype://pixelink.mogilvie/?call www.pixelink.com blocked::http://www.pixelink.com/ -- 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_d2d_mar ___ 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_d2d_mar ___ 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_d2d_mar ___ 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] COM+ registration help
It is entirely possible the COM+ CustomAction has not been updated to handle NETFX 4.0. I don't even know if that statement makes sense but the custom action was written so long ago, there may be something about NETFX 4.0 that isn't handled correctly. Someone could look at the code... On Tue, Mar 19, 2013 at 2:26 PM, Neil Sleightholm n...@x2systems.comwrote: Does the .NET 4.0 component install to COM+ ok if you do it manually? -Original Message- From: DexterSinister [mailto:dma...@nt4hire.com] Sent: 19 March 2013 20:34 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] COM+ registration help Hi Rob - Your 'nothing' is probably more than my nothing on this topic, so thanks in advance for any assistance and insight you can provide. Here's the relevant log segment: ** ComPlusInstallExecuteCommit: Entering ComPlusInstallExecuteCommit in C:\WINDOWS\Installer\MSI29.tmp, version 3.7.1224.0 MSI (s) (E0!50) [11:17:57:286]: Closing MSIHANDLE (859) of type 790531 for thread 3920 MSI (s) (E0!50) [11:17:57:286]: Creating MSIHANDLE (860) of type 790531 for thread 3920 MSI (s) (E0!50) [11:17:57:286]: Closing MSIHANDLE (860) of type 790531 for thread 3920 MSI (s) (E0!50) [11:17:57:426]: Creating MSIHANDLE (861) of type 790531 for thread 3920 MSI (s) (E0!50) [11:17:57:426]: Closing MSIHANDLE (861) of type 790531 for thread 3920 MSI (s) (E0!50) [11:17:57:426]: Creating MSIHANDLE (862) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: Registering assembly, key: myApp MSI (s) (E0!50) [11:17:57:426]: Closing MSIHANDLE (862) of type 790531 for thread 3920 MSI (s) (E0!50) [11:18:01:708]: Creating MSIHANDLE (863) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: ExceptionInfo: Code='0', Source='System.EnterpriseServices', Description='Failed to load assembly 'c:\program files (x86)\MyCompany\queue\13.0\vmsqueue.dll'.', HelpFile='', HelpContext='0' MSI (s) (E0!50) [11:18:01:708]: Closing MSIHANDLE (863) of type 790531 for thread 3920 MSI (s) (E0!50) [11:18:01:708]: Creating MSIHANDLE (864) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: Error 0x80020009: Failed to invoke RegistrationHelper.InstallAssembly() method MSI (s) (E0!50) [11:18:01:708]: Closing MSIHANDLE (864) of type 790531 for thread 3920 MSI (s) (E0!50) [11:18:01:708]: Creating MSIHANDLE (865) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: Error 0x80020009: Failed to register .NET assembly MSI (s) (E0!50) [11:18:01:708]: Closing MSIHANDLE (865) of type 790531 for thread 3920 MSI (s) (E0!50) [11:18:01:708]: Creating MSIHANDLE (866) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: Error 0x80020009: Failed to register assembly, key: myApp MSI (s) (E0!50) [11:18:01:708]: Closing MSIHANDLE (866) of type 790531 for thread 3920 MSI (s) (E0!50) [11:18:01:708]: Creating MSIHANDLE (867) of type 790531 for thread 3920 ComPlusInstallExecuteCommit: Error 0x80020009: Failed to register assemblies MSI (s) (E0!50) [11:18:01:708]: Closing MSIHANDLE (867) of type 790531 for thread 3920 MSI (s) (E0:20) [11:18:01:708]: Closing MSIHANDLE (858) of type 790536 for thread 3360 ** Doesn't seem very helpful ... but that's what I've got ... If the assembly is re-based to target Framework v2 [2.0.50727, to be precise] ... then it installs just fine ... There is some uninstallation weirdness [but only on 1 system, not on a clean test box] - when uninstalling, the app remains in the Component Services control panel applet ... the installed files and folders [and ARP entry] get removed properly ... weird, huh? We're trying to move all of our code to Framework v4 ... so this is kind of a pain ... and as I've said already, any assistance / insights are greatly appreciated. Thanks, -dmm -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/COM-registration-help-tp7584402p7584465.html Sent from the wix-users mailing list archive at Nabble.com. -- 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_d2d_mar ___ 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_d2d_mar ___ 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
Re: [WiX-users] Translated shortcuts only in one msi
Unfortunately, no. The MSI can only have one codepage, although a transform can change the codepage. On Tue, Mar 19, 2013 at 12:46 PM, Uma Harano uhar...@esri.com wrote: Hi, I have been asked to create a setup msi that has the workflow explained below: The setup will install the help resources for 14 languages (without using msts, just one msi file). One of the dialogs in the setup will ask the user to select a language in a drop down list box. If the user selects Italian (for example), the shortcut to help will be created in the Program menu pointing to the Italian help installed on the machine. The name of the shortcut will be translated in Italian. I plan to do this by having 14 components (that contain only the help shortcut) in the setup which get installed based on the user input. Is it possible to do this? Note, some of the 14 languages installed will not be code page 1252. SO not sure if I can do this without using msts. Is it possible to have one msi file contain Arabic, Japanese, Chinese, and other strings? Thanks! Uma- -- 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_d2d_mar ___ 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_d2d_mar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Uninstall
A verbose log file should tell all. On Tue, Mar 19, 2013 at 2:34 PM, Phil Wilson phil.wil...@mvps.org wrote: The file paths may be in the SharedDlls registry entries, HKLM\Software\Microsoft\CurrentVersion\SharedDlls. If you ever marked them shared or permanent and installed them, then they are stuck on the system. Changing the guid won't help if they're permanently on the system under another guid, or in SharedDlls. This is a common issue on dev systems used for testing (which should be done on VMs), and sometimes a misunderstanding of how these things work. Setting Permanent or Shared is not a nifty project setting that can be turned on and off. It is a system state as soon as a component/file is installed with these settings. A log might tell you more, maybe disallowing uninstall of file because another client exists, that kind of text. Phil -Original Message- From: Michael Ogilvie [mailto:michael.ogil...@pixelink.com] Sent: Tuesday, March 19, 2013 1:30 PM To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Uninstall Thought of that, I created new GUID for those components and tried the install again. Still an issue on Windows XP WIX 3.6 and 3.7ntries in the registry, Thank you, Michael Ogilvie Application Support Specialist | PixeLINK 1900 City Park Drive, Suite 410. Ottawa, Ontario K1J 1A3 tel: 613.247.1211 Ext. 242 | cell: 613.302.9844 | fax: 613.247.2001 | skype: pixelink.mogilvie www.pixelink.com -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: Tuesday, March 19, 2013 4:20 PM To: Michael Ogilvie; 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] Uninstall Are unique Guids set for each installed file, particularly the ones that aren't being uninstalled? That might not explain why it works on one OS and not another though. Alain -Original Message- From: Michael Ogilvie [mailto:michael.ogil...@pixelink.com] Sent: March 19, 2013 16:17 To: afor...@cmu.edu; General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] Uninstall I remove all files then do a fresh clean install of the bundle and then a uninstall of the bundle and some of the files are left. This only happens on Windows XP, Windows 8 cleans up everything Thank you, Michael Ogilvie -Original Message- From: Alain Forget [mailto:afor...@cmu.edu] Sent: Tuesday, March 19, 2013 4:01 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Uninstall Many reasons, one of which is because they were created by the application as it was running on the client machine, and weren't a part of the original installation package. We'd need more details to help much more. Alain -Original Message- From: Michael Ogilvie [mailto:michael.ogil...@pixelink.com] Sent: March 19, 2013 15:58 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Uninstall Why would some files be left after the uninstall?? Thank you, Michael Ogilvie Application Support Specialist | PixeLINK 1900 City Park Drive, Suite 410. Ottawa, Ontario K1J 1A3 tel: 613.247.1211 Ext. 242 | cell: 613.302.9844 | fax: 613.247.2001 | skype: pixelink.mogilvie skype://pixelink.mogilvie/?call www.pixelink.com blocked::http://www.pixelink.com/ -- 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_d2d_mar ___ 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_d2d_mar ___ 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_d2d_mar ___ 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_d2d_mar ___ WiX-users mailing list
