We define _USE_RTM_VERSION when compiling all custom actions (well,
our lone CA) and include the following MS merge modules ... haven't
come across any issues to date with many thousands of customers...
although we might just be lucky ;)
Merge Id=MS_Merge1
Try http://www.robmensching.com/ :)
On Thu, May 27, 2010 at 7:51 PM, Francesc Castells
fcaste...@dgtexperts.com wrote:
Hi,
I was hoping to find a WIX expert to help me with my installer needs. I
posted jobs at oDesk and Elance and I tried several developers and after
several months and quite
The problem is that the ICE isn't smart enough to tell that the conditions
are mutually exclusive. It sounds like you have exactly what you want. You
need to let the ICE warnings go. smile/
On Thu, May 27, 2010 at 12:10 AM, Thomas Due t...@scanvaegt.dk wrote:
Hi,
I think I need to supply a
Hi WiX Community,
Does anyone know if it is at all possible to get the MSI database
codepage at runtime?
The session.Database.CodePage throws exception... The MSDN says you
should export tables (wtf???) in order to determine the codepage -
that's probably why session.Database.CodePage fails from
Hi there,
I have an ini.-file that is not divided into sections. Looks like this:
# Hostname of COSIMA
de.docufy.cosima.ui.parts/cmshost=localhost
# Port of COSIMA host
de.docufy.cosima.ui.parts/cmsport=443
# Start XMetaL with tag-view
de.docufy.xmetal.ui/startwithtags=true
# switched to HTTPS
We had a similar problem and ended up writing a TemplateFile extension in
http://msiext.codeplex.com.
dB. @ dblock.org
Moscow|Geneva|Seattle|New York
-Original Message-
From: Jonas Kahlert [mailto:jonas.kahl...@docufy.de]
Sent: Friday, May 28, 2010 7:34 AM
To:
Hi everybody,
we've just encountered a problem with our WiX setup when using shared
libraries. We have two installations:
- first one is installing only one shared component SharedBase.dll
- second one is installing two shared components SharedBase.dll and
SharedAdvanced.dll
The issue is, when
Unless I'm missing something, that's MsiGetSummaryInformation() and
MsiGetSummaryInfoGetProperty() and associated Win32 functions, or the scripting
Installer.SummaryInfo etc
Phil Wilson
-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net]
Sent: Friday, May 28, 2010
Hi,
We are facing installation problem for VSTO excel add in on Windows 2008
server
The addin we are registering is available only for admin user and not
for non admin user.
We changed the registration key from HKCU to HKLM still the add ins are
not available.
Is any one faced same problem?
There are two codepages in an MSI database: the database codepage, and the
summary info codepage. They can be different, and there are circumstances
where the valid values for each are different as well.
The functions that Phil mentions retrieve the summary info codepage, not the
database
Which version of Office are you targeting?
If it is Office 2003, it won't work.
If it is Office 2007, HKLM VSTO add-ins were not supported when RTM shipped but
were enabled later via an update (KB976477). Even if you have the update you
have to explicitly enable HKLM registered VSTO add-ins by
I am using Office 2007. We found problem on Windows 2008 server after
installing patch KB976477 excel not starts.
I also created separate installer but it not installs the add in for all
user. I am going to try
HKLM\Software\Microsoft\Office\12.0\Common\General\EnableLocalMachineVST
O = 1.
Unless you are using MSI 5.0 or higher, any/all files must be in the package
involved in the installation transaction. So, the general rule would be to
include SharedAdvanced.dll in both installations, but condition the component
containing it to only install if the second package is (or is
That sounds like this rather strange procedure:
http://msdn.microsoft.com/en-us/library/aa368277(VS.85).aspx
To determine the code page of a database, call MsiDatabaseExport with
hDatabase set to the handle of the database and szTableName set to
_ForceCodepage. This exports a text file with
These are auto-generated shortnames. I suspect files whose length is greater
than 8 will have these while those that confirm -- as is -- to 8.3 naming
conventions will not. In other words, I do not think you have anything to worry
about and this is expected.
Good luck,
Navid
-Original
Hi Wix users,
before I sink time into authoring installers and testing, I am seeking
your comments wether the following concept could work, or wether I have
missed something.
Assuming I have an INSTALLERA.msi, which consists of the features
MAINFEATURE and DATA1 and DATA2, and another
If you follow the component rules then yes: this should work. The contents
of MAINFEATURE should be identical between INSTALLERA and INSTALLERB,
including the directories used and the GUIDS of the included components, as
well as the associated keypaths which must also be identical.
-Original
17 matches
Mail list logo
