Dear All,
I followed an example from a book (Wix 3.6: A Developer's Guide to Windows
Installer XML by Nick Ramirez, Chapter 16) to create a WiX bootstrapper
application DLL. The project in this example has a WPF view and references the
Microsoft.Practices.Prism assembly from SilverLight and tha
2013/12/11 Dave Williamson, Clear Sky Software :
> My brain is twisted and can't seem to get the condition logic right.
>
> 1. If the Product has not been installed on the machine then the
> condition should set Level to 1.
>
> 2. If the Product has been installed but the HAVELS2208 reg
I'm not sure about this, but if the DISM API can do this, it might be
somewhat easier. DismEnableFeature(), for example.
Phil Wilson
On Wed, Dec 11, 2013 at 6:59 AM, John Walter wrote:
> Thanks Steven yes I have similar also by checking the registry I build a
> list of the missing features so i
Thanks John for the useful tip. So far I have not been asked to consider
installing on anything other than standard Windows 7 or 8 PCs but I know
that installing onto server versions will be needed in the near future.
On 11 December 2013 15:24, John Cooper wrote:
> Using the Get-WindowsFeature
If you don't specify an ALLUSERS property it defaults to per user. The
behavior you see might be because ALLUSERS was 2, which does per machine if
the user is privileged and per user if not privileged. Verify what's
happening to ALLUSERS by looking in the log, for the upgrade and original,
and what
Thanks Steven yes I have similar also by checking the registry I build a
list of the missing features so in theory if all the needed features are
active I should not need to run DISM.
As I said my main issue is with the seemingly random nature of what happens
when DISM is run on the one PC startin
Using the Get-WindowsFeature PowerShell cmdlet is a far better option on Server
OS: 1) the interface is consistent between Server 2008R2 and Server 2012; and
2) the resulting PowerShell objects are much easier to reliably parse.
The only gotcha is that the C# wrapper needs to be compiled x64.
One problem is that between the different versions of Windows the DISM command
line parameters have changed...
I have created a custom action that checks what version of Windows I am running
and then sets the command line parameters up accordingly...
Btw WriteErrorLogInstall is a custom logging f
My brain is twisted and can't seem to get the condition logic right.
1. If the Product has not been installed on the machine then the
condition should set Level to 1.
2. If the Product has been installed but the HAVELS2208 registry key
doesn't exist then the condition should NOT
Hi,
I am fairly new to the WiX installer but have been able to create an
install package that creates our website and installs all needed components
some being installed from other installers run from my bootstrapper.
The one element I am having difficulties with is enabling IIS. We need to
have
10 matches
Mail list logo
