I am using SQL Login sa right now
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Run-scripts-on-remote-sql-server-tp7579668p7579682.html
Sent from the wix-users mailing list archive at Nabble.com.
-
That means they need to install on each and every machine that they want to
configure.
ok ,Thanks
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Configure-diff-machines-by-installing-on-one-machine-tp7579659p7579681.html
Sent from the wix-users ma
Thank's a lot! I already broke my mind and it was so easy!
2012/8/1 jhennessey
> Don't try to set feature states by directly setting the ADDLOCAL property
> from the UI. Instead you should use the
>
> http://msdn.microsoft.com/en-us/library/windows/desktop/aa367537%28v=vs.85%29.aspx
> AddLocal
Thank you for the link. I changed the upgrade install to the same name as the
original install and the upgrade worked fine.
However, this did not solve my initial problem - torch/pyro is not finding a
difference so pyro is not building the patch.
Any other ideas as to how I fix this?
-Orig
You can't change the name of the MSI in a minor/small update.
See
http://kb.flexerasoftware.com/doc/Helpnet/installshield12helplib/MajorMinorSm
all.htm
is only used for major upgrades and won't affect what you're doing
currently.
-Original Message-
From: Jeanne Dixon [mailto:jdi...@cots
Hey,
One of my custom actions is meant to display a dialog, however I keep
getting a Debug Assertion Failed error and it points me to the source, which
is:
ASSERT(afxCurrentResourceHandle != NULL);
Can anyone tell me how to correct this as I'm losing my mind trying to
figure it out.
I don't know if this is related to why no changes are detected, but I put in
the tags and tried to run the msi file as a minor upgrade through the
msiexec command line. When I do that it starts to run the install (as opposed
to giving me the message that a different version already exists), but
It sounds like you've done it right so far.
A patch IS a minor upgrade. A patch just a different way of packaging the
upgrade. By leaving unchanged resources out, you can't do a first time
install with it but it's smaller.
The version number can be different in any field to be different in a mino
How does WiX schedule it's custom actions? Normally CA's are scheduled
for deffered no-impersonate but in the case of intermachine sql execution
using SSPI this would result in the computer account (assuming there is a
domain) trying to authenticate to the remote machine rather then the
Don't try to set feature states by directly setting the ADDLOCAL property
from the UI. Instead you should use the
http://msdn.microsoft.com/en-us/library/windows/desktop/aa367537%28v=vs.85%29.aspx
AddLocal and
http://msdn.microsoft.com/en-us/library/windows/desktop/aa371210%28v=vs.85%29.aspx
Rem
I've done this type of installer many times before and whoever is giving
you the requirements is off in the weeds.
What you want is an installer with three feature. Web, App, Data. You
run the installer on 'n' number of machines and installing the features as
needed for your deployment sce
I built the first install with the old file, then changed the file and built
the second install. Individually each install works fine, and the second
install has the correct file with it. So I think the MSIs have been built
properly. I also have changed the version number - in the first one it i
Hi All,
I have created a installer which i suppose to run some sql scripts on SQL
server which is located in network.
When I am using Server installed on local machine then its working fine.but
if I use remote server then it throws exception failed to connect to server.
I also tried like I used my
How you build is up to you. As long as the MSIs that come out of the build
contain the correct files, then it's a valid method. From your description,
it's not clear if you're building the MSI before or after you change the file
in the first ads_install directory, which might be where you're going
I'am using WixUI_Mondo set, wix 3.6, Windows XP SP3,. On the SetupDlg I
want to have two buttons: ClientButton,ServerButton. They will initiate
installing two different configurations with muttually exclusive features.
Here is mya code:
OLDARPFOUND
1
It is good to know I don't have to update all files with a version number.
I redid my pyro statement to use "ADSPatch" but I still get the same error.
I am obviously missing something. What I have tried to do is use the same
directory for both builds. I have a directory (I'll refer to it as the
You can't. Windows Installer is a single machine deployment technology.
You'll need to use some system in conjunction with it, that's capable of
network deployment, such as GPSI or SCCM.
-Original Message-
From: aman jha [mailto:er.amanjha...@gmail.com]
Sent: 01 August 2012 08:33
To: wix
I found your original message and it looks like you're updating a PDF. Those
don't have Windows version resources, so ignore me there. You can remove
those edits you made with Orca.
The patchbaseline in the patch.wxs has the Id "ADSPatch". This Id must match
the -t argument passed to pyro, which y
The BoostrapperApplicationData.xml (included with your BA) contains lots of
such information.
On Tue, Jul 31, 2012 at 12:16 PM, John M. Wright wrote:
> I've created a .net-based custom UI using a class
> extending
> Microsoft.Tools.WindowsInstallerXml.Bootstrapper.BootstrapperApplication
> (MBA).
I like to use the AssertSz(FALSE, "debug here") from dutil. It'll give you
a nice message including the process id to attach to.
On Tue, Jul 31, 2012 at 1:15 PM, Adam Kadzban wrote:
> In C# I have often used System.Diagnostics.Debugger.Launch(). If you have
> Visual Studio installed it pops up a
Hi All,
I am developing an Installer using WIX, The project for which I am creating
the installer can be splitted into multiple machines.
1. Application server : where some windows services will be installed.
2. Web Server : where Website will be installed and hosted in IIS
3. DB Server : where D
21 matches
Mail list logo
