Hi
As part of patch installation I am using the ExecuteSQLString CustomAction to
modify Database Schema and also recreate stored procedures.
Due to some SQL connection issues, the connection failed to the SQl server, but
instead of erroring out immediately it waited 17 hrs to error out.
Is ther
I have a really simple MSI that installs a bunch of files and then creates
and starts a service. One of the files it installs ( privately to the
installdir ) is log4net.dll and is a dependency of the service.
I'm getting bug reports from dev that occasionally the service won't start.
The roo
Hi guys,
I want to use the WixUI_Advanced sequence so that I can easily support per
machine and per user installation in the same package in order to install a
VSIX package. I have added some custom tasks to ensure that the default paths
for the two scopes point to the correct places for VSIX v
Hello Yan
I can't see anything wrong with your test app (I will give it ago myself
tonight and get back to you on that). In regards the SQL Logging - I don't
think there is a way to up the level. It sounds as though it is not finding
the SQL instance, or is being blocked.
Mean time a coup
Thanks for the feedback Phil.
I think what threw me was that if I install my COM server to the 32-bit
registry and then use the default command prompt in 64-bit Win 7 to execute a
VBScript client for this COM server, it fails (presumably because the default
command prompt is 64-bit and it can'
Hi,
Is it possible to customize and localize the first UI screen that shows up
if BA needs .Net and it isn't installed?
Also, is there a way to provide localized versions of the .Net license in
the wix variable "WixMbaPrereqLicenseUrl"?
Thanks,
Shruthi
--
View this message in context:
http://w
why not block a x86 installer on x64 and vice versa ?
When going the way to block a msi in presence of another following
approach might be helpful. Not tested but should illustrate a possible
approach:
where UpgradeCodeOfX64Package is the UpgradeCode GUID of
Hi,
Thanks for your answer! I have been trying long and hard, but this is what i
get in the log:
-
Project "C:\Project\xxx\NEW-UPGRADE-VS2010\Setup\Deploy.proj" (Patch
target(s)):
Target Patch:
Touching "xxxPatch\xxxPatch.wixproj".
Building patch
cscript WiLang
I was looking for some help with the following:
I've built the installer to request a value from the user before doing
initial installation. I then store this value in a registry location. If
the user then does a 'Change' installation, I allow them to change the value
(it's a directory path), and
The MSI SDK says "a 32-bit package consists of only 32-bit components" so
you're not really playing by those rules. There's also this:
http://blogs.msdn.com/b/heaths/archive/2008/01/15/different-packages-are-required-for-different-processor-architectures.aspx
If you have 32-bit and 64-bit cl
Nope, Wix does all that for you.
-Original Message-
From: Stephen R Cook [mailto:stephen.r.c...@dom.com]
Sent: 12 October 2011 17:20
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] CloseApplication
But don't you have to put something in the InstallExecu
But don't you have to put something in the InstallExecuteSequence like
?
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Wednesday, October 12, 2011 12:11 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] CloseApplicati
This is what we use:
?XXX.exe = 3 and ($XXX.exe = 2 or $XXX.exe = 4)
where XXX.exe is the component Id of the exe.
It works for upgrade as well as removal because we use an early scheduling of
RemoveExistingProducts (which is the default when using ) and
that removes the existin
I am working on a silent installer for an application and I need to be able to
call the WixCloseApplications custom action on uninstall and upgrade. The
installer is set to upgrade a previous version. I can get it to close the
application when I am upgrading, but not uninstalling.
--
Hi,
I want to block installation of 32 bit installer if 64 bit installer is
already installed on same machine. Is there ant straight way in Wix to
detect the platform of a installed package ?
Thanks in advance.
Regards,
Sanjay Rao
-
I believe I have some more information about this after further testing.
Basically, if I start up a 32bit command prompt (%windir%\SysWoW64\cmd.exe)
from my 64bit machine, and run my VBScript, everything works fine. I would have
thought that since my .NET class can natively run on either archite
Ok, I've spent quite some time investigating and researching, but with no
luck.
@Michael, the server logs are empty. There's simply no trace during the time
slot my installation runs and fails. Maybe, there's a "verbose" mode or
something?
@David, I tried using the profiler (although it is a thir
If your MSI is 32 bits then you don't use HKCR\Wow6432Node\CLSID, just
HKCR\CLSID.
The Wow6432Node is required in Windows x64 to separate the x64 and the x86
registry; Look for Registry redirection in the MSDN library for more info :)
Best regards,
Albert van Peppen
Senior System Engineer
Ins
18 matches
Mail list logo