>
>Meant maybe try to explain why you are getting downgrading between builds
>with no errors - from 2.3.4.6 to 2.3.4.2 Got ahead of myself.
>
As far as MSI is concerned, those 2 version numbers are the same. MSI only
looks at the first 3 parts.
http://msdn.microsoft.com/en-us/library/aa370
Meant maybe try to explain why you are getting downgrading between builds
with no errors - from 2.3.4.6 to 2.3.4.2 Got ahead of myself.
J
On Mon, Jun 2, 2014 at 3:15 PM, Jeremiahf wrote:
> FYI there is not an attachment.
>
> This is how I used to do it before my requirements changed...
>
I'll answer my own question. No, SqlScript does not perform property
substitution.
I had thought property substitution rules were being followed when I was
troubleshooting an install failure that had a msi log entry like this...
ExecuteSqlStrings: Executing SQL string: CREATE TABLE .(
IDENTI
FYI there is not an attachment.
This is how I used to do it before my requirements changed...
will upgrade 1.1.1.1 to 1.1.2.1 and not allow a downgrade.
keep the Upgradecode static and the product/Package Ids to "*"
I use a config.wxi file that I include into product.wxs then reference the
valu
Does the SqlExtension's SqlScript processing use installer property
substitution rules?
IOW, if my script contains...
CREATE TABLE [MyDatabase].[MyTable](
[MyId] [int] IDENTITY(1,1) NOT NULL,
[CreatedOn] [datetime] NOT NULL,
[CreatedBy] [nvarchar](256) NOT NULL
)
Am I expected to escape all o
Hi there!
I have a terrible problem with using the MajorUpgrade element in the current
installer we have. We tended to use the Upgrade element having different error
messages for different versions by using UpgradeVersion property.
We wanted this behaviour to persist and to force the Major upgrad
It sounds like a repair, so also look for MsiInstaller entries in the
Windows Event Log (Application).
---
Phil Wilson
On Mon, Jun 2, 2014 at 4:50 AM, Phill Hogland wrote:
> I would enable verbose logging on the test system and then review the log
> after the on-demand install happen
It's viable in the sense that it works, and you can disable the ice
warning, and I've had conversations with Microsoft about using it as
an alternative solution to
http://support.microsoft.com/kb/905238/en-us but you lose
MigrateFeatureStates if that matters to you.
---
Phil Wilson
On
I have built a service that requires common.logging DLL. This service
works correctly when I manually install using 'installutil'. I have
included common.logging DLL as a component in the Product.wxs file and when
I install and run the service using the WiX installer I get an error
message about
I would suggest using melt from the WiX Toolkit instead of msiexec to create
your administrative installs. This will allow you to re-base your folders
anywhere you want.
There is one caveat to this: You *must* use a bindpath for your installer
sources. This usually isn't a breaking change but wo
Hi!
I have a WiX bundle executable (using Bundle/Chain/MsiPackage elements) I use
to install 2 different MSI packages.
I already have several MSI properties as Variable elements that are defined in
the bundle and passed along to the MSI packages as MsiProperty elements.
My question now is, how c
I would enable verbose logging on the test system and then review the log
after the on-demand install happens.
http://support.microsoft.com/kb/223300
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Installer-runs-after-upgrade-if-running-instal
On 29-05-2014 19:13, Phil Wilson wrote:
> Yes, in this case scheduling RemoveExistingProducts before
> CostInitialize should solve the problem if it's related to this:
Yeah, that is what I figured. Unfortunately, that is not a legal
scheduling. According to
http://msdn.microsoft.com/en-us/library
Thanks All,
I have found a solution, the problem here was that I was performing admin
install of the application in a directory other than %TEMP% directory. Once
I moved the admin install inside the %TEMP% directory, the issue was
resolved.
I have a question here, is there a way to perform these
14 matches
Mail list logo
