Hi Rob,
Does this also work if only that related bundle is installed? This will be the
case: either one or both bundles can be installed.
Met vriendelijke groet,
Rob van Rosmalen B ICT software engineer
stabiplan +31 172 65 02 65 www.stabiplan.nl www.stabiplan.nl/disclaimer
-Original
I think i didn't make myself clear, i do know how to sign the files. The
question was more like should i sign and timestamp Wix Toolset binaries
with my own certificate?
On Thu, Sep 11, 2014 at 5:50 PM, Rob Mensching r...@firegiant.com wrote:
Override the signing tasks defined in WiX .targets.
Ensuring that it's there should not be the same as you install it :)
Anyway, I need to detect if this feature is installed, so i can abort the
install if it's missing, It's easy to detect IIS and .net, but is there any
examples on how to do this feature checking?
Is WMI really the way to do it?,
Ok, the clue is to make sure you have 4 digits for the Bundle, when one
installs an new version of the bundle, it uninstalls the previous bundle
after installing the new one.
The difference is that one get two logfiles when installing the new bundle
when things are correct, the last one with
Joe, did you ever get the MaskedEdit control to only accept Upper/Lower case
letters and numbers?
I am trying the same thing and I just want the MaskedEdit to only access the
same thing, but at the moment it will accept all characters and then I have
to create conditions/CA to validate to make
I'm updating one of our installers to support change/modify and I'm running
into a few issues that I don't understand. I'm using the WixUI_FeatureTree
sequence. And, for the first time installation, by default, we want none
of the features selected for install. This works. However, later during
It should be noted that in the failure case the feature table reads like
I'd expect...(from the installer log)
Feature: Root; Installed: Local; Request: Null; Action: Null
Feature: WebSites; Installed: Local; Request: Null; Action: Null
Feature: Public; Installed: Local; Request: Null;
No the Visual Basic MaskedEdit may support uppercase 'A', but the WiX
MaskedEdit does not. I tried it anyways I set the MaskedEdit Text control to:
A-A-A-A and when I ran the install the entry field was set to
A-A-A-A.
So definitely did not work...
Since we
I don't understand why you'd want to declare something is yours (i.e. put your
signature on it) when it isn't.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Ilir
I have a MaskedEdit control that can either be blank or filled in. If blank
then next button will continue, but if any characters are entered then I
only want it to continue if all the required characters are filled in. So is
there some built in method to validate that all characters have been
Hey
Instead of creating a new MSI installer for our services for a new project
I want to use our old services MSI...
However I want to disable installing the merge modules via a MSI property...
I have:
Merge Id=EnterpriseService1ServicesMM DiskId=1
Feature Conditions?
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Steve-Ogilvie [mailto:steven.ogil...@titus.com]
Sent: Friday, September 12, 2014 11:12 AM
To:
Assuming we are using the WixUI_FeatureTree UI sequence, how can I define
my features (multi-level) such that none of them are selected for
installation by default?
This works, but I wonder if it is a poor choice...(setting the
rootfeature's level to '2')?
Feature Id=RootFeature Level=2
A signature doesn't just say this is something I wrote though.
Authenticode *should* be used to ensure that what you have provided to your
customers hasn't been modified in any way (malicious or not). Authenticode
also assists with code getting around annoying anti-virus behaviour as well.
We
We sign only what we make and own.
There is a school of thought in IP law that signing is equivalent to branding
and amounts to an appropriation of a third party's software product and is a
kin to redistributing it under your name without authorization.
This is very far from a settled area of
Dear All,
I'm trying to create an msi that would, base on user selection during the
installation process, install either the admin or regular user of the
application. This access right is controlled by an element
ApplicationName.exe.config file (this is not an ideal solution, but for the
Change your level to 2
On Fri, Sep 12, 2014 at 1:44 PM, Tony yellowjacketl...@gmail.com wrote:
Assuming we are using the WixUI_FeatureTree UI sequence, how can I define
my features (multi-level) such that none of them are selected for
installation by default?
This works, but I wonder if it
17 matches
Mail list logo
