Re: [WiX-users] Installed: Local; Request: Absent; Action: Null ?
Arnette, Bill wrote: Non-Windows Installer installers use the SharedDlls registry key to refcount the usage of common/shared dlls. By default Windows Installer will only increment that refcount if it already exists so that the other installer will track the refcount properly if a WI installer installs the same file. Windows Installer also maintains its own refcount for components it tracks elsewhere. You can force Windows Installer to create a SharedDLLs entry if it doesn't already exist with the msidbComponentAttributesSharedDllRefCount attribute on a component. So this is what the SharedDllRefCount='yes' attribute means... Let me try to get the consequences for me straight: if I have an old installer using the SharedDll mechanism and new installers are msi based (and will stay so for the forseeable future) I would not have to explicitly use SharedDllRefCount='yes' and it'd still work if I install my newer version in parallel (yes, we do that...) to the older version and I could deinstall in arbitrary order. It would not work, however, if I installed the new version first and than the older one in parallel. But as that's not a scenario I need to support, I'd be ok without using the SharedDllRefCount='yes' attribute. Did I get that right? So what that log indicates is that a non-WI installer installed that file before your product was installed and that since the SharedDlls refcount will not go to 0 after your product is uninstalled, the file will not be removed so that the other product is not broken. Ok, that's probably exactly what happens as I have an older version installed (or at least not fully uninstalled) Thanks for the explanation, Andre' - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix and Drivers
After checking all what I can get it seems I have to use custom action now to proceed. Is that a correct assumption? So is the order then: 1) install the driver files in the Driver Store 2) calling a custom action to install the printer? the way to go or do I have overseen something in Wix? Regards Friedrich - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Setting (Default) value for registry key
Hi.
I have a problem and i hope somebody can help me.
I need to register .NET assembly for COM during installation. So i use heat
to produce a valid code. Here is an example:
Component Id=Lib.dll Guid=PUT-GUID-HERE
Class Id={83602D89-19ED-377D-BCFA-07DEC0826D15}
Context=InprocServer32 Description=Lib.frmAdmin ThreadingModel=both
ProgId Id=Lib.frmAdmin Description=Lib.frmAdmin /
/Class
File Id=Lib.dll Name=AdminInquiryLib.dll KeyPath=yes
Source=C:\blah\blah\blah\Lib.dll /
ProgId Id=Record /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32\2.0.0.0
Name=Class Value=Lib.frmAdmin Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32\2.0.0.0
Name=Assembly Value=Lib, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=f57227384aa6f133 Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32\2.0.0.0
Name=RuntimeVersion Value=v2.0.50727 Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32\2.0.0.0
Name=CodeBase Value=[#Lib.dll] Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32 Value=
mscoree.dll Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32
Name=Class Value=Lib.frmAdmin Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32
Name=Assembly Value=Lib, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=f57227384aa6f133 Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32
Name=RuntimeVersion Value=v2.0.50727 Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32
Name=CodeBase Value=[#Lib.dll] Type=string Action=write /
The main problem - how to create (Default) value in registry key
HKCR\CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32 ?
This tag
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32 Value=
mscoree.dll Type=string Action=write /
is duplicated with
Class Id={83602D89-19ED-377D-BCFA-07DEC0826D15} Context=InprocServer32
Description=Lib.frmAdmin ThreadingModel=both.../Class
what can i do with it?
--
Best regards, Myth
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installed: Local; Request: Absent; Action: Null ?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of André Pönitz Sent: Thursday, December 21, 2006 3:20 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Installed: Local; Request: Absent; Action: Null ? Arnette, Bill wrote: Non-Windows Installer installers use the SharedDlls registry key to refcount the usage of common/shared dlls. By default Windows Installer will only increment that refcount if it already exists so that the other installer will track the refcount properly if a WI installer installs the same file. Windows Installer also maintains its own refcount for components it tracks elsewhere. You can force Windows Installer to create a SharedDLLs entry if it doesn't already exist with the msidbComponentAttributesSharedDllRefCount attribute on a component. So this is what the SharedDllRefCount='yes' attribute means... Let me try to get the consequences for me straight: if I have an old installer using the SharedDll mechanism and new installers are msi based (and will stay so for the forseeable future) I would not have to explicitly use SharedDllRefCount='yes' and it'd still work if I install my newer version in parallel (yes, we do that...) to the older version and I could deinstall in arbitrary order. As I understand it, yes; theoretically :) It would not work, however, if I installed the new version first and than the older one in parallel. But as that's not a scenario I need to support, I'd be ok without using the SharedDllRefCount='yes' attribute. Did I get that right? Right, because unless you explicitly tell MSI to use SharedDllRefCount, the other/older installer is unaware that the MSI-installed product/version is sharing that file. So what that log indicates is that a non-WI installer installed that file before your product was installed and that since the SharedDlls refcount will not go to 0 after your product is uninstalled, the file will not be removed so that the other product is not broken. Ok, that's probably exactly what happens as I have an older version installed (or at least not fully uninstalled) Thanks for the explanation, Andre' Glad I could help. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Setting (Default) value for registry key
I think this bug in heat was reported before. Until someone fixes heat, you'll
have to delete the colliding registry key. The collision is happening in new
code in heat so the bug isn't completely unexpected... it was one of the last
things Derek did before he left (and we haven't had anyone else with cycles to
maintain heat).
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vasiliy Povalyaev
Sent: Thursday, December 21, 2006 03:44
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Setting (Default) value for registry key
Hi.
I have a problem and i hope somebody can help me.
I need to register .NET assembly for COM during installation. So i use heat to
produce a valid code. Here is an example:
Component Id=Lib.dll Guid=PUT-GUID-HERE
Class Id={83602D89-19ED-377D-BCFA-07DEC0826D15}
Context=InprocServer32 Description=Lib.frmAdmin ThreadingModel=both
ProgId Id=Lib.frmAdmin Description=Lib.frmAdmin /
/Class
File Id=Lib.dll Name=AdminInquiryLib.dll KeyPath=yes
Source=C:\blah\blah\blah\Lib.dll /
ProgId Id=Record /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32\2.0.0.0
Name=Class Value=Lib.frmAdmin Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32\2.0.0.0
Name=Assembly Value=Lib, Version=2.0.0.0http://2.0.0.0, Culture=neutral,
PublicKeyToken=f57227384aa6f133 Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32\2.0.0.0
Name=RuntimeVersion Value=v2.0.50727 Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32\2.0.0.0
Name=CodeBase Value=[#Lib.dll] Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32
Value=mscoree.dll Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32 Name=Class
Value=Lib.frmAdmin Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32
Name=Assembly Value=Lib, Version=2.0.0.0http://2.0.0.0, Culture=neutral,
PublicKeyToken=f57227384aa6f133 Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32
Name=RuntimeVersion Value=v2.0.50727 Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32
Name=CodeBase Value=[#Lib.dll] Type=string Action=write /
The main problem - how to create (Default) value in registry key
HKCR\CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32 ?
This tag
RegistryValue Root=HKCR
Key=CLSID\{83602D89-19ED-377D-BCFA-07DEC0826D15}\InprocServer32
Value=mscoree.dll Type=string Action=write /
is duplicated with
Class Id={83602D89-19ED-377D-BCFA-07DEC0826D15} Context=InprocServer32
Description=Lib.frmAdmin ThreadingModel=both.../Class
what can i do with it?
--
Best regards, Myth
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] help with Tallow.exe error on Vista
Well, it certainly is possible there is something in Vista that confused
tallow's registry redirection code. There have been plenty of problems in that
area (it's a funky little feature that causes lots of weird side-effects). At
this point, you'd have to debug the selfreg of your OCX a little bit to
understand why it is failing under tallow (probably some redirected registry
key is missing).
From: Dan Hoeger
Sent: Thursday, December 21, 2006 08:12
To: Rob Mensching; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] help with Tallow.exe error on Vista
I've run across several files with this issue in tallow on Vista but I can
register them with regsvr32 on Vista just fine.
From: Rob Mensching
Sent: Thursday, December 21, 2006 10:10 AM
To: Dan Hoeger; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] help with Tallow.exe error on Vista
It appears the OCX does not like Vista.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Hoeger
Sent: Thursday, December 21, 2006 08:07
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] help with Tallow.exe error on Vista
Does anyone know off hand why this would fail on Vista?
This same call works fine on 2003 server.
Thanks,
Dan
Source\Common\CrmFileListtallow.exe -s Drop2Ctrl.ocx
Microsoft (R) Windows Installer Xml Tool version 2.0.3929.0
Copyright (C) Microsoft Corporation 2003. All rights reserved.
Wix xmlns=http://schemas.microsoft.com/wix/2003/01/wi;
Fragment
DirectoryRef Id=TARGETDIR
Component Id=component0 DiskId=1 Guid=PUT-GUID-HERE
File Id=file0 Name=DROP2C_1.OCX LongName=Drop2Ctrl.ocx
src=d:\enlistment\fwm3\Source\Common\CrmFileList\Drop2Ctrl.ocx /Failed to
SelfReg: Drop2Ctrl.ocx
System.Reflection.TargetInvocationException: Exception has been thrown by the
target of an invocation. --- System.Runtime.InteropServices.COMException
(0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM
component.
at DllRegisterServer()
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[]
arguments, SignatureStruct sig, MethodAttributes methodAttributes,
RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[]
arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle
typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean
skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at
Microsoft.Tools.WindowsInstallerXml.Tools.Tallow.TallowMain.DynamicPInvoke(String
dll, String entryPoint, Type returnType, Type[] parameterTypes, Object[]
parameterValues)
at
Microsoft.Tools.WindowsInstallerXml.Tools.Tallow.TallowMain..ctor(String[] args)
Registry Root=HKCR
Key=CLSID\{D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731} Value=VBPropertyBag
Type=string /
Registry Root=HKCR
Key=CLSID\{D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}\InProcServer32
Value=C:\Windows\system32\MSVBVM60.DLL Type=string /
Registry Root=HKCR
Key=CLSID\{D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}\InProcServer32
Name=ThreadingModel Value=Apartment Type=string /
/Component
/DirectoryRef
/Fragment
/Wix
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] volatile registry key
Hello, Sorry if this is in the user list archive or tutorial, my quick search did not come up with anything. Is there a way to create a volatile registry key with Wix? Thanks, Tom - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] volatile registry key
Why would setup create a volatile key? My understanding is that when the registry hive is unloaded (usually on a reboot) the key would be lost. Your setup would be broken after every reboot and a repair would be in order. What's the scenario? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Svare Sent: Thursday, December 21, 2006 08:29 To: wix-users@lists.sourceforge.net Subject: [WiX-users] volatile registry key Hello, Sorry if this is in the user list archive or tutorial, my quick search did not come up with anything. Is there a way to create a volatile registry key with Wix? Thanks, Tom - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] System.ArgumentException in ClickThrough
When I try to run the ClickThrough wizard, as soon as l select a folder where my binaries are, the program crashes. The report references a system.argumentexception in the WiX Toolset ClickThrough UI. Here is more information about the crash: Code: 0xe0434f4d Address: 0x7c812a5b Windows XP SP2 The module seems to be ctui.exe Any help would be greatly appreciated. Levi - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] help with Tallow.exe error on Vista
Have you tried running it from an elevated command prompt? That sometimes
helps with COM registrations (despite the fact that the 'canary' keys that
HKCR, etc, are redirected to should be editable by a non-admin user, I found
that a low-privileged account didn't always work under XP).
I wonder if Vista's own registry redirection feature for legacy applications
gets in the way here. Does tallow have a manifest to specify asInvoker
privilege level?
--
Mike Dimmick
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dan Hoeger
Sent: 21 December 2006 16:07
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] help with Tallow.exe error on Vista
Does anyone know off hand why this would fail on Vista?
This same call works fine on 2003 server.
Thanks,
Dan
Source\Common\CrmFileListtallow.exe -s Drop2Ctrl.ocx
Microsoft (R) Windows Installer Xml Tool version 2.0.3929.0
Copyright (C) Microsoft Corporation 2003. All rights reserved.
Wix xmlns=http://schemas.microsoft.com/wix/2003/01/wi;
Fragment
DirectoryRef Id=TARGETDIR
Component Id=component0 DiskId=1 Guid=PUT-GUID-HERE
File Id=file0 Name=DROP2C_1.OCX LongName=Drop2Ctrl.ocx
src=d:\enlistment\fwm3\Source\Common\CrmFileList\Drop2Ctrl.ocx /Failed to
SelfReg: Drop2Ctrl.ocx
System.Reflection.TargetInvocationException: Exception has been thrown by
the target of an invocation. ---
System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT
E_FAIL has been returned from a call to a COM component.
at DllRegisterServer()
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[]
arguments, SignatureStruct sig, MethodAttributes methodAttributes,
RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[]
arguments, Signature sig, MethodAttributes methodAttributes,
RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean
skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at
Microsoft.Tools.WindowsInstallerXml.Tools.Tallow.TallowMain.DynamicPInvoke(S
tring dll, String entryPoint, Type returnType, Type[] parameterTypes,
Object[] parameterValues)
at
Microsoft.Tools.WindowsInstallerXml.Tools.Tallow.TallowMain..ctor(String[]
args)
Registry Root=HKCR
Key=CLSID\{D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731} Value=VBPropertyBag
Type=string /
Registry Root=HKCR
Key=CLSID\{D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}\InProcServer32
Value=C:\Windows\system32\MSVBVM60.DLL Type=string /
Registry Root=HKCR
Key=CLSID\{D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}\InProcServer32
Name=ThreadingModel Value=Apartment Type=string /
/Component
/DirectoryRef
/Fragment
/Wix
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] volatile registry key
Hello, One of our features installs a kernel driver and we don't want maintenance to be performed or the application to run unless a reboot is done. Thanks, Tom From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Thursday, December 21, 2006 11:34 AM To: Thomas Svare; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] volatile registry key Why would setup create a volatile key? My understanding is that when the registry hive is unloaded (usually on a reboot) the key would be lost. Your setup would be broken after every reboot and a repair would be in order. What's the scenario? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Svare Sent: Thursday, December 21, 2006 08:29 To: wix-users@lists.sourceforge.net Subject: [WiX-users] volatile registry key Hello, Sorry if this is in the user list archive or tutorial, my quick search did not come up with anything. Is there a way to create a volatile registry key with Wix? Thanks, Tom - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] help with Tallow.exe error on Vista
I am running under an Administrator console window and I am able to register
the same component with regsrv32 from the same console
From: Mike Dimmick [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 21, 2006 10:38 AM
To: Dan Hoeger; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] help with Tallow.exe error on Vista
Have you tried running it from an elevated command prompt? That sometimes helps
with COM registrations (despite the fact that the 'canary' keys that HKCR, etc,
are redirected to should be editable by a non-admin user, I found that a
low-privileged account didn't always work under XP).
I wonder if Vista's own registry redirection feature for legacy applications
gets in the way here. Does tallow have a manifest to specify asInvoker
privilege level?
--
Mike Dimmick
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Hoeger
Sent: 21 December 2006 16:07
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] help with Tallow.exe error on Vista
Does anyone know off hand why this would fail on Vista?
This same call works fine on 2003 server.
Thanks,
Dan
Source\Common\CrmFileListtallow.exe -s Drop2Ctrl.ocx
Microsoft (R) Windows Installer Xml Tool version 2.0.3929.0
Copyright (C) Microsoft Corporation 2003. All rights reserved.
Wix xmlns=http://schemas.microsoft.com/wix/2003/01/wi;
Fragment
DirectoryRef Id=TARGETDIR
Component Id=component0 DiskId=1 Guid=PUT-GUID-HERE
File Id=file0 Name=DROP2C_1.OCX LongName=Drop2Ctrl.ocx
src=d:\enlistment\fwm3\Source\Common\CrmFileList\Drop2Ctrl.ocx /Failed to
SelfReg: Drop2Ctrl.ocx
System.Reflection.TargetInvocationException: Exception has been thrown by the
target of an invocation. --- System.Runtime.InteropServices.COMException
(0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM
component.
at DllRegisterServer()
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[]
arguments, SignatureStruct sig, MethodAttributes methodAttributes,
RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[]
arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle
typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean
skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at
Microsoft.Tools.WindowsInstallerXml.Tools.Tallow.TallowMain.DynamicPInvoke(String
dll, String entryPoint, Type returnType, Type[] parameterTypes, Object[]
parameterValues)
at
Microsoft.Tools.WindowsInstallerXml.Tools.Tallow.TallowMain..ctor(String[] args)
Registry Root=HKCR
Key=CLSID\{D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731} Value=VBPropertyBag
Type=string /
Registry Root=HKCR
Key=CLSID\{D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}\InProcServer32
Value=C:\Windows\system32\MSVBVM60.DLL Type=string /
Registry Root=HKCR
Key=CLSID\{D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}\InProcServer32
Name=ThreadingModel Value=Apartment Type=string /
/Component
/DirectoryRef
/Fragment
/Wix
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] volatile registry key
You don't want to declare a registry key in setup then (there is no support for volatile keys, for the reasons I mentioned below). Instead, it seems like you need a CustomAction to create a temporary marker. The WiX toolset has a function in the CustomAction Library that is used to communicate a reboot is required from the deferred CustomAction to the immediate CustomAction by using an Atom. You can see the code in wix\src\ca\wcautil\wcawrap.cpp - WcaDeferredActionRequiresReboot(). From: Thomas Svare [mailto:[EMAIL PROTECTED] Sent: Thursday, December 21, 2006 08:44 To: Rob Mensching; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] volatile registry key Hello, One of our features installs a kernel driver and we don't want maintenance to be performed or the application to run unless a reboot is done. Thanks, Tom From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Thursday, December 21, 2006 11:34 AM To: Thomas Svare; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] volatile registry key Why would setup create a volatile key? My understanding is that when the registry hive is unloaded (usually on a reboot) the key would be lost. Your setup would be broken after every reboot and a repair would be in order. What's the scenario? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Svare Sent: Thursday, December 21, 2006 08:29 To: wix-users@lists.sourceforge.net Subject: [WiX-users] volatile registry key Hello, Sorry if this is in the user list archive or tutorial, my quick search did not come up with anything. Is there a way to create a volatile registry key with Wix? Thanks, Tom - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] volatile registry key
Rob, That makes sense. The volatile registry creation is currently in a CA of a merge module I'm trying to convert to Wix. Thanks, Tom From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Thursday, December 21, 2006 11:49 AM To: Thomas Svare; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] volatile registry key You don't want to declare a registry key in setup then (there is no support for volatile keys, for the reasons I mentioned below). Instead, it seems like you need a CustomAction to create a temporary marker. The WiX toolset has a function in the CustomAction Library that is used to communicate a reboot is required from the deferred CustomAction to the immediate CustomAction by using an Atom. You can see the code in wix\src\ca\wcautil\wcawrap.cpp - WcaDeferredActionRequiresReboot(). From: Thomas Svare [mailto:[EMAIL PROTECTED] Sent: Thursday, December 21, 2006 08:44 To: Rob Mensching; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] volatile registry key Hello, One of our features installs a kernel driver and we don't want maintenance to be performed or the application to run unless a reboot is done. Thanks, Tom From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Thursday, December 21, 2006 11:34 AM To: Thomas Svare; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] volatile registry key Why would setup create a volatile key? My understanding is that when the registry hive is unloaded (usually on a reboot) the key would be lost. Your setup would be broken after every reboot and a repair would be in order. What's the scenario? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Svare Sent: Thursday, December 21, 2006 08:29 To: wix-users@lists.sourceforge.net Subject: [WiX-users] volatile registry key Hello, Sorry if this is in the user list archive or tutorial, my quick search did not come up with anything. Is there a way to create a volatile registry key with Wix? Thanks, Tom - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrade XML config files
Alexander Biryukov wrote: Can anybody suggest universal mechanism to upgrade XML config files (such as Web.config) ? Take a look at the XmlConfig custom action in WiX v3. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Query selected features?
Matthew Janulewicz wrote: ADDLOCAL is set later in the InstallSequence (I believe) so I can't use that. Is there a variable that is set by the feature tree at the moment feature selections change? Or, is there a way I'm not aware of (and too dumb to find in the docs, apparently) to set a variable at the time a feature is selected or unselected? Thanks! Take a look at the Conditional Statement Syntax and Examples of Conditional Statement Syntax topics in the MSI SDK. They cover the featureId syntax for determining feature action state. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Creating user in AD
Michael Osmond wrote: I am not familiar with the custom action, but do you know if it is impersonating the user running the install or as the local system account (which the MSI process uses). I suspect it is the later, in that case the custom action will work if the install is running on a domain controller, but will not work on a member server/workstation, because the local system account only has local significance. Correct -- the CA that creates the users runs as system. There isn't explicit support in the serverca code to support AD. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] System.ArgumentException in ClickThrough
When I try to run the ClickThrough wizard, as soon as l select a folder where my binaries are, the program crashes. The report references a system.argumentexception in the WiX Toolset ClickThrough UI. Here is more information about the crash: Code: 0xe0434f4d Address: 0x7c812a5b Windows XP SP2 The module seems to be ctui.exe Any help would be greatly appreciated. Levi - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrade XML config files
Yes, XmlConfig useful for me in some cases. Is exist a plans for port this CA to Wix2 ? -- Alexander Biryukov On Thu, 21 Dec 2006 20:04:53 +0300, Bob Arnson [EMAIL PROTECTED] wrote: Alexander Biryukov wrote: Can anybody suggest universal mechanism to upgrade XML config files (such as Web.config) ? Take a look at the XmlConfig custom action in WiX v3. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] ICE20 with WiX v3
I receive the following errors when trying to follow along with part 8 of the tutorial when linking with version 3 (all ICE20s BTW): - Standard Dialog: 'FilesInUse' not found in Dialog table - ErrorDialog Property not specified in Property table - Exit dialog/action not found in AdminUISequence (and one about InstallUISequence - etc. Can anyone offer me any insight or point me to a website that indicates some of the differences between version 2 and 3 of the linker and why I keep running into ICExxx errors? Any help would be greatly appreciated, thanks! Levi - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ICE20 with WiX v3
The difference you're seeing is that WiX v2 did not run validation and WiX v3 does. Those are errors in your WiX v2 package, you just didn't know it before. smile/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Levi Wilson Sent: Thursday, December 21, 2006 12:54 To: wix-users@lists.sourceforge.net Subject: [WiX-users] ICE20 with WiX v3 I receive the following errors when trying to follow along with part 8 of the tutorial when linking with version 3 (all ICE20s BTW): * Standard Dialog: 'FilesInUse' not found in Dialog table * ErrorDialog Property not specified in Property table * Exit dialog/action not found in AdminUISequence (and one about InstallUISequence * etc. Can anyone offer me any insight or point me to a website that indicates some of the differences between version 2 and 3 of the linker and why I keep running into ICExxx errors? Any help would be greatly appreciated, thanks! Levi - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ICE20 with WiX v3
The biggest difference, and the reason you're seeing the errors now when you didn't before, is that wix 3 runs ICE validation on the MSI that is created by light, while wix 2 didn't. Most likely, if you run ice validation on the msi you created with wix 2, you'll see the same errors. You just have to run ICE validation manually, like through Orca. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Levi Wilson Sent: Thursday, December 21, 2006 12:54 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] ICE20 with WiX v3 I receive the following errors when trying to follow along with part 8 of the tutorial when linking with version 3 (all ICE20s BTW): * Standard Dialog: 'FilesInUse' not found in Dialog table * ErrorDialog Property not specified in Property table * Exit dialog/action not found in AdminUISequence (and one about InstallUISequence * etc. Can anyone offer me any insight or point me to a website that indicates some of the differences between version 2 and 3 of the linker and why I keep running into ICExxx errors? Any help would be greatly appreciated, thanks! Levi - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ICE20 with WiX v3
The wix team generally asks that you keep the alias on replies, so everyone can learn together. I don't know much about custom dialogs. Actually, I don't know anything. I can tell you, though, from personal experience, that moving from v2 to v3 *will* identify lots of errors that have existed in your MSIs all along, but which you didn't know about, because v2 didn't run validation. Hopefully, someone else can help you with the custom dialogs. From: Levi Wilson [mailto:[EMAIL PROTECTED] Sent: Thursday, December 21, 2006 1:25 PM To: Cullen Waters Subject: Re: [WiX-users] ICE20 with WiX v3 I guess I just don't understand why adding a single dialog to display caused all these problems for a project that previously didn't have any UI. Does adding the show/ tag in the InstallUISequence force new requirements upon the MSI? I'm just playing around with custom dialogs. Any help would be greatly appreciated. On 12/21/06, Cullen Waters [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: The biggest difference, and the reason you're seeing the errors now when you didn't before, is that wix 3 runs ICE validation on the MSI that is created by light, while wix 2 didn't. Most likely, if you run ice validation on the msi you created with wix 2, you'll see the same errors. You just have to run ICE validation manually, like through Orca. From: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] On Behalf Of Levi Wilson Sent: Thursday, December 21, 2006 12:54 PM To: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: [WiX-users] ICE20 with WiX v3 I receive the following errors when trying to follow along with part 8 of the tutorial when linking with version 3 (all ICE20s BTW): * Standard Dialog: 'FilesInUse' not found in Dialog table * ErrorDialog Property not specified in Property table * Exit dialog/action not found in AdminUISequence (and one about InstallUISequence * etc. Can anyone offer me any insight or point me to a website that indicates some of the differences between version 2 and 3 of the linker and why I keep running into ICExxx errors? Any help would be greatly appreciated, thanks! Levi - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ICE20 with WiX v3
Please keep wix-users on the line so everyone sees the replies. Yes, MSDN provides explanations about all of the ICEs and common ways to fix them. From: Levi Wilson [mailto:[EMAIL PROTECTED] Sent: Thursday, December 21, 2006 13:19 To: Rob Mensching Subject: Re: [WiX-users] ICE20 with WiX v3 Thanks for the quick response. I'm very new to Windows Installer, would the best place to find out about these ICExxx errors be MSDN? I guess I'm just not sure what it is expecting. I'll continue to look into these errors. Thanks! On 12/21/06, Rob Mensching [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: The difference you're seeing is that WiX v2 did not run validation and WiX v3 does. Those are errors in your WiX v2 package, you just didn't know it before. smile/ From: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] On Behalf Of Levi Wilson Sent: Thursday, December 21, 2006 12:54 To: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: [WiX-users] ICE20 with WiX v3 I receive the following errors when trying to follow along with part 8 of the tutorial when linking with version 3 (all ICE20s BTW): * Standard Dialog: 'FilesInUse' not found in Dialog table * ErrorDialog Property not specified in Property table * Exit dialog/action not found in AdminUISequence (and one about InstallUISequence * etc. Can anyone offer me any insight or point me to a website that indicates some of the differences between version 2 and 3 of the linker and why I keep running into ICExxx errors? Any help would be greatly appreciated, thanks! Levi - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ICE20 with WiX v3
Sorry about that. Have you much experience with adding custom dialogs? I guess I just don't understand why adding a single dialog created all of these ICE errors when the UI-less install was perfectly fine. On 12/21/06, Rob Mensching [EMAIL PROTECTED] wrote: Please keep wix-users on the line so everyone sees the replies. Yes, MSDN provides explanations about all of the ICEs and common ways to fix them. *From:* Levi Wilson [mailto:[EMAIL PROTECTED] *Sent:* Thursday, December 21, 2006 13:19 *To:* Rob Mensching *Subject:* Re: [WiX-users] ICE20 with WiX v3 Thanks for the quick response. I'm very new to Windows Installer, would the best place to find out about these ICExxx errors be MSDN? I guess I'm just not sure what it is expecting. I'll continue to look into these errors. Thanks! On 12/21/06, *Rob Mensching* [EMAIL PROTECTED] wrote: The difference you're seeing is that WiX v2 did not run validation and WiX v3 does. Those are errors in your WiX v2 package, you just didn't know it before. smile/ *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Levi Wilson *Sent:* Thursday, December 21, 2006 12:54 *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] ICE20 with WiX v3 I receive the following errors when trying to follow along with part 8 of the tutorial when linking with version 3 (all ICE20s BTW): - Standard Dialog: 'FilesInUse' not found in Dialog table - ErrorDialog Property not specified in Property table - Exit dialog/action not found in AdminUISequence (and one about InstallUISequence - etc. Can anyone offer me any insight or point me to a website that indicates some of the differences between version 2 and 3 of the linker and why I keep running into ICExxx errors? Any help would be greatly appreciated, thanks! Levi - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ICE20 with WiX v3
Because now that you have UI, the Windows Installer will call back to your UI for things like FileInUse and random error handling. MSDN should talk about this stuff more. From: Levi Wilson [mailto:[EMAIL PROTECTED] Sent: Thursday, December 21, 2006 13:32 To: Rob Mensching; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] ICE20 with WiX v3 Sorry about that. Have you much experience with adding custom dialogs? I guess I just don't understand why adding a single dialog created all of these ICE errors when the UI-less install was perfectly fine. On 12/21/06, Rob Mensching [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Please keep wix-users on the line so everyone sees the replies. Yes, MSDN provides explanations about all of the ICEs and common ways to fix them. From: Levi Wilson [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Thursday, December 21, 2006 13:19 To: Rob Mensching Subject: Re: [WiX-users] ICE20 with WiX v3 Thanks for the quick response. I'm very new to Windows Installer, would the best place to find out about these ICExxx errors be MSDN? I guess I'm just not sure what it is expecting. I'll continue to look into these errors. Thanks! On 12/21/06, Rob Mensching [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: The difference you're seeing is that WiX v2 did not run validation and WiX v3 does. Those are errors in your WiX v2 package, you just didn't know it before. smile/ From: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] On Behalf Of Levi Wilson Sent: Thursday, December 21, 2006 12:54 To: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: [WiX-users] ICE20 with WiX v3 I receive the following errors when trying to follow along with part 8 of the tutorial when linking with version 3 (all ICE20s BTW): * Standard Dialog: 'FilesInUse' not found in Dialog table * ErrorDialog Property not specified in Property table * Exit dialog/action not found in AdminUISequence (and one about InstallUISequence * etc. Can anyone offer me any insight or point me to a website that indicates some of the differences between version 2 and 3 of the linker and why I keep running into ICExxx errors? Any help would be greatly appreciated, thanks! Levi - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ICE20 with WiX v3
Thanks again for the help. I'll continue to scour MSDN for more information. These errors will probably disappear since I'll be including some default UI sequences with the -ext WixUIExtension.dll parameter (terminology?). Thanks again! On 12/21/06, Rob Mensching [EMAIL PROTECTED] wrote: Because now that you have UI, the Windows Installer will call back to your UI for things like FileInUse and random error handling. MSDN should talk about this stuff more. *From:* Levi Wilson [mailto:[EMAIL PROTECTED] *Sent:* Thursday, December 21, 2006 13:32 *To:* Rob Mensching; wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] ICE20 with WiX v3 Sorry about that. Have you much experience with adding custom dialogs? I guess I just don't understand why adding a single dialog created all of these ICE errors when the UI-less install was perfectly fine. On 12/21/06, *Rob Mensching* [EMAIL PROTECTED] wrote: Please keep wix-users on the line so everyone sees the replies. Yes, MSDN provides explanations about all of the ICEs and common ways to fix them. *From:* Levi Wilson [mailto:[EMAIL PROTECTED] *Sent:* Thursday, December 21, 2006 13:19 *To:* Rob Mensching *Subject:* Re: [WiX-users] ICE20 with WiX v3 Thanks for the quick response. I'm very new to Windows Installer, would the best place to find out about these ICExxx errors be MSDN? I guess I'm just not sure what it is expecting. I'll continue to look into these errors. Thanks! On 12/21/06, *Rob Mensching* [EMAIL PROTECTED] wrote: The difference you're seeing is that WiX v2 did not run validation and WiX v3 does. Those are errors in your WiX v2 package, you just didn't know it before. smile/ *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Levi Wilson *Sent:* Thursday, December 21, 2006 12:54 *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] ICE20 with WiX v3 I receive the following errors when trying to follow along with part 8 of the tutorial when linking with version 3 (all ICE20s BTW): - Standard Dialog: 'FilesInUse' not found in Dialog table - ErrorDialog Property not specified in Property table - Exit dialog/action not found in AdminUISequence (and one about InstallUISequence - etc. Can anyone offer me any insight or point me to a website that indicates some of the differences between version 2 and 3 of the linker and why I keep running into ICExxx errors? Any help would be greatly appreciated, thanks! Levi - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] IIS CustomAction not registering Cert properly (ver 3.0.2330.0)
The build of v2 we were using was really old, and this code worked on that build. Was there a known regression in the code from v2 to v3? From: Rob Mensching Sent: Thursday, December 21, 2006 2:51 PM To: Cullen Waters; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] IIS CustomAction not registering Cert properly (ver 3.0.2330.0) The cert fixes in v2 has not been ported to WiX v3 yet. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Thursday, December 21, 2006 13:45 To: wix-users@lists.sourceforge.net Subject: [WiX-users] IIS CustomAction not registering Cert properly (ver 3.0.2330.0) I have some wix code that is creating a web application, and assigning a cert to that web app. Everything seems to work okay, but the cert is not getting associated with the correct website. This error just started, after moving from v2 to v3. I didn't change anything in the code in question, except to run wixcop, and have the iis: appended to the elements. Component Id=component14 Guid=316CF6D6-F173-413C-9BC0-294139F10FDA iis:Certificate Id=IWSWebSiteCert StoreName=my StoreLocation=localMachine Overwrite=yes Request=yes CertificatePath=[UIWebServer.CertificateFileName] PFXPassword=[UIWEBSERVER.CERTIFICATEPASSWORD] / iis:WebSite Id=IWSWebSite Description=UI Web Site WebLog=DefaultLogging Directory=directory16 DirProperties=IWSWebSite ConfigureIfExists=yes iis:WebAddress Id=UIHostName IP=[MYIWSWEBSITEIP] Header=[IWSWEBSITEHOST] Port=80 / iis:WebAddress Id=LocalHost IP=127.0.0.1 Header=localhost Port=80 / iis:WebAddress Id=Default_Secure IP=[MYIWSWEBSITEIP] Port=443 Secure=yes / iis:WebApplication Id=IWSWebApplication Isolation=high WebAppPool=Standard Name=IWS UI Web Site iis:CertificateRef Id=IWSWebSiteCert Permissions=8 / /iis:WebApplication /iis:WebSite /Component iis:WebDirProperties Id=IWSWebSite AnonymousAccess=yes AnonymousUser=AnonymousUserAccount LogVisits=yes Script=yes Execute=yes Read=yes DefaultDocuments=default.aspx / The installer executes fine, but when I go into inetmgr, and look at the properties of the website, the certificate is not properly associated. It looks like there is a certificate there, but when you click view cert, nothing happens. If I manually replace the cert with the one in the cert store, which this msi installed, the cert shows up properly. Anyone run into this before? Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Extracting COM data from executable COM servers (AppID) with heat.exe
As always, thank you for your help, Bob. I'll submit an enhancement request for Heat. It seems like we could add a switch (perhaps in file-mode only if it is too giving us much rope for directories) that would override the registry location, run an exe with the regserver switch, capture the diff, and provide the desired functionality. Slow and clunky, but functional. Perhaps if enough other people find it useful, it will be worth the trouble to add the functionality. Eric Hybner wrote: Do y'all have any pointers for extracting COM data from executable COM servers? Bob Arnson wrote: The technique Heat uses to detect self-reg data only works on in-proc servers. I don't think there's a way for Heat to support out-of-proc servers. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Extracting COM data from executable COM servers(AppID) with heat.exe
FWIW, the RegSpy utility here http://www.installsite.org/pages/en/tt_analyze.htm (scroll down to RegSpy) can monitor registration of out of process servers. It initiates the process suspended with the /regserver command line, then injects code to call RegOverridePredefKey for the process, then resumes the process. The result is redirection of the registration entries to a substitute key in the registry (not a .reg for or wxs file). Source is available and I'm told it still works although it's rather dated now. Capturing registry diffs is tricky unless you can completely control what's happening on the system at the time, and anyway RegOverridePredefKey to write to a completely different registry location captures the relevant data - it just needs conversion from a bunch of registry items to a wxs or .reg file. Phil Wilson From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Hybner Sent: Thursday, December 21, 2006 3:07 PM To: Bob Arnson Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Extracting COM data from executable COM servers(AppID) with heat.exe As always, thank you for your help, Bob. I'll submit an enhancement request for Heat. It seems like we could add a switch (perhaps in file-mode only if it is too giving us much rope for directories) that would override the registry location, run an exe with the regserver switch, capture the diff, and provide the desired functionality. Slow and clunky, but functional. Perhaps if enough other people find it useful, it will be worth the trouble to add the functionality. Eric Hybner wrote: Do y'all have any pointers for extracting COM data from executable COM servers? Bob Arnson wrote: The technique Heat uses to detect self-reg data only works on in-proc servers. I don't think there's a way for Heat to support out-of-proc servers. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Nested IIS:WebVirtualDir?
I think I know the answer to this (can't do it!), but I thought I'd ask anyway. There's really no technical reason for me needing to do this except 'This is the way it was done previously.' In our IIS installation, we have our 'Default Web Site', then a webdir under that called 'Corporate'. Under Corporate we have a bunch of virtual directories/web apps. It seems that Wix (3.0) can't create a WibVirtualDir this way as it references a WebSite for it's parent. So we basically end up with our web services at the root instead of under the Corporate directory. No biggie, but I wanted to be sure I knew what I was talking about before other folks notice it. Is it possible to nest a web virtual directory deeper than the root level of IIS's Default Web Site? (or the root of any website, for that matter.) -- Matthew Janulewicz SCM Engineer Green Dot Corporation [EMAIL PROTECTED] (626) 775-3857 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Please allow me to post on wix-users list
- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Status Meeting
TTEN Continues Explosive Growth TTEN *** TTEN *** TTENTTEN - Ten 10, Inc. Current Price: 08Short Term Target: .50 TTEN recently announced a key development which will enable them to provide Value Added Services to the 55 million wireless subscribers of ChinaMobile's Guangzhou Division through its joint venture with IEC. China Mobile is the largest telecommunications provider in China, and the largest among all the overseas listed Chinese companies on the Hong Kong and NewYork Stock Exchanges. TTEN is made up of 4 operating subsidiaries: Tech 10: WIFI and WiMAX Mobile 10: Music and mobile entertainment delivered via Internet, G3, etc Dream Learning Center: Digital Media Learning products Ten 10 Network: Sales and marketing Telecommunications is globally a TRILLION dollar industry. TTEN could see explosive growth as a newly trading company - 500%-1000% is not uncommon. Any of the above statements with respect to the future predications or goals and events may be seen as only Forward Looking and nothing else. All information inside this email pertaining to any sort of financial advice needs to be understood as information and not advice. None of the information above can be constructed as any sort of financial advice. This is a paid advertisement. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
