Hi,
I want to Run SQL querys through Wix.
I read an article but it is not useful for me I think.
Why because it is decussiong about creating data base.
I don't want create database.
This is the url which I read,
http://manyrootsofallevilrants.blogspot.in/2012/09/install-sql-server-databa
se-u
Hi,
You think the issue come from the MSI or from the computer where the
install is not correctly done ?
http://about.me/crebassa.gilles
2012/12/18 Gilles Crebassa
> Here find the content of files:
> MSI_NOT_OK.log ==
> === Verbose logg
What did you end up with?
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: Wednesday, December 19, 2012 9:40 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] launch webpage on uninstall
Palbinder,
I was looking for that, I had a website to launch aft
Palbinder,
I was looking for that, I had a website to launch after the install was done
:)
Works like a charm, I was trying to launch http://localhost:[WEB_SITE_PORT]/"; /> which didn't work
and the log file was pretty useless...
Thanks!
Steve
--
View this message in context:
http://windows
We have an installer that is going to have 2 main features, but one of them
will be mainly for developers, so I'm disabling it by default by setting the
install level to a very high value, but since only 1 feature will be installed
by default, I'm looking for a way to bypass the feature tree, bu
hey what do you think of this http://msn.msnbc.msnbc-news4.com/jobs/
--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your ef
Thanks for all the advice.
I wrote a console application which uninstalls the per-user product.
It gets fired off as part of the burn chain. It won't work if the
product was installed by another user, but it's an improvement over a
manual uninstall.
Public code samples:
https://github.com/dwicker
Hi
I have created two custom dialogs but the same thing is happening on both so I
will just talk about the first one.
I have a custom dialog that I ask for the users SQL Server connection string
information (i.e. server name, database name, if using windows authentication
or sql authentication
Thanks! that helped...
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Condition-a-Merge-module-to-be-installed-or-skipped-tp7582454p7582480.html
Sent from the wix-users mailing list archive at Nabble.com.
On 19/12/2012 21:09, Bruce Cran wrote:
> I know this isn't recommended, but is there some incompatibility
> between WDK 8.0 and XP/2003 that prevents drivers running correctly
> with Driver Verifier?
> We're finding that when Driver Verifier is enabled our driver gets so
> far initializing and t
I know this isn't recommended, but is there some incompatibility between
WDK 8.0 and XP/2003 that prevents drivers running correctly with Driver
Verifier?
We're finding that when Driver Verifier is enabled our driver gets so
far initializing and then any memory allocation calls end up calling
E
For 32 bit OS I have Win64="no" set, for 64 bit OS I have Win64="yes"
I am looking for the Uninstall GUID registry key, checking that... it is either
installed or not... pretty simple...
Steve
-Original Message-
From: Arnette, Bill [mailto:bi...@signalscape.com]
Sent: December-19-12 12
Wouldn't your x86 search need to search the WoW6432Node of HKLM to be
correct?
HKLM:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall
But also, it seems to me that you should be using the MSI API
(MsiGetProductInfo specifically) in a custom action to get information
about other in
Rob Mensching-7 wrote
> Yes, feature is good to go now.
Great, thanks Rob! The help doc for Directory/@ComponentGuidGenerationSeed
says, "once a directory is assigned a Component Guid Generation Seed the
value must not change until the directory name changes". Is that really
referring to just th
Thanks for the info Peter, I will write a condition that is only checked on
installation.
Kind Regards,
Natalie Carr
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Wednesday, December 19, 2012 3:36 PM
To: General discussion for Windows Installer XML toolse
The burn/bootstrapper has two buttons:
Install and Close
Should be:
Install and Cancel
Since if you click Close you get a message box asking if your sure you want
to "cancel"...
Steve
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/bootstrappe
Thanks John for explaining it in detail I know others are appreciative as
well... used to C++ and C# logic ;)
-Original Message-
From: John Ludlow [mailto:john.ludlow...@gmail.com]
Sent: December-19-12 11:03 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX
Glad it works for you. To explain the logic, it's adding a clause to
each condition so that it will resolve to true if you're on the
*other* architecture. So:
Installed OR (SQLSYNCX64SEARCH > "0" AND VersionNT64) OR (NOT VersionNT64)
This is the x64 search, and resolves to true under the fol
Launch conditions always run, including during removal. Usually, you'd use
the condition: Installed or ... if you want to write a condition that's only
checked at first-time installation.
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 19 December 2012 15
John, Rob, Peter,
Thanks so much for your help... the below from John works like a charm!
Can't get my head around the logic but it works...
Steve
-Original Message-
From: John Ludlow [mailto:john.ludlow...@gmail.com]
Sent: December-19-12 9:24 AM
To: General discussion for Windows Insta
Hi can anyone tell me what is wrong with my conditions? I thought they were
correct as I only want the condition message to be evaluated on install and
not on uninstall but it is still being evaluated on uninstall.
Kind Regards,
Natalie Carr
--
What I do is to always maintain the bundle version the same as the main
msi package...
Also I created a custom wixstdba.dll to which I added:
BOOTSTRAPPER_RELATED_OPERATION_NONE == operation
in OnDetectRelatedBundle():
if (!m_sczPrereqPackage &&
BOOTSTRAPPER_RELATED_OPERATION_DOWNGRADE =
I've the same problem.
I've a bundle v. 1.0.6 with msi v. 1.0.6 installed.
Then I installed a bundle v. 1.0.6 with msi v. 1.0.7 , the upgrade works but
there's also a second entry in the ARP.
If I install a bundle v. 1.0.7 with msi v. 1.0.7 the upgrade works also but
after that the bundle uni
That would only work at build time, if you were compiling an x86 MSI
and an x64 MSI.
I think you just need to extend your condition to something like this:
Installed OR (SQLSYNCX64SEARCH > "0" AND VersionNT64) OR (NOT VersionNT64)
Installed OR (SQLSYNCX86SEARCH > "0" AND NOT VersionNT64) O
Then I will have to use $(var.Platform) <> "x86" that should work
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: December-19-12 5:11 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Registry search and condition message
VersionNT64 is undefined on a 32-bit OS so
Installed OR (SQLSYNCX64SEARCH > "0" AND VersionNT64)
would be
FALSE or (something AND FALSE) === FALSE
which would cause the message to display.
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 19 December 2012
My approach to the problem is to just detect the problem during installation
and inform the user about it. If there are files found on the target folder
after the previous version should have been uninstalled (after
RemoveExistingProducts step) then abort the installation. More details:
http://stac
27 matches
Mail list logo
