So then, why have that as a project type? It seems kind of silly, doesn't it?
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Tuesday, September 18, 2012 1:17 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] creating databa
Seems pretty interesting; I like that idea actually. I plan to join the open
source community in a very short time, and I mean everything I do will be based
on WiX, at least for setup. Everyone else can go away; we don't need
commercial installation programs anymore.
-Original Message---
Can anyone clarify where is here in my code per-machine element, please?
2012/9/14 Nelya Iva
> Thank you for response.
> INSTALLLOCATION - is a folder in ProgramFiles directory.. It's a
> per-machine location?
> So if i want to delete enries during uninstall then i need to put
> condition on fe
In WiX, yes.
http://www.robmensching.com/blog/posts/2008/10/10/What-are-.wixlibs-and-why-would-you-use-them
On Mon, Sep 17, 2012 at 4:29 PM, Katherine Moss
wrote:
> Are those meant to take the place of merge modules?
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.c
So after doing a ton of analysis I figured out my problem. Here is the
process in which my upgraded bundle goes through: Detect packages, apply
begin, uninstall existing msi package, install new msi package, apply
complete, detect packages, apply begin, uninstall previous bundle. It gets
to the poi
Actually I love merge modules. :) ( well not really... )
I worked on really massive installers with hundreds of feature and merge
modules and tens of thousands of files. Everything was reusable to compose
different installers. The GUID suffixes make it easy to track down the
source of tabl
Are those meant to take the place of merge modules?
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Monday, September 17, 2012 4:26 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] creating database problem
Yeah, that's w
I wasn't able to resolve this issue for now, but I think it should be
trivial; so leaving it as it is.
Doubt 1: Can I change the theme file to show checkboxes/form fields where
user can feed in data which can be set as Properties and used in
installation later ?
Doubt 2:
If [Doubt 1 == No] , then
Yeah, that's why we created .wixlibs.
On Mon, Sep 17, 2012 at 1:09 PM, Steven Ogilvie wrote:
> Merge Modules are really annoying!!!
>
> Moved the code out of the merge module to the product.wxs file and works
> fine!
>
> -Original Message-
> From: Hoover, Jacob [mailto:jacob.hoo...@greenh
Merge Modules are really annoying!!!
Moved the code out of the merge module to the product.wxs file and works fine!
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: September-17-12 3:34 PM
To: General discussion for Windows Installer XML toolset.
Subject:
Action being null (on the component), it's doing nothing <
http://msdn.microsoft.com/en-us/library/windows/desktop/aa367858(v=vs.85).aspx
>. What and where is the value being assigned to your
DATABASE_WINDOWSAUTHENTICATION property? Also, I assume these components are
inside a feature which is
MSI (s) (F4:9C) [15:07:30:065]: Component:
cmp_SqlDatabaseWindowsAuthenticated.1D39C24B_6F68_4E7A_9602_D57B4F7A88D7;
Installed: Absent; Request: Local; Action: Null; Client State: Unknown
MSI (s) (F4:9C) [15:07:30:065]: Component:
cmp_SqlDatabaseSQLAuthenticated.1D39C24B_6F68_4E7A_9602_D57
It's also badly mangling the log file. What lines are in the log file around
the two components?
Jacob
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: Monday, September 17, 2012 2:02 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] creating database
crap the nabble post/reply is killing the condition, lets see what happens if
I put spaces:
< C o n d i t i o n > < ! [ C D A T A [ D A T A B A S E _ W I N D O W S A U
T H E N T I C A T I O N = 1 ] ] > < / C o n d i t i o n >
for SQL server it would be =0
Steve
--
View this message in context
oops the condition got wiped out:
here it is for windows authentication:
here it is for SQL Server authentication:
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/creating-database-problem-tp7580594p7580596.html
Sent from the wix-users mailing
My first guess is the condition (blank) would probably always result in a false
condition, causing them never to happen.
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: Monday, September 17, 2012 1:22 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] crea
Hi,
I have 3 sql scripts I need to run on our database (creating, overwrite)
I have created a merge module that installs the scripts down...
I create a user account: for SQL authentication (if required)
I create two components, 1 for windows authentication the other for sql
server authentication:
If the service literally starts and stops without following the proper
service protocols, then Winmdows will give you that message about "Some
services stop". It means that your service didn't do anything. If it
looks for some resource and exits if it can't find it, then that's the
issue.
The
I don't have access to the logs right now but Rob I think you are right. I
remember when I provided an uninstall button inside of the upgraded bundle
it usually failed because of some dependency issue of the package (from the
logs), which I don't quite understand since there is only one package in
You should be able to request ABSENT for the OnPlanRelatedBundle() of the
bundle that has the same version. The default is NONE so it stays.
On Mon, Sep 17, 2012 at 10:03 AM, Neil Sleightholm wrote:
> >> The BootstrapperApplication can override the default logic to do
> whichever you want. Howeve
If your UpgradeCodes are correct then I would guess the Bundle upgrade is
failing. You should see the new Bundle kick off an uninstall of the old
Bundle at the end of the new Bundle's install.
If you take a walk through the log files you should be able to see all the
calls.
On Mon, Sep 17, 2012
I have a custom .net BootstrapperApplication where I've included .net in
the chain:
http://schemas.microsoft.com/wix/2006/wi"; xmlns:util="
http://schemas.microsoft.com/wix/UtilExtension";>
When I run the installer on a machine wi
Sorry for all the posts but I will explain my problem in more detail. I am
not using the wixstdba, I have created my very own managed Bootstrapper
Application based loosely on the Wix 3.6 Installer. Everytime I build my
solution I increment the version, it is never the same (just for testing
purpos
>> The BootstrapperApplication can override the default logic to do whichever
>> you want. However, the wixstdba does not, so you get the default behavior of
>> the engine.
If you have time I'd be interested to know how, I have looked at this and as
far as I can tell it is baked in to the Engin
The default upgrade logic in the Burn engine does not block and does not
upgrade bundles with the same version. That is pretty arguably wrong (and
is the bug Neil is referring to).
The BootstrapperApplication can override the default logic to do whichever
you want. However, the wixstdba does not,
"variables" in MSI files are called Properties. You can dereference a
Property using [PropertyId] but that only works when the column type is
Formatted. You can read about "Formatted" in the MSI SDK.
On Mon, Sep 17, 2012 at 4:25 AM, Nageswara Rao wrote:
> Hi Team,
>
> I am creating an AppPool fro
Sorry, this is my bad. I really should have made the error message
in the log file much clearer when the engine and attached container are not
signed correctly. I'll look at making this better in WiX v3.7.
On Mon, Sep 17, 2012 at 6:35 AM, Hoover, Jacob
wrote:
> Signing the bundle isn't bad, you
You want to use a public property, for example, [APPPOOLNAME]. The WiX
authoring looks like this:
On the command line you simply specify the value of the public property,
APPPOOLNAME, like this:
msiexec /i "Path\to\package.msi" APPPOOLNAME=MyAppPoolName
Note, that you can use a LaunchConditi
Try File/@PatchWholeFile="yes"
although MSDN recommends including whole files in patches, if you can, to
reduce source prompts.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370841%28v=vs.85%29
.aspx
-Original Message-
From: rowbot [mailto:jamesnrow...@yahoo.co.uk]
Sent: 17
This should be posed to the users group not the developers group.
Since the uninstall is non-interactive, the usual mantra would be if the user
has modified the XML file then you should leave it. From
http://msdn.microsoft.com/library/windows/desktop/hh749939, 5.4 Your app must
never block sile
Hi,
I have the same issue..
How can I mark certain files as a full-file patch?
Thanks,
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-failure-when-using-non-whole-files-tp701419p7580576.html
Sent from the wix-users mailing list archive
> -Original Message-
> From: Branko Horvat [mailto:branko_hor...@hotmail.com]
> Sent: Monday, September 17, 2012 14:14
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] wix ftdi drivers
>
>
>
>
> My driver msi is now set to perMachine installation. When I comment both
My driver msi is now set to perMachine installation. When I comment both
tags, the files are actually copied into general "programFiles"
(not into user programFiles).
But when I uncomment Driver tag, this error occurrs (got from log file under
/L* switch):
...
DIFXAPP: ERROR: no driver pack
Signing the bundle isn't bad, you just need to do it at the right timing
points. There are two events in MSBuild which should be used to accomplish this,
See http://wix.sourceforge.net/manual-wix3/insignia.htm for more info.
-Original Message-
From: Jeff McClintock [mailto:j...@synthe
I'm pretty sure its the package but I could be wrong.
On Sep 17, 2012 4:33 AM, "Neil Sleightholm" wrote:
> Do you mean multiple entries from your burn package or the msi?
>
> Neil
>
>
> >Does this mean I should remove the AllowSameVersions from the MajorUpgrade
> >tag also? Right now I still get
Hi Team,
I am creating an AppPool from my wix project with the below code
Now I want the AppPool Name different for different environments.
So, My idea is to create a variable and assign that variable to AppPool Name
and when I am calling the MSI from commandline, variable value should be
ov
Do you mean multiple entries from your burn package or the msi?
Neil
>Does this mean I should remove the AllowSameVersions from the MajorUpgrade
>tag also? Right now I still get multiple entries with different versions
>but I still have the flag there.
>
>Greg Beaty
>greg.bea...@gmail.com
>
>
>O
37 matches
Mail list logo
