Hi Daniel,
1) For a COM dll, heat should generate the appropriate registry data.
2) For a COM EXE server, heat will not generate the the registry data but
you can do the following.:
a) Use RegSpy2 to extract the registry data into a reg file.
So if my COM exe is called TestCOM.exe, you would
Hi all,
I have the following Custom Action, based on reading the docs...
CustomAction Id=CA_LaunchLicenceManager
Directory=ProgramFilesFolder
ExeCommand=[ProgramFiles64Folder]\LicenceManager\MyLicenceManager.exe
Return=ignore /
And it is supposed to be called
No. It is available in the base installer itself. I cant event execute the
sql script while installing the patch. I tried with sql string also. It is
not working.
--
View this message in context:
I haven't used the SQL custom actions. Have you tried generating a verbose
installation log ?
-Original Message-
From: Nangai [mailto:thangananga...@iinterchange.com]
Sent: 27 July 2011 12:44
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Unable to execute SQL script from
Ok I think I found the issue. The ExeCommand is wrong, it should actually be...
CustomAction Id=CA_LaunchLicenceManager
Directory=ProgramFilesFolder
ExeCommand=[ProgramFilesFolder]LicenceManager\MyLicenceManager.exe
Return=ignore /
Damn paths. That then works as
Hi,
I have a large WiX project in visual studio 2010 and I am having trouble
finding where values in preprocessor variables come from. When I go to Project
Properties - Build and look at Define preprocessor variables: there are
variables in this format: Product=$(Product);Version=$(Version).
Hi Andreas,
Unload your WiX project in VS 2010 (right click project) and then unload it.
Then select project again right click select Edit
You should see a PropertyGroup element and each sub-element within it, is
a property which can be referenced by eg $(Product)
You should find some values
Forgot to add that the DefineConstants element conatins the assignments of
properties to preprocessor variables.
Anil.
On Wed, Jul 27, 2011 at 2:54 PM, Andreas Vestlund
andreas.vestl...@sekonden.se wrote:
Hi,
I have a large WiX project in visual studio 2010 and I am having trouble
finding
The wix.targets set this all up for you behind the scenes. You should see
them if you run MSBuild with a very verbose output.
On Wed, Jul 27, 2011 at 6:54 AM, Andreas Vestlund
andreas.vestl...@sekonden.se wrote:
Hi,
I have a large WiX project in visual studio 2010 and I am having trouble
Hi Joseph,
Have a look at this link about adding the WiX project to your VS 2010
solution.
http://www.havecomputerwillcode.com/blog/?p=421
Cheers,
Anil.
On Tue, Jul 26, 2011 at 4:24 PM, Joe Tilley jtil...@fwmurphy.com wrote:
Hello,
This is my first time using the mailing list, so please
My installer has a dialog that lets the user choose a feature. Based on that
choice ADDLOCAL is modified via a custom action.
The problem seems to be that WiX has insufficient granularity with regards to
scheduling UI actions. The problem I can't seem to solve is precisely how to
schedule this
As I said I'm not clear on the details having never tried it, but your invalid
handle error suggests that you are not using an immediate custom action to do
this.
Phil Wilson
-Original Message-
From: Uma Harano [mailto:uhar...@esri.com]
Sent: Tuesday, July 26, 2011 8:54 AM
To:
If you allow users to browse to a different install folder, that changed path
usually applies to the ProgramFiles folders, so beware of changed locations. A
path to the exe based on [#file key] is more reliable because it works wherever
the file is installed.
Phil Wilson
-Original
Upon further research I zeroed in on the primary culprit for the difficulties
involving ADDLOCAL. The problem lies with the InstallUISequence itself,
particularly the location of CostFinalize in the sequence. Any sort of GUI with
multiple dialogs is very likely to require the Directory Manager.
I'm building a bootstrapper using DTF. I'd like to set the messageFilter to
Installer.SetExternalUI() to be equivalent to the msiexec /l*v logging option
but I can't quite figure out which combination of InstallLogModes values to
use. At one point, I had nearly all values but I didn't see
Greetings all,
is it possible to set the Enable 32-Bit Applications flag for an apppool im
creating withing the msi ( under iis 7 ) via Wix?
--
Got Input? Slashdot Needs You.
Take our quick survey online. Come on, we
I don't see anything mentioned in IIS extension schema that would support this
(see http://wix.sourceforge.net/manual-wix3/iis_xsd_webapppool.htm). If the
documentation is out of date, then maybe someone can chime in. I believe you
might need to run appcmd.exe out-of-band or directly modify
I based my code on this:
http://stackoverflow.com/questions/3287626/wix-installer-remove-files-on-uninstall-but-not-on-upgrade
I saw no complaints about the suggested answer so I assumed it worked. But when
I adapted to my code it does nothing.
In product.wxs:
InstallExecuteSequence
There's a lot of other stuff that needs doing for upgrades to work, and you
haven't said if you actually have it, such as upgrade specifications in your
WiX.
I'd look at all your FindRelatedProducts actions in your install to see if they
report anything about finding older versions of your
We use this... It seems to work well for us...
!-- Custom Action used to setup the Application Pool for IIS on 64bit or
32bit machines --
CustomAction Id=CfgAppPools64 Return=check Directory=TARGETDIR
ExeCommand=[SystemFolder]inetsrv\appcmd set apppool
/apppool.name:quot;XPJquot;
I've yet to roll this into production but under my circumstances I went
with an alternate option of using Application and Assembly manifests.
This will not work with out of process (exe) COM servers, but it will
work with both native and managed assemblies.
The manifests leverage on SxS / RegFree
21 matches
Mail list logo
