Re: [WiX-users] Inherit permissions on a folder in WiX 3

2007-12-19 Thread Strele Franz
The Permission Extended=yes ... from WiX v2 has been replaced by the PermissionEx element in WiX v3. Have a look in the Wix.chm for all the details. Hth, Franz Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Maxim Vyazovsky Gesendet: Mittwoch, 19. Dezember 2007 13:33 An:

Re: [WiX-users] Inherit permissions on a folder in WiX 3

2007-12-19 Thread Strele Franz
My understanding is that PermissionEx is inheriting by default. For Modify I would use following attributes: Execute (or Traverse) Read ReadAttributes ReadExtendedAttributes CreateFile CreateChild WriteAttributes WriteExtendedAttributes Delete ReadPermissions Hth, Franz Von: [EMAIL

Re: [WiX-users] wix 2.0 to 3.0 - COM registration

2007-10-24 Thread Strele Franz
Using registry keys is the recommended way of registering .NET Assemblies for COM Interop. http://msdn2.microsoft.com/en-us/library/aa367520.aspx Use the Registry table instead of the Class table when you register COM Interop for an assembly. -Ursprüngliche Nachricht- Von: [EMAIL

Re: [WiX-users] wix 2.0 to 3.0 - COM registration

2007-10-24 Thread Strele Franz
You can use the 'undocumented' -scom switch with heat.exe to generate only RegistryKey/RegistryValue-entries (instead of Class/ProgId/...). -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] Im Auftrag von Strele Franz Gesendet: Mittwoch, 24

Re: [WiX-users] NOT PRIVILEDGED Condition

2007-10-16 Thread Strele Franz
Properties are case sensitive (and you have a spelling error too). You need to use NOT Privileged. Condition Message=You need to be Administrator to install this add-in.NOT Privileged/Condition Hth, Franz Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Nitin Chaudhari

Re: [WiX-users] NOT PRIVILEDGED Condition

2007-10-16 Thread Strele Franz
: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] Im Auftrag von Strele Franz Gesendet: Dienstag, 16. Oktober 2007 14:58 An: wix-users@lists.sourceforge.net Betreff: Re: [WiX-users] NOT PRIVILEDGED Condition Properties are case sensitive (and you have a spelling error too). You need to use

Re: [WiX-users] WiX Permission Element

2007-10-05 Thread Strele Franz
It's the other way round: In v2 its Permission with Extended=yes: CreateFolder Permission Extended=yes ... / /CreateFolder In v3 its PermissionEx with WixUtilExtension-namespace (here util): CreateFolder util:PermissionEx ... / /CreateFolder Hth, Franz

Re: [WiX-users] (hresult -2147024770)

2007-09-25 Thread Strele Franz
The hresult means ERROR_MOD_NOT_FOUND (The specified module could not be found.) which usually happens when you are missing a dependent dll. Can you manually register your dll on Vista (eg. with regsvr32.exe)? Hth, Franz -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED]

Re: [WiX-users] (hresult -2147024770)

2007-09-25 Thread Strele Franz
. September 2007 13:34 An: wix-users@lists.sourceforge.net Betreff: Re: [WiX-users] (hresult -2147024770) no registering the dll manualy fails as well, im not sure if its a vista prob as it works fine on XP Strele Franz-2 wrote: The hresult means ERROR_MOD_NOT_FOUND (The specified module

Re: [WiX-users] Browse dialogs New folder (Localization)

2007-09-24 Thread Strele Franz
You need to define the UITextNewFolder string in a .wxl-file like this: ?xml version=1.0 encoding=utf-8? WixLocalization Culture=de-de xmlns=http://schemas.microsoft.com/wix/2006/localization; String Id=UITextNewFolderOrdner|Neuer Ordner/String /WixLocalization Or in a .wxs-file like this:

Re: [WiX-users] tallow.exe failing to generate fragment for unmanagedshim DLL

2007-09-05 Thread Strele Franz
Instead of the -c switch, you'll need the -s switch: tallow -nologo -s LicensingClientShim.dll Hth, Franz -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] Im Auftrag von Duncan Bayne Gesendet: Mittwoch, 05. September 2007 13:33 An:

Re: [WiX-users] Kill Process

2007-08-29 Thread Strele Franz
From the Windows Installer Documentation: http://msdn2.microsoft.com/en-us/library/aa372059.aspx If you expect the installer to display a FilesInUseDialog, but it does not, this may be due to one of the following reasons: The files in use are not executables. The installer is not actually

Re: [WiX-users] Error with WIX and SQL when executing light

2007-08-20 Thread Strele Franz
I compiled (candle/light) your example with Wix 3.0.3210.0 without any problems. Make sure your paths are correct and contain the required binaries. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] Im Auftrag von Chris Gesendet: Montag, 20.

Re: [WiX-users] Getting the MSI Package Path from a custom action

2006-11-30 Thread Strele Franz
Hi, have a look at the OriginalDatabase or the SourceDir Windows Installer-property. Hth, Franz -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Gerald Grininger Gesendet: Donnerstag, 30. November 2006 09:04 An:

Re: [WiX-users] Internationalization - Folder name

2006-10-17 Thread Strele Franz
the browse dialog uses the DirectoryListNew control event. it looks up the value from NewFolder-row in the UIText-table. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/set up/directorylistnew_controlevent.asp in wix (2.0.4423.0) and WixUI_de-de.wxl it is not localized, but

Re: [WiX-users] environment variable available in executed program

2006-07-04 Thread Strele Franz
hi, have a look at the msdn-documentation for the Environment Table [1]: Note that environment variables do not change for the installation in progress when either the WriteEnvironmentStrings action or RemoveEnvironmentStrings action are run. On Windows NT and Windows 2000, this information is