oing to revert back to build 5006 for now. Is this a bug that I should
report?
- Don Benson -
Tribute Inc.
CONFIDENTIALITY NOTICE: This email and any files transmitted with it are the
property of Tribute Inc. and/or its affiliates. The contents of this
communication are confidential an
Windows Installer automatically handles translating the ProgramFilesFolder
property for 32-bit vs. 64-bit platforms. Are you using an XMLFile element
to set the web.config value? Use the [ProgramFilesFolder] property within
the XMLFile element, and you should get what you want.
- Don Benson
g
> on the XML file before it was modified by the IIS custom action, even though
> the IIS custom action was earlier in the sequence). A flush operation was
> added to the custom action to fix this scenario in 3.5, but 3.5 is still
> early on and it's hard to recommend it at this poin
, a bug in the Wix extension, a problem in .NET,
or what? Do I have any workaround options?
Oh, I almost forgot... this is built with WIX v3.0.5006 (built 06-Feb-09).
- Don Benson -
CONFIDENTIALITY NOTICE: This email and any files transmitted with it are the
property of Tribute Inc. and/or i
n the command line. Windows limits
commands to 2048 characters.
Here's a link where somebody has done a similar type of thing using a VBScript
custom action:
http://blog.coretech.dk/section/scripting/vbscript-scripting/automated-windows-installer-properties-from-ini-embedded-vbscript/
- Don
ry to fix it. Upgrades and
removals are still a complication.
Option 1 seems to be the simplest choice for now, and I do have some time
pressure to get the installation working soon. I would appreciate any other
ideas or thoughts on my options.
Sincerely,
- Don Benson -
CONFIDENTIALITY NOTICE: This
That is what I did, and it was easy to do.
So what is the purpose of the DLLPathFromGAC attribute on the ComPlusAssembly
element? It doesn't seem like it has any use as of build 3.0.5006 unless you
are using to register a DLL that already was previously installed, and I'm not
sure what installa
If you only need to do this manually one time, the Dark utility with the /x
option will decompile an MSI and extract all of the binary components,
including any embedded CAB files. You can then use a standard "archive" tool to
extract files from the CABs.
> -Original Message-
> From: Ma
ing to do with Fusion, but I am at a loss to
> tell what.
>
> Are you saying that you have had it working with a previous WiX build
> BTW?
>
> -Original Message-
> From: Don Benson [mailto:dben...@trulinx.com]
> Sent: Friday, February 20, 2009 11:06 AM
> To: Gener
sHost\0.0.0.1_CF47A01D50A7B0F5\MyProduct.EnterpriseServicesHost.dll,
or something like that. The Previous file activity involved the
C:\WINNT\GAC_MSIL tree. That seemed not right to me, but I don't know anything
about the Fusion API.
- Don Benson -
> -Original Message-
> Fro
I think the simplest solution for you is the reverse condition:
NOT REMOVE ~= "ALL"
This condition will be true for all states except when the product is being
removed.
> -Original Message-
> From: Mr_Geva [mailto:mail.g...@gmail.com]
> Sent: Monday, February 23, 2009 1:20 PM
> To: wix-u
This suggestion is problematic when the installation incudes .NET assemblies
that are registered in GAC or native DLLs registered as side-by-side (SxS)
assemblies. If either of these assemblies does not change in the major
upgrade, the assembly disappears after the major upgrade, leaving you with
of features to be available on the ComPlusApplication element.
Are these ideas totally incompatible with how Windows Installer works?
Sincerely,
- Don Benson -
From: Neil Sleightholm (via Nabble)
[mailto:ml-user+58265-1563573...@n2.nabble.com]
Sent: Monday, February 23, 2009 4:18 PM
To: Don Benson
Subject: Re
Are you using the ComPlus extension to manage the COM+ application(s). I have a
similar line, except I am not putting a condition on the RemoveExistingProducts
action.
Sincerely,
- Don Benson -
CONFIDENTIALITY NOTICE: This email and any files transmitted with it are the
property of T
ts of examples of
how you do this for the .NET Framework. You'll need to figure out a command
line or API in Windows you can use to automate installing the missing features
and incorporate that into the bootstrapper. I cannot really help with that
aspect of your question.
- Don Benson -
s (wxl) for the different
cultures we need. This broke the server compile. The localized clients are
generated in a separate subfolder for each culture, but the server build
breaks because it is looking for the client MSI in the folder that is the
parent to the culture folder.
Should this be working
If WiX had a built-in variable for the culture that is currently being
built, I'd be able to declaratively define the file source using that. Is
this something that I should enter as a feature request in the issue
tracker, or is this not technically feasible?
- Don Benson -
On Sat, Mar 7,
You don't need a custom action. Check out the TrueType attribute on the File
element.
On Mon, Mar 9, 2009 at 11:10 PM, xfishxi wrote:
> hi
>
> I'm use wix to generate my MSI Installer, our product needs to use two
> Fonts(SIMYOU.TTF and STHUPO.TTF), so we
>
> need to install these two fonts into
nd writing your scripts to not
reference a database at all. Instead of MyDB.dbo.MyTable, use dbo.MyTable.
The osql command has a command-line parameter to define the database to use.
If you use this parameter inside the custom action, your script will be
applied to the correct database.
- Don Benso
>
>
> am not able to locate the cause of this error, can any one help me on this
> ?
>
> in sql script i am adding few tables into my database "[ORGANIZATIONDB]"
>
> i am not using "USE [ORGANIZATIONDB]" insode sql script, which i guess it
> takes aut
event:
INSTALLDIR_VALID<>1. You will need an error dialog to explain why the value
is not valid.
The third event is the action you want when the directory is valid. It
should be conditioned with INSTALLDIR_VALID=1.
With this technique, the push button is always enabled.
- Don Benson -
On Wed,
Where to schedule the CA depends on how you intend to use the results. If
you want to use it to prevent installation, you should schedule it before
LaunchConditions as an immediate CA and use a Condition element based on the
property set by the CA.
- Don Benson -
On Sun, Mar 8, 2009 at 11:43 PM
Look at the CustomAction/@Execute attribute. This should be set to
firstSequence or Immediate. If you have a UI on your installer, I would use
firstSequence, in which case you will want to schedule the custom action in
both InstallExecuteSequence and InstallUISequence.
- Don Benson -
On Wed, Mar
If you use SQL Profiler to monitor the RPC calls to the database server, you
should be able to capture the full SQL statement that is being used to
create the database. Knowing the statement that was sent to the SQL Server
will help with figuring out what is going wrong.
- Don Benson -
On Thu
event installation when the
OS is below a certain level and include a message to indicate they should
use Windows Update to get the latest service pack and security updates.
- Don Benson -
On Thu, Mar 12, 2009 at 8:51 AM, Holmgren Mathias
wrote:
> I've read up a bit on bootstrappers, but
Try putting a condition of "Not Installed" on the element where you
sequence the action.
- Don Benson -
On Thu, Mar 12, 2009 at 12:57 PM, wimpos wrote:
>
> Hi
>
> I have a custom action in my wix installer executing a powershell script.
> This scripts adds a line to
public
properties:
msiexec /i MyInstaller.msi /l*v InstallDebug.log LOGVERBOSE=1
INSTALLDIR="D:\Custom Programs\My Program"
- Don Benson -
On Thu, Mar 12, 2009 at 5:16 PM, Sudripta Nandy (Sarangsoft Corporation) <
v-su...@microsoft.com> wrote:
> In my setup program, the user needs
I haven't tried this, but what if you make that registry value a the key
path of its own component and mark the component as Permanent. I suspect
that will not be removed when the app is uninstalled.
- Don Benson -
On Thu, Mar 12, 2009 at 9:00 PM, Andrew Lowe <
al...@immersivetechnolo
for the PIA.
I hope that my suggestions are appropriate for your scenario. If I've made
any poor suggestions, hopefully somebody else will chime in.
- Don Benson -
--
Apps built with the Adobe(R) Flex(R) framework and Fl
within the to instantiate the appropriate DLL.
This would be invisible to the user and make a simpler MSI.
- Don Benson -
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with
ice 2003 PIA:
- Or condition
- Not condition
- Registry check for Office 2003
- And condition
- Registry check for Office 2003
- Registry check for Excel 2003 PIA
The two Registry checks for Office 2003 will be i
ow progress bar during custom action.
>
The Windows Installer documentation seems to indicate that the progress bar
does not work after InstallFinalize. Check out the following, link,
especially step 9.
http://msdn.microsoft.com/en-us/library/aa367525(VS.85).aspx
-
I recently submitted a feature request on the bug tracker for this kind of
variable.
On Tue, Mar 17, 2009 at 9:40 AM, Alastair Smith
wrote:
> Hi there
>
> I'm building an installer for multiple cultures. Currently, the EULA is
> specified using the WixVariables element in the wixproj file as fol
cutable that runs at the end of an installer. My
ProgessText for the custom action includes the text "This may take several
minutes. Please be patient." The users don't get a progress bar, but their
expectations are set.
- Don Benson -
On Wed, Mar 18, 2009 at 1:57 AM, Michael wrote:
It is issue 2677254.
On Wed, Mar 18, 2009 at 7:30 AM, Alastair Smith
wrote:
> Do you have a link available for this feature request? I can't seem to
> find it on the SF tracker.
>
> -Original Message-
> From: Don Benson [mailto:dbenso...@gmail.com]
> Sent: 1
n),
> $(Platform), etc.
>
> I see in wix.targets that there is a %(EmbeddedResourceWithCulture.Culture)
> metadata variable referenced (on line 1549, amongst other places), but I
> can't seem to successfully use it in my .wixproj files.
>
> Cheers
>
> Alastair
>
>
n with or without the UI, the action should be
scheduled in both sequences. You can set CustomAction/@Execute to
"firstSequence". This ensures that it won't run again in the Execute
sequence if it was already set in the UI
nent, so we don't remove them and break another
application that might also be depending on them.
- Don Benson -
--
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Down
On Thu, Apr 9, 2009 at 12:54 PM, MacDiarmid, James D <
james.macdiar...@eds.com> wrote:
>
> Where would I normally find a merge module like this, or is this
> something I would need to create myself?
http://tinyurl.com/cmbtq
e purview of Windows
Installer.
- Don Benson -
--
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf
Windows Installer defines the UPGRADINGPRODUCTCODE property when a product
is being removed as part of a major upgrade. A typical condition you might
use is "NOT UPGRADINGPRODUCTCODE".
- Don Benson -
On Thu, Apr 16, 2009 at 8:00 AM, Jeff Reed wrote:
> I apologize about the prev
l always have the same IDs for
all the components.
- Don Benson -
--
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conf
42 matches
Mail list logo
