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

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 PROTECT

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

The from WiX v2 has been replaced by the 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: wix-users@lists.sourceforge.net Betreff: Re: [

[WiX-users] New Dialogs not in Patch when using pyro.exe

Hello all, When I create a patch using "pyro.exe" (as described in the help file), it does not contain new rows in the "Dialog", "Control", "ControlEvent", etc. tables, but the corresponding rows in "InstallUISequence". When I look inside the generated .wixmst-file, I can find the rows with 'op="a

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

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 F

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

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: [EMAI

Re: [WiX-users] NOT PRIVILEDGED Condition

Correction: the expression must evaluate to True for installation to begin. So you need to use "Privileged" instead of "NOT Privileged", like this: Privileged Hth, Franz > -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] [mailto:wix-users- > [EMAIL PRO

Re: [WiX-users] NOT PRIVILEDGED Condition

Properties are case sensitive (and you have a spelling error too). You need to use "NOT Privileged". NOT Privileged Hth, Franz Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Nitin Chaudhari Gesendet: Dienstag, 16. Oktober 2007 14:36 An: wix-users@lists.sourceforge.net Betre

Re: [WiX-users] WiX Permission Element

It's the other way round: In v2 its Permission with Extended=yes: In v3 its "PermissionEx" with WixUtilExtension-namespace (here "util"): Hth, Franz > -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] [mailto:wix-users- > [EMAIL PROTECTED] Im Auftrag von Ro

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

Gesendet: Dienstag, 25. 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

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

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] [mailto:wix

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

You need to define the "UITextNewFolder" string in a .wxl-file like this: http://schemas.microsoft.com/wix/2006/localization";> Ordner|Neuer Ordner Or in a .wxs-file like this: Ordner|Neuer Ordner > -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] [mailto:wix-users- >

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

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: wix

Re: [WiX-users] Kill Process

>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 tryi

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

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. Au

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

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: wix-users@lists

Re: [WiX-users] Internationalization - Folder name

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

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

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