Thanks, removed the "both" and added condition on this custom action
NOT
Installed
and now repair runs. Although, with Another problem. I'll post it here...
Now when my repair works it removes my Application pool account from my
Application pool and i can't understand why. Been trying to add con
Hi
Been trying to figure this one out now for a while... I'm installing a web
site, creating an application pool with a domain user and everything works
great. When hitting repair though, the application pool account i cleared
for some reason.
I finally solved it by adding a condition on custom action ConfigureIIs and
that stopped the reconfigure of iis on repair and patches.
NOT Installed AND NOT
PATCH
Hope this helps somebody else at least.
I have to say, finding this kind of info is incredibly hard. Wix feels so
undocumented but
If I change to the rememberme pattern, is there a way of saving the account
password? I mean, Its a domain service account and It wouldnt look that good
saving that in clear text in the registry.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Rep
Anybody?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Repair-removes-application-pool-user-tp7597260p7597313.html
Sent from the wix-users mailing list archive at Nabble.com.
--
I've managed to have sql:SqlDatabase inside a component without creating it:
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Running-SQL-script-without-creating-a-database-tp7597296p75
Hi
I'm running som tests on my msi and some simulated patches before releasing
my RTM package and have some problems/questions
1. When creating my patch 1.0.1.0 I do that with my Msi 1.0.0.0 as baseline.
But when creating 1.0.2.0 patch, what baseline msi should I use?
2. It seems that an updated
Here's an update. It seems that when building the patch it only includes my
added sqlscript if I also change some files. Is that expected behaviour?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-a-patch-tp7597504p7597524.html
Sent from t
Hi
I have a MyProduct_1.0.0.msi that I'm going to release and I am planning for
the patchwork that will come. When doing patch 1.0.1 I'll create a patch
comparing the two versions. So far so good...
But the patch 1.0.2. Should that be made comparing againts 1.0.0 or 1.0.1?
Thanks?
--
View thi
Thanks!
That part I got though. I think you misunderstood my question a bit. The
question was on how to generate patch 1.0.2. Should I generate that so that
it contains the difference between:
1.0.0 ->1.0.1 or
1.0.0 -> 1.0.2
--
View this message in context:
http://windows-installer-xml-wix-t
Great! I'll go with option one then. Thanks!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patching-msi-tp7597706p7597756.html
Sent from the wix-users mailing list archive at Nabble.com.
--
My setup includes several dialogs where you need to specify different Active
Directory accounts. For now, they are all free text and it's pretty easy to
miss spell. I found Msiext (http://dblock.github.io/msiext/) but was
wondering if there is something out there that can be used without starting
c
Hi
I have a product that consists of two features. Web and a Windows service.
They share some dll's that are gacced. Is it ok to inlude the gac-components
in both features? They usually are installed together. It seems to work but
what is best practice?
It now looks something like this
13 matches
Mail list logo