> Should I be manually changing the product code of each instance
every time? Or should the base product code be static also? Or ought it not
matter?
Follow the Windows Installer documentation guidelines as for when to change
your PC:
http://msdn.microsoft.com/en-us/library/aa370579(v=VS.85).aspx
If the transform is to be applied during an installation you must use the
CreateTransformSummaryInfo method to populate the summary information stream.
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Friday, September 02, 2011 1:46 PM
To: wix
Anyone have any idea as to how to go about specifying the position within an
XML document to insert a node, relative to some other node?
SharePoint has a 'wss_minimaltrust.config' file which contains a
firstmatchcodegroup construct (reference
http://msdn.microsoft.com/en-us/library/system.secu
I think this is kind of odd:
Which compiles just fine.
What I want to be able to do is have the preprocessor condition logic based on
whether or not an environment variable is set.
Forexample:
But I cannot use because in the case when
the environ
A launch condition probably should not be used for this. Launch conditions
should be things that verify things at first launch, not at some pre-determined
time well into the installation UI.
You could use a Custom Action to accomplish this, or perhaps better yet, just
hide the feature appropri
Here's the key point from the SDK:
* To keep the nonfile data of each instance isolated, the base package
should collect nonfile data into sets of components for each instance. The
appropriate components should then be installed based on conditional
statements that depend on the instance identifie
Regarding properties from the UI not retaining their values into the execute
sequence, look into 'SecureCustomProperties', ref:
http://msdn.microsoft.com/en-us/library/aa371571(VS.85).aspx
-Original Message-
From: David Drake (Excell Data Corporation) [mailto:a-ddr...@microsoft.com]
S
t there and the file is then
written as expected)."
The concept you'll want to look up here is "transitive components".
Reference: http://msdn.microsoft.com/en-us/library/aa372462(VS.85).aspx
-----Original Message-
From: John Nannenga
Sent: Thursday, November 05, 2009
This might get the job done for you...
?Foo.exe=3 AND NOT PATCH
This would work if your upgrade process will install missing files.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Thursday, November 05, 2009 10:40 AM
To: 'General discussion for Windows Inst
It's important to keep in mind the DTF (for the most part) provides a managed
interop around the windows installer APIs. You'll still need to become
intimately familiar with [
http://msdn.microsoft.com/en-us/library/aa368786(VS.85).aspx ] and how to
handle all the messages and compute the prog
Not sure of the terminology here, but if your checks are in the LaunchCondition
table, they execute in an indeterminate order:
Ref: http://msdn.microsoft.com/en-us/library/aa369752(VS.85).aspx
Specifically,
"You cannot guarantee the order in which the launch conditions are
evaluated by
You likely don't need your own CA for this, check out XmlConfig or XmlFile.
Your problem here is likely that you get a FileNotFoundException or something
similar which is due to the fact you have your CA scheduled to execute in the
"immediate" sequence and scheduled after "InstallFiles" which do
Take a peek at CurrentSession.GetMode, passing it what you're interested in
detecting. InstallRunMode.Scheduled I believe is 'deferred',
InstallRunMode.Commit is commit, etc...
For immediate I use InstallRunMode.Operations || InstallRunMode.Maintenance.
-Original Message-
From: Tom Cr
...\wix\src\ext\NetFxExtension\wixlib\NetFxExtension.wxs
-Original Message-
From: Lloyd Dupont [mailto:l...@galador.net]
Sent: Monday, June 22, 2009 6:14 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixNetFxExtension / how to check for .NET 3.5 S
Features and components both have "state" information which indicate the
current state [status] and requested action of the feature / component.
Refer to:
http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx
and perhaps this:
http://msdn.microsoft.com/en-us/library/aa3678
I'm not familiar with "mailto:shrinuen...@gmail.com]
Sent: Wednesday, April 29, 2009 7:20 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] feature and component installation
Hi,
we have different dotnet custom actions which we give under the component
tag. like following\
we hav
mp...
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Tuesday, April 28, 2009 7:57 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX compiler extension and WiX Lib...
John
Reference this:
http://msdn.microsoft.com/en-us/library/aa371662(VS.85).aspx
and probably this... INSTALLLEVEL:
http://msdn.microsoft.com/en-us/library/aa369536(VS.85).aspx
From: MYFLEX [shrinuen...@gmail.com]
Sent: Tuesday, April 28, 2009 6:57
Found my issue and resolved it...
Cheers...
From: John Nannenga [john.nanne...@microsoft.com]
Sent: Tuesday, April 28, 2009 2:18 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] WiX compiler extension and WiX Lib
Howdy folks;
I'm building a WiX compiler extension. I've over-ridden
WixExtension::GetLibrary to return my custom built WiX Lib.
My WiX Lib has the following in it:
When I build an MSI that references my compiler extension, I g
Reference the "TerminalServerAware" attribute of the CustomAction element in
the WiX help.
TerminalServerAware YesNoType This attribute specifies controls whether the
custom action will impersonate the installing user during per-machine installs
on Terminal Server machines. Deferred execution
According to the Feature Table in the SDK:
http://msdn.microsoft.com/en-us/library/aa368585(VS.85).aspx
Neither Title or Description are format-able fields
-Original Message-
From: Jon Drnek [mailto:jon.dr...@vibrationresearch.com]
Sent: Wednesday, March 25, 2009 9:45 AM
To: wix-users@
Presuming we're all talking about the basic UI dialog...
Time remaining: {[1] minutes }{[2]
seconds}
Product Name is being configured on your
computer.
Reference:
http://msdn.microsoft.com/en-us/library/aa368554(VS.85).aspx
-Original Mes
Take a look at configurable merge modules in the SDK...
http://msdn.microsoft.com/en-us/library/aa368027(VS.85).aspx
From: Reuss, Matthias [matthias.mr.re...@siemens.com]
Sent: Monday, March 23, 2009 10:25 AM
To: General discussion for Windows Installer XML
Quick question...should this work after the product is installed i.e., in
maintenance mode or even in a patch?
A quick implementation we've messed with results in a read only session object
in these situations; before we get heavy into looking into this, wanted to see
if you knew off the top of
FDI Error code of 11 means user aborted; I found that interesting so I dug into
this a bit...
sfxca\Extract.cpp :: ExtractCabinet
Comments note that the destination directory (szExtractDir) must
already exist (and should be empty)
sfxca\Extract.cpp :: FNFDINOTIFY...
casefdin
Ref: INSTALLLEVEL http://msdn.microsoft.com/en-us/library/aa369536(VS.85).aspx
Feature Table http://msdn.microsoft.com/en-us/library/aa368585.aspx
-Original Message-
From: xcjjohansen [mailto:x...@saxobank.com]
Sent: Thursday, February 26, 2009 10:05 AM
To: wix-users@lists.sour
ect.
Neither version of the 3rd CAB are sorted in any recogniaseable way, they're
just predictably randomly different from each other.
John Nannenga wrote:
>
> Ref: http://msdn.microsoft.com/en-us/library/aa368060(VS.85).aspx
> -- SDK documentation pertaining to this issue.
Ref: http://msdn.microsoft.com/en-us/library/aa368060(VS.85).aspx
-- SDK documentation pertaining to this issue.
Where the rubber then meets the road [within WiX] is within your directory
elements...if you have any file additions / removals within your directory
table, that impacts file
Your CA isn't running because although you've defined the custom action within
Product.wxs you haven't scheduled it for execution (you have no sequences
defined which would invoke your CA).
For example...
.
.
.
1
-Original Message-
From: jballe [mailto:j...@visionpe
Take a peek at the "Preprocessor" section in the WiX.chm file. It has all
sorts of information in this regard, complete with examples.
-Original Message-
From: sandun css [mailto:sandun...@gmail.com]
Sent: Wednesday, February 25, 2009 2:59 AM
To: wix-users@lists.sourceforge.net
Subject
DateAdd returns a date, Session.Property must take a string, hence the type
mismatch error you were likely receiving.
Try this instead... Use FormatDateTime to convert your date object...
SUB CalcMigratorDate
Session.Property("OLDDATE") =
FormatDateTime(DateAdd("d",-30,DateValu
You can control the progress bar via messaging...
Reference: http://msdn.microsoft.com/en-us/library/aa371672(VS.85).aspx
Use a message type of msiMessageTypeProgress and fill out the record
information as documented for what you want to accomplish.
-Original Message-
From: Neil Sleigh
Try this:
[CustomAction]
public static ActionResult DisplayMessageBox(Session session)
{
session.Log("Begin CustomAction1");
Record rd = new Record(2);
rd.SetString(0, "[1] [2]");
rd.SetStri
Corrected my type-o on the Text element below... had a quote in there that
didn't belong...
-Original Message-
From: John Nannenga [mailto:john.nanne...@microsoft.com]
Sent: Monday, February 23, 2009 11:38 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] update Ho
Same thing works in WiX, only it's XML so you have to use "&" instead of
"&".
"&Next
Alt+N would then be the "accelerator" for the "Next" button.
-Original Message-
From: Richard [mailto:legal...@xmission.com]
Sent: Monday, February 23, 2009 11:31 AM
To: wix-users@lists.sour
Reference:
http://msdn.microsoft.com/en-us/library/aa370905(VS.85).aspx#configuration_properties
'ComputerName' will get you, well, the computer name.
Full name of the machine, I've normally gone after that with a CA of sort...
-Original Message-
From: sandun css [mailto:sandu
The condition of "NOT Installed" means "do this if the product is not
installed".
In maintenance mode the product is installed and upgrading isn't normally
relevant to maintenance mode; so this constraint keeps your CA from running.
-Original Message-
From: ערן גבע [mailto:mail.g...@
If memory serves me correctly (from last August), the issue here lies in the
MakeSfxCA processing. It only writes the Embedded UI entry points if there are
no CAs included in the project.
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent:
That'll work great but be mindful of `Feature`.`Level` = 0.
>From the SDK, "An install level of 0 (zero) disables the item and prevents it
>from being displayed. A feature with an installation level of 0 (zero) is not
>installed during any installation, including administrative installations."
I leave the upgrade code the same for all instances. I have a dialog asking
the user whether they'd like to upgrade an existing instance, or install a new
instance (only if an existing instance is detected).
If the user selects to upgrade an existing instance, I store the product code
of that
What happens when the data value you need contains what appears to be the
delimiter between independent properties within the CustomActionData class?
"semi-colon"...
-Original Message-
From: Rob Mensching [mailto:r...@wixtoolset.org]
Sent: Tuesday, February 17, 2009 10:52 PM
To: Ge
I figured it out. It was classic user error.
-Original Message-
From: John Nannenga [mailto:john.nanne...@microsoft.com]
Sent: Tuesday, February 17, 2009 4:54 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Per user installation HKCU registry keys remain after
un
I'm working on deployment of a managed Word Add-in. Managed Word Add-Ins in
Office 2007 are registered under the HKCU registry hive, hence I'm creating a
per-user installation.
My question is regarding the HKCU registry keys-they are not being removed
during product uninstallation...
Installa
In your patch generation you need to target the patch for all the product codes
[instances] you want it to be applicable to.
Etc...
From: Matt Ziegler [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 20, 2008 3:50 PM
To: wix-users@lists.sourceforge.net; [EMAIL PROTECTED]
Subject: Re: [
Use a configurable merge module.
Ref: http://msdn.microsoft.com/en-us/library/aa368027(VS.85).aspx
From: Castro, Edwin (Hillsboro) [EMAIL PROTECTED]
Sent: Thursday, November 13, 2008 1:56 PM
To: General discussion for Windows Installer XML toolset.
Subjec
Reference:
http://msdn.microsoft.com/en-us/library/aa369786(VS.85).aspx
From: Joshua Chambers [EMAIL PROTECTED]
Sent: Monday, September 29, 2008 6:19 PM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] old installer running?!
Hello!
When I ru
al Message-
From: John Nannenga [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 24, 2008 1:11 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] what setting causes current wix build output to land
in bin\$(Configuration)\en-us versus bin\$(Configuration)
Subject: Re: [WiX-users] what setting causes current wix build output to land
in bin\$(Configuration)\en-us versus bin\$(Configuration) where it always used
to land
Yes, that looks like it won't work. Can you log a bug on this in SourceForge?
Neil
-Original Message-
From: John Nannen
Is this change not compatible with the "List of Supported Project References"?
Before this change, I had a reference in my MSI WiX project to a merge module
WiX project. I then referred to the built merge module via
$(var..TargetPath). This worked just peachy, until this change
was introduc
One way would be to use Dark against your built deliverable.
WiXCop is documented to take WiX 2.0 to WiX 3.0...
http://www.wixwiki.com/index.php?title=WixCop
WiX 1.0 was so long ago (for me), I can't remember much about it... :)
From: [EMAIL PROT
Found the MSIPATCHREMOVE property... Ref:
http://msdn.microsoft.com/en-us/library/aa370348(VS.85).aspx
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert O'Brien
Sent: Monday, September 15, 2008 1:03 PM
To: 'General discussion for Windows Installer XM
FindRelatedProducts, Ref:
http://msdn.microsoft.com/en-us/library/aa368600(VS.85).aspx only runs the
first time the product is installed. Hence, I do not believe it is relevant
for a small update or a minor upgrade.
You can verify this in your scenario by capturing a verbose log file "/l*v
lo
Reference:
http://robmensching.com/blog/archive/2007/09/03/Windows-Installer-4.5-and-the-WiX-toolset.aspx
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Svare
Sent: Monday, September 15, 2008 7:53 AM
To: wix-users@lists.sourceforge.net
Subject: [
There's the MsiSetProperty API Ref:
http://msdn.microsoft.com/en-us/library/aa370391(VS.85).aspx
Or, if you're doing this from a native windows installer UI sequence, through
WiX, you'd make use of the "Publish" element.
Example:
NOT Installed
If you want the property to be available
eir KeyPath is properly detected during the upgrade or patch processing
and in the case of custom actions I've have the correct install pass only
feature & component state conditions in place. Is that a correct assumption.
-----Original Message-
From: [EMAIL PROTECTED] [mailto:[E
FindRelatedProducts:
http://msdn.microsoft.com/en-us/library/aa368600(VS.85).aspx ... only runs the
first time the product is installed. As so, I don't believe it executes during
a patch scenario (so it wouldn't be relevant).
That is also documented as being true for RemoveExistingProducts (o
on install and not on install.
regards
Derekj
John Nannenga wrote:
>
> Launch conditions fire when the condition is false:
>http://msdn.microsoft.com/en-us/library/aa369752.aspx
>
> The property you likely mean to use is "Installed", not "INSTALLED".
>
You may also be able to make use of the following properties:
http://msdn.microsoft.com/en-us/library/aa367536(VS.85).aspx
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Pally Sandher [EMAIL
PROTECTED]
Sent: Thursday, September 11, 2008 8:46
.vcproj references are not supported. Reference the recent thread (last
monday) w/Subject : Add reference to setup project in Visual Studio 2008.
Essentially Justin R notes, "Unfortunately .vcproj references aren't supported
because they're not MSBuild compliant. There is a feature request out
msi" approach to update an existing
install?
-----Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John
Nannenga
Sent: Tuesday, September 09, 2008 7:32 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] does running upgrade
Launch conditions fire when the condition is false:
http://msdn.microsoft.com/en-us/library/aa369752.aspx
The property you likely mean to use is "Installed", not "INSTALLED".
http://msdn.microsoft.com/en-us/library/aa369297(VS.85).aspx
From: [EMAIL
d that to execute a minor upgrade you
need reinstallmode="vomus" not "omus" for this to work. Is that only for the
case of applying a minor upgrade using a "My Deliverable Small Update or Minor
Upgrade.msi" approach to update an existing install?
-Original Mes
How are your features configured?
Pay particular attention to the Feature.Directory_ column of the Feature
table...
ref: http://msdn.microsoft.com/en-us/library/aa368585(VS.85).aspx
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Alvin Moser [EMA
In our installs, we don't utilize a patch wrapper.
Instead, we set the REINSTALL and REINSTALLMODES appropriately within our
installation(s)...
...
PATCH and Installed
PATCH and Installed
...
mailto:[EMAIL PROTECTED] On Behalf Of Pally Sandher
Sent: T
body know how to use EmbeddedUI?
Thanks for the reply John. I guess the question is, what is an example of
Wix XML that will use/launch my embeddedUI dialog.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Nannenga
Sent: Saturday, August 23, 2008 12:2
I've spent a bunch of time lately regarding UI handlers, including embedded UI.
Where can I be of assistance (did you have particular questions I might
answer)?
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Andrew Crum [EMAIL
PROTECTED]
Sent:
Here's a creative approach:
You could use an external UI handler to assist you in unit testing deferred
custom actions. You can still create the MSI etc... like documented on
code.dblock.org; but instead of actually invoking the custom actions yourself,
fire off the install and process the mes
If folks are looking for some good information regarding patching, you might
try the following:
The Windows Installer 3.0 Patching white paper (an excellent resource):
http://www.microsoft.com/downloads/details.aspx?FamilyID=ad7ac91e-2493-4549-ae6f-bf5e007c12a3&DisplayLang=en
Heath Stewart
I believe REINSTALLMODE comes into play here.
Ref: http://msdn.microsoft.com/en-us/library/aa371182(VS.85).aspx
So, in your first post, you had a non-transitive component installing a
registry key conditioned on NOT PATCH. Assuming your installation wasn't
slipstreaming (applying a patch
You've got a ton of options available to you; since I don't know the details of
your installation, I'll try to give you a couple options (pick one [or
something similar, or perhaps a hybrid] that makes the most sense for your
situation). If none of the below work for you, holler and I'll try to
I, personally, absolutely love WiX v3. I have a bunch of installations built
with WiX v2; I took a couple of 'em and moved them over to WiX v3 (with very
little problems, I might add).
Moreover, a bunch of the features within WiX v3 actually saved me time and when
I re-factored, was able to re
Where is your RemoveExistingProducts action scheduled?
Ref: http://msdn.microsoft.com/en-us/library/aa371197(VS.85).aspx
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Jim Flood [EMAIL
PROTECTED]
Sent: Wednesday, August 06, 2008 4:26 PM
To: wi
Custom4 runs during the install because your condition is "Not Installed".
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Moore
Sent: Wednesday, August 06, 2008 2:34 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Custom Actions
I'm
for Windows Installer XML toolset.
Subject: Re: [WiX-users] EmbeddedUIResource
Bug in the XSD. Compiler would support it if you suppress schema validation.
Mind opening a bug on it? It'll be easy to fix.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of J
mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Monday, July 28, 2008 11:03 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] EmbeddedUIResource
John Nannenga wrote:
> We're building a .NET based embedded UI for Windows Installer 4.5. While the
>
We're building a .NET based embedded UI for Windows Installer 4.5. While the
SDK for windows installer implies more than one resource DLL can be included in
the MsiEmbeddedUI table (though only one primary DLL), the wix schema doesn't
allow more than one EmbeddedUIResource element under the Emb
.
Subject: Re: [WiX-users] Extract files from an MSP
Is it possible using DTF?
Regards
Simon Powell
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John
Nannenga
Sent: 25 July 2008 15:03
To: General discussion for Windows Installer XML toolset.
Subject: Re:
http://blogs.msdn.com/heaths/archive/2006/02/14/532200.aspx
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Powell, Simon
Sent: Friday, July 25, 2008 4:29 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Extract files from
they all use an MSI
to install a database. I decided to try this as an alternative to the DOS
batch script I used in the previous version of our software.
On Wed, Jul 23, 2008 at 10:14 AM, John Nannenga <[EMAIL PROTECTED]>
wrote:
> > Ideally, the MSI would un-install itself after it f
> Ideally, the MSI would un-install itself after it finished creating the
> database.
This might be off topic, but curiosity got the best of me; given that to be the
case, why would this be in an MSI at all?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf O
Your rollback script will only be invoked if failure was realized after your
rollback script was scheduled.
Bear in mind, the Immediate vs. Deferred execution context. Rollback happens
only in the deferred sequence.
So, is your failure that you "fake" in the deferred sequence after
MsiUnpubli
component GUIDs." If the Component
content is identical then you shouldn't put them in different Components.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Nannenga
Sent: Friday, July 18, 2008 07:31
To: General discussion for Windows I
erstand what is different from one Component to the next.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Nannenga
Sent: Wednesday, July 16, 2008 15:35
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Multiple Instanc
.
John Nannenga wrote:
>
> Well, below is a really stupid example, but illustrates the behavior
> (refer to WiX code snippets below).
>
> Both installations install a single file and a single registry key. The
> file components have the same Component GUID, but are installed to
rent to Windows Installer Component counts) and allows
for multiple installation media types to reference count (i.e. items other
than windows installer used with Windows installer)
in relation to the non file components are you referring to non file keypath
or components which simply contain add
Well, below is a really stupid example, but illustrates the behavior (refer to
WiX code snippets below).
Both installations install a single file and a single registry key. The file
components have the same Component GUID, but are installed to a different file
system location. The registry co
name but is not
backwards compatible the GUID's should not be matched. In many cases only
the dev will know this information.
John Nannenga wrote:
>
> I believe component ref-counting for file based data is handled at the
> product code and location level. That's why Chad see
PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Nannenga
Sent: Wednesday, July 16, 2008 14:28
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Multiple Instances and Torch.exe
Looking for some advice:
I need to support multiple instances of my product installation (for sake of
Looking for some advice:
I need to support multiple instances of my product installation (for sake of
discussion, let's just say 50 of the suckers).
Regarding all non-file data, I've authored separate components and conditioned
their installation based upon an internal instance name property:
I believe component ref-counting for file based data is handled at the product
code and location level. That's why Chad see's the results he does for the
below situation regarding the web.config file.
Component ref-counting for non-file based data (registry information, ini keys,
shortcuts, e
You can use a custom action to prompt for credentials. Condition the custom
action to fire if the property values you need are not already set, tie it to a
component / other action that requires the property values, and be mindful of
the UILevel.
-Original Message-
From: [EMAIL PROTEC
Here's some example code (this was WiX v2) for configurable merge modules:
In the merge module (foo.msm) => module GUID =
03A6BA5C-D324-4BB6-9109-35DCAFA943FE:
erated using heat using the fragment template and fine tuned with XSLT
> (adding the ... and setting
> the Id of the ComponentGroup.
>
>> What specifically is meant by "with embedded Java Runtime Environment"?
>
> In contrast to, for example, the dot-net runtime, the JR
ple, the dot-net runtime, the JRE works fine when an
installed JRE directory is just *copied* to a new machine (without invoking
an installer which adds a myriad of registry keys and fully integrates into
the target machine).
--
Tom
John Nannenga wrote:
> This seems a little odd, but what the hec
This seems a little odd, but what the heck, I'll bite.
However, since I don't know anything about the Java Runtime Environment, I need
more info. How does your application installation (the one with JRE) deploy
the JRE? Merge modules? Components you authored yourself into your package?
MSI
With regards to patches, I've encountered some folks / standards that don't
like patch wrappers. So if you don't want a patch wrapper AND you don't want
to force users to install your patch via the command line, here's a trick you
might find useful...
1) Author a property setting custom actio
omething ranging between "pretty hard" and
"nearly impossible" :(
Can you add this as a feature request on Source Forge?
http://sourceforge.net/tracker/?group_id=105970&atid=642717
Neil
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf
the warnings at the merge module level. It's all or nothing
at the project level.
Neil
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of John Nannenga [EMAIL
PROTECTED]
Sent: Wednesday, July 09, 2008 10:53 AM
To: General discussion for Windows Instal
/custom action so it can be
extended...
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Nannenga
Sent: Wednesday, July 09, 2008 13:53
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Explicit Deny permissions
I'm t
1 - 100 of 112 matches
Mail list logo
