Sounds like you are doing a small update. If so, no. See:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa371855(v=vs.85).aspx
On Wed, Apr 3, 2013 at 7:48 AM, Brown, Dan d.br...@techsmith.com wrote:
Is it possible/allowed to remove a feature via a patch?
I get a 2711 error when
The first list I sent is for Bundles, the second list is for MSIs.
On Wed, Apr 3, 2013 at 9:01 AM, James Allen jal...@bidpalnetwork.comwrote:
This will compile however the resultant .exe will not run, what am I doing
wrong?
Bundle Name=AppName Version=1.0.0.0 Manufacturer=AppCompany
Sorry, I should have been more clear up front.
On Wed, Apr 3, 2013 at 9:09 AM, Rob Mensching r...@robmensching.com wrote:
The first list I sent is for Bundles, the second list is for MSIs.
On Wed, Apr 3, 2013 at 9:01 AM, James Allen jal...@bidpalnetwork.comwrote:
This will compile however
Windows Installer will not recognize 4.1.1.8878 as a higher version than
4.1.1.8896. However, you can write your upgrade to say Upgrade when the
version is the same. Technically speaking, I think you could write
Upgrade when the version is lower but I don't know that anyone does that.
On Wed,
This is possible. First the new B.exe needs a higher Bundle/@Version than
any previously released Bundle. You can give the new B.exe one of the
existing UpgradeCodes or give it a new one. The important thing is to add
RelatedBundle elements where the Id attribute is set to the UpgradeCode of
the
You can customize the WiX dialogs if you want.
On Wed, Apr 3, 2013 at 12:21 PM, j2associates j2associa...@yahoo.comwrote:
Hello all,
We are using a Wix setup project with the minimal UI. Is there a way to
include the project configuration so that it is displayed somewhere in the
, 2013 at 7:41 PM, Rob Mensching r...@robmensching.com
wrote:
You can do a minor upgrade.
On Wed, Apr 3, 2013 at 7:00 AM, Subbiah Ganesan subbiahtv...@gmail.com
wrote:
Hi all,
I have a msi released MSI1 and planning to release MSI2. i need to fix
some
custom actions which
That will be very challenging. You don't want to lie to the MSI about what
file is on disk. IOW, the MSI should know what file is being installed,
changing it on the fly would require changing the MSI and that'll also be
challenging (and I believe impossible) while the MSI is running.
On Thu,
anything. Attempt your
download, then copy either your safe file or the downloaded one into the
'live' application area.
Dave
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 04 April 2013 14:17
To: General discussion for Windows Installer XML toolset
Why not just change the TargetName property in MSBuild?
On Thu, Apr 4, 2013 at 9:15 AM, j2associates j2associa...@yahoo.com wrote:
Hello all,
We had a requirement to show the configuration in the msi name because we
have several validation steps along the way. For the benefit of others,
My bet is that something is awry in the upgrade logic on the MSIs. If you
look at the Burn log, the plan should show you what it is doing for each
MSI. That plus the Upgrade (or MajorUpgrade) elements can explain a lot
about what is going sideways.
On Thu, Apr 4, 2013 at 11:16 AM, Alain Forget
not forgotten. Hopefully someone
with knowledge of WiX internals will be able to provide the functionality.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: April 1, 2013 14:20
To: afor...@cmu.edu; General discussion for Windows Installer XML toolset.
Subject
The Win64 attribute defaults to 'yes' or 'no' based on the value you pass
to the candle.exe -arch switch. If Win64 is 'no' it searches 32-bit. If it
is 'yes' it will search 64-bit on 64-bit machine and 32-bit on a 32-bit
machine (because there is no 64-bit).
Bootstrapper is completely separate
Yeah, changing the TargetName should just be a matter of editing the
.wixproj to include another MSBuild property. This is really about MSBuild
though functionality, not the WiX toolset.
On Fri, Apr 5, 2013 at 4:54 AM, j2associates j2associa...@yahoo.com wrote:
Hello Rob,
Thanks for the
like it is.
Thanks
Raj
On Fri, Apr 5, 2013 at 6:53 AM, Rob Mensching r...@robmensching.com
wrote:
The Win64 attribute defaults to 'yes' or 'no' based on the value you pass
to the candle.exe -arch switch. If Win64 is 'no' it searches 32-bit. If
it
is 'yes' it will search 64-bit on 64
wanted to know if this is
documented behavior and not likely to break in future.
-Raj
On Fri, Apr 5, 2013 at 8:28 AM, Rob Mensching r...@robmensching.com
wrote:
Sorry, my bad. I didn't realize you were talking about the
util:RegistrySearch. My answer was about the MSI based
name you need.
--
Edwin
On Fri, Apr 5, 2013 at 5:54 AM, Rob Mensching r...@robmensching.com
wrote:
Yeah, changing the TargetName should just be a matter of editing the
.wixproj to include another MSBuild property. This is really about
MSBuild
though functionality, not the WiX toolset
Make sure you pass a handle to your Bootstrapper Application window to
Apply().
On Sat, Apr 6, 2013 at 7:27 AM, feng huang fy24h.hu...@gmail.com wrote:
Dear all,
I have write a custom bootstrapper use wpf, it will show some
prerequisites. everything is ok. but when click install , the
That's a pretty scary hack to me. I could see us doing things in the future
that totally get confused doing that. It seems like this would be a better
feature request for the engine to handle. The behavior you are seeing right
now is completely expected but I can totally see why it'd be nice if
());
Bootstrapper.Engine.Plan(LaunchAction.Install);
}
-邮件原件-
发件人: Rob Mensching [mailto:r...@robmensching.com]
发送时间: 2013年4月6日 23:08
收件人: General discussion for Windows Installer XML toolset.
主题: Re: [WiX-users] Burn DisplayInternalUI z-order has problem
Make sure you
Log file for all Bundles is in %TEMP%. There is a known issue with the most
recent build that is just busted. Should all be fixed in Monday's build.
On Sat, Apr 6, 2013 at 1:28 PM, Sean Farrow sean.far...@seanfarrow.co.ukwrote:
Hi,
I'm running a machine with the latest weekly builds. I've
I think you want SystemFolder (
http://msdn.microsoft.com/en-us/library/windows/desktop/aa372055(v=vs.85).aspx)
and System64Folder (
http://msdn.microsoft.com/en-us/library/windows/desktop/aa372054(v=vs.85).aspx
)
On Sun, Apr 7, 2013 at 7:24 AM, David Steadman steadm...@gmail.com wrote:
When I
...@gmail.com
wrote:
testing now sorry, your correct...
On Sun, Apr 7, 2013 at 10:30 AM, Rob Mensching r...@robmensching.com
wrote:
I think you want SystemFolder (
http://msdn.microsoft.com/en-us/library/windows/desktop/aa372055(v=vs.85).aspx
)
and System64Folder (
http
What do the log files say? You'll find them in %TEMP%
On Sun, Apr 7, 2013 at 3:22 PM, Marco Tognacci mark...@live.it wrote:
I have made a Burn installer using latest weekly release of wix 3.7,
following the sample provided with wix package.I can install and uninstall
the package with no
a built in way of doing this, and with management
expecting what previously worked with Wise to work with Wix, it iwa the
best I could come up with.
From: Rob Mensching r...@robmensching.com
To: General discussion for Windows Installer XML toolset.
wix
Variable is like Property. The Value attribute is the value of the
variable. It isn't interpreted.
On Sun, Apr 7, 2013 at 8:00 AM, Marco Tognacci mark...@live.it wrote:
In my Bundle application I have defined a variable to define the
installation folder, I want to initialize this variable to
Recommended to leave them blank and let the toolset pick them for you.
On Mon, Apr 8, 2013 at 6:17 AM, ptr ptrajku...@gmail.com wrote:
hey all
When you include a Msipackage in boostrapper you can specify cache and
cacheid. The documenation is sparse on what these attribtues do ? What is
deprecating it yet.
On Mon, Apr 8, 2013 at 12:54 PM, ptr ptrajku...@gmail.com wrote:
Thanks Rob, But what does these variables do ?
thanks
Raj
On Mon, Apr 8, 2013 at 1:28 PM, Rob Mensching r...@robmensching.com
wrote:
Recommended to leave them blank and let the toolset pick them for you
Did you add the extra files as Payload elements under the
BootstrapperApplication element? If not, they are certainly missing from
where your BA is being run.
On Mon, Apr 8, 2013 at 12:51 PM, Nick Miller nmil...@livetechnology.comwrote:
Thanks for the reply. This looks like what I currently
If you want the value of a Variable formatted call the Engine
FormatString() method. This is very similar to MSI API to format a property.
On Mon, Apr 8, 2013 at 1:26 PM, Marco Tognacci mark...@live.it wrote:
I need to have the value resolved in the plan phase as I have to report it
on the
: Rob Mensching [mailto:r...@robmensching.com]
Sent: Monday, April 08, 2013 4:21 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Visual Styles in Wix BA
Did you add the extra files as Payload elements under the
BootstrapperApplication element
That bug was about adding support to the wixstdba to parse the command-line
arguments passed via Command and convert them to variables automatically.
That bug was really a feature request and Bob fixed it when he added
support for the `Overridable` attribute to `Variable` element.
There is no
Sounds reasonable. Other people have been successful doing such things on
this mailing list in the past. Good luck!
On Tue, Apr 9, 2013 at 12:09 AM, Christoph Goetz
christoph.go...@giepa.dewrote:
Hi,
i want to create a multi-language installation.
I want to do this over and torch,
No, you can write your BA's in native code if you prefer.
On Tue, Apr 9, 2013 at 11:04 AM, Marco Tognacci mark...@live.it wrote:
So there is no way for making this in the Bundle.wxs, without using c#
code, right?The only way is to add c# code and evaluate FormatString()?
Date: Mon, 8 Apr
That's a feature called modifiable chain that is not implemented yet.
On Tue, Apr 9, 2013 at 2:39 PM, Marco Tognacci mark...@live.it wrote:
I need to have the possbility to run some executable during installation
made with Burn, I know these executable only after building the Burn setup,
so
It is a very challenging feature particularly around security. There is no
plan that I'm aware of to implement the feature currently. It will require
a lot of dedication to implement properly and it hasn't been worth the
effort given that the straight forward solution is to build an updated
bundle
]i007: Exit code: 0x80070002, restarting: No
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 06 April 2013 22:16
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] latest weekly build fails to update
Log file for all Bundles
The GUIDs will only be stable if you use the -ag switch to heat.exe (I
forget the switch in HeatDirectory task to do the same).
On Wed, Apr 10, 2013 at 7:05 AM, Gareth Williams
gar...@trinitydigital.co.uk wrote:
Thanks for responding - I think patches are not probably needed, but full
What about [dirA]. The [$dirA] would be trying to get the directory of
a Component matching that Id, right?
On Mon, Apr 8, 2013 at 4:00 PM, Alain Forget afor...@cmu.edu wrote:
Hi all,
Say we have the following structure:
Directory Id=dirA Name=A
Directory Id=dirB Name=B
Directory Id=dirC
into a small book or something.
smile/
On Wed, Apr 10, 2013 at 8:01 AM, Alain Forget afor...@cmu.edu wrote:
Thanks for the reply. I thought the syntax [dirA] was only for
properties. Does the Directory element also count as (or create) a
property?
-Original Message-
From: Rob Mensching
GetCommandLineArgs() is a member on the Command struct provided to your BA.
Basically, it was already contributed. smile/
tom is just noting that you can use it.
On Wed, Apr 10, 2013 at 11:11 AM, Steven Ogilvie
steven.ogil...@titus.comwrote:
Classification: Public
What. no no...
I meant
(without full path)
anddirectories in formatted strings
Thanks for the reply. I thought the syntax [dirA] was only for
properties.
Does the Directory element also count as (or create) a property?
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: April 10
If you get to Apply() then you need to return Result.Cancel from one of the
callbacks before apply phase is complete to cause rollback.
On Wed, Apr 10, 2013 at 2:41 PM, ptr ptrajku...@gmail.com wrote:
hey all
I have a custom managed boostrapper that installs .NET4 framework as a
prereq.
name. For example, say some File element installs a file to
C:/My/Path/To/File.exe, I'd like some formatted string type thing to return
just File.exe.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: April 10, 2013 17:27
To: afor...@cmu.edu; General
as installed. It would be good if there was Engine.Abort method that did
the needful
Thanks
raj
On Wed, Apr 10, 2013 at 4:27 PM, Rob Mensching r...@robmensching.com
wrote:
If you get to Apply() then you need to return Result.Cancel from one of
the
callbacks before apply phase
Usually indicates that Windows Update is busy or unhappy on that machine.
If the problem persists check out Windows Update and see that it is
behaving well.
On Thu, Apr 11, 2013 at 7:23 AM, Michael Ogilvie
michael.ogil...@pixelink.com wrote:
On one of our Vista test boxes I am getting a very
Probably related to recent fixes WiX v3.8 to get native code working
correctly on WinXP. What version of WiX toolset are you using?
On Thu, Apr 11, 2013 at 2:10 AM, Sergey Yukhno
sergey.yuk...@visutechsystem.by wrote:
Hello.
Error at creating user on Windows XP with error dialog ...Setup
If the hash doesn't match then the Bundle expects a different MSI than the
one you are putting on the URL. You can't change the MSI without updating
the Bundle's that reference it.
The WiX toolset shares the ProjectAggregator.msi across many versions of
the Bundles because the
updates the
issue went away.
Is there any way to bypass this windows update check?
Thank you,
Michael Ogilvie
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Thursday, April 11, 2013 10:42 AM
To: General discussion for Windows Installer XML toolset
Note there are more things than the file date that change with every build
(namely the PackageCode). File date will not affect the file hash.
On Thu, Apr 11, 2013 at 8:47 AM, Spud andysmi...@gmail.com wrote:
I think I've been having a few blonde moments. (sigh)
My build is re-creating this
wrote:
v3.8.309.0 and early. I can't setup v3.8.401.0 and later on Win 7 x64
like in [WiX-users] latest weekly build fails to update.
On 4/11/2013 17:44, Rob Mensching wrote:
Probably related to recent fixes WiX v3.8 to get native code working
correctly on WinXP. What version of WiX toolset
By default the newer version of the Bundle will remove older versions of
the Bundles that share the same UpgradeCode. Bundles do not suffer from the
same 3 field version issues that MSI packages do. Forcing the e.State for
RelatedBundles to absent could have other side-effects (like removing
Wow, that's beginner mistake. Get them to fix the file version or rename
the file. Or you can install to a new location (which essentially renames
the file). DefaultVersion basic lies to the Windows Installer and it will
never be certain the file that is on disk is the right one (because the one
Your BA provides all UI.
On Sat, Apr 13, 2013 at 4:22 AM, Marco Tognacci mark...@live.it wrote:
I have made a setup using Burn with WPF UI,Unistalling from ARP (Uninstall
programs from control panel) is there an option to make appear the message
dialog for request of confirm?Or I have to
No, but a custom BA can provide the DownloadUrl for payloads.
On Mon, Apr 15, 2013 at 7:57 AM, Snoza, Ivo ivo.sn...@ncr.com wrote:
Hello,
is there any way how to insert variable value into DownloadUrl string in
run time of bootstrap? I'm starting bootstrapper from command line like
Yes. Curious why you want to support downgrades? Don't hear that very often.
On Mon, Apr 15, 2013 at 8:51 AM, Alain Forget afor...@cmu.edu wrote:
This is very insightful, thanks! So my MajorUpgrade tag looks like this:
MajorUpgrade AllowDowngrades=yes Schedule=afterInstallInitialize /
The
msizap creates more problems than it's worth.
On Mon, Apr 15, 2013 at 1:42 PM, Mr GAPearce mr_gapea...@yahoo.com wrote:
Search for msizap.exe on the msdn website.
On Apr 15, 2013, at 4:03 PM, Marco Tognacci mark...@live.it wrote:
I have think about this problem, if I make a mistake in the
+1 but I'd rev the 4th number of the version to know if the user has the
fixed MSI.
On Mon, Apr 15, 2013 at 2:06 PM, Hoover, Jacob
jacob.hoo...@greenheck.comwrote:
I would say fix your MSI, If you release a bad one, you need to
re-release it with the same product/upgrade codes (and version),
Yeah, testers used to find crazy bugs with installs. Then a couple hours of
complete confusion trying to figure out what the heck went wrong, they'd
say, Oh, by the way I ran msizap on the machine before the install. As
calmly as possible I'd respond, Cool, format machine and try to reproduce
the
No, this matches the behavior of uninstalling MSI files from ARP.
On Mon, Apr 15, 2013 at 4:23 PM, Christopher West C
christopher.c.w...@ericsson.com wrote:
Using Wix 3.7, I have created a default burn bootstrapper using the
WixStandardBootstrapperApplication.RtfLicense. I have been
Take a look at the src\Setup\Bundle\Bundle.wxs which is the web installer
for the WiX toolset itself.
On Tue, Apr 16, 2013 at 2:45 AM, Kannan24 skan...@syncfusion.com wrote:
Hi,
Can you please how to create the online installation setup?
Is possible to create the online installation by
MsiPackage element is used by Bundles. That data is provided in the
BootstrapperApplicationData.xml file provided to BootstrapperApplications
running in Burn. Not clear if you are writing a custom BA or if you have a
custom bootstrapper engine. For the latter, you'll have to write all the
There are no plans to make the Bundle Id settable. There are so many things
that would start to fall apart if that value was the same for two Bundles.
Huge numbers of conflicts. smile/ RelatedBundle is a fantastic way to
address the problem. You could even Bundle/@Tag the different bundles and
via the burn .exe, versus if the .msi is installed and then uninstalled
from ARP without using the burn .exe.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Tuesday, April 16, 2013 9:02 AM
To: General discussion for Windows Installer XML toolset.
Subject
for the installed one to be uninstalled. Is this correct? If both are
installed and at same version then you'd have two entries in ARP?
Wes
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: April-16-13 11:05 AM
To: General discussion for Windows Installer XML
PS: Why does it matter? I'm curious.
On Tue, Apr 16, 2013 at 7:52 AM, Rob Mensching r...@robmensching.com wrote:
Ug. I know Bob changed some things here last because there were some
issues. I thought it was as my memory remembered but I was apparently
wrong. Hopefully, he can chime
/MsiPackage
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Tuesday, April 16, 2013 9:31 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] UILevel on uninstall using
WixStandardBootstrapperApplication.RtfLicense bootstrapper
Do you want the MYVAR Burn Variable to be saved after the initial install?
If so add Persist='yes' to the Variable definition of MYVAR. Otherwise, it
will be reset every time the Bundle runs.
On Tue, Apr 16, 2013 at 8:03 AM, StevenOgilvie sogil...@msn.com wrote:
I am trying the same thing and
.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: April-16-13 11:50 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Handling Web + CD bundle with same Version +
content but built with different BundleIDs
displaying
the message box, and instead would write the message to the log file.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Tuesday, April 16, 2013 9:53 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] UILevel
=no
Visible=no
Cache=no
Compressed=no
Permanent=no
Vital=yes
MsiProperty Name=MYVAR Value=[MYVAR] /
/MsiPackage
Thanks,
Steve
-Original Message-
From: Rob Mensching
Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: April-16-13 12:24 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Handling Web + CD bundle with same Version +
content but built with different BundleIDs
There is no removal for detect
the result in the Property table
were it can be queried.
Phil
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Tuesday, April 16, 2013 7:03 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] determining the install size
After restart, the process starts over. However, Detect should see that a
bunch of things are already on the machine and thus Planning will only do
what is next.
This is important because machine state could change significantly between
the time the restart was requested and the restart actually
I'm obviously biased but non-declarative installation technologies like
NSIS are a complete non-starter for me. I don't want to write scripts that
install files then have to remember write more scripts to uninstall those
files.
I had a couple consulting gigs to convert setups from NSIS. It amazed
The Command structure passed to your BA will tell you if the Bundle is
starting after restart. You can also persist values in Variables before the
original Apply() and they will be there after restart.
On Tue, Apr 16, 2013 at 3:08 PM, Marco Tognacci mark...@live.it wrote:
But in this case how
Take a look at the current wix38 branch. The WiX Bundle is turned into a
single self-extracting executable to be hosted on CodePlex just before
final release. Then it goes back to being a web bundle when we host the
weekly builds of http://wixtoolset.org/releases
On Tue, Apr 16, 2013 at 10:00
Unfortunately, no. The child MSI just gets `UPGRADINGPRODUCTCODE`.
On Wed, Apr 17, 2013 at 12:13 AM, Simon Stevenson redw...@gmail.com wrote:
Is it possible to pass parameters to the msi being uninstalled during an
upgrade?
I am using the Upgrade tag to do my upgrades.
Yeah, bug.
On Wed, Apr 17, 2013 at 8:08 AM, Phil Wilson phil.wil...@mvps.org wrote:
I had the same issue with RunOnce. The solution was to create the RunOnce
data in a file and have the RunOnce key start the program with a command
line that said hey, the data you want is in this file.
Phil
proficient...
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Tuesday, April 16, 2013 7:53 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX vs NSIS
I'm obviously biased but non-declarative installation technologies
Yes. You'd need to persist your state yourself. The Plan is only valid for
a single Apply and is discarded after. It is never persisted because the
machine state could change between the Plan and the Apply.
On Wed, Apr 17, 2013 at 11:45 AM, Marco Tognacci mark...@live.it wrote:
As I have made
The former.
On Wed, Apr 17, 2013 at 12:13 PM, Marco Tognacci mark...@live.it wrote:
I have implemented the /layout option in my Burn setup. the only thing
that it do is to copy all the setup.exe that I have made.I have a single
file setup, with all the resources embedded inside.This option
Today you have to write it all yourself. You can see this in wixstdba.
On Wed, Apr 17, 2013 at 12:17 PM, Marco Tognacci mark...@live.it wrote:
I have implemented the Help page in Burn setup using WPF custom UI.I'd
like to add all the command line args, is there any way to have the help
text
People guessing the SQL influence are correct. Back in 1995, SQL was a big
thing and transacted install was the big new idea (a very good idea, IMHO)
so there was a theory that you should make the MSI a SQL database because
you're doing transaction stuff. IMHO, that didn't work out nearly as well
Does FIPS require SHA2 now? Burn currently expects SHA1 hashes.
On Fri, Apr 19, 2013 at 7:35 AM, Jonathan Racine jonathan.rac...@hybris.com
wrote:
Hi All,
Using Wix toolset 3.7 or 4.0.12, I have created a really simple bundle
application using the WixStandardBootsrapper and am getting a
What you are seeing is the recommended best practices for Windows. Don't
elevate until necessary. Only put the shield on the button that causes
elevation. Burn does all that, except you have to put the shield on the
Install button because your BA shows that. smile/
On Fri, Apr 19, 2013 at 1:03
Not aware of a workaround for a system feature. Task scheduler is an
interesting idea for Vista+. Might add a chunk of complexity. Something
someone could investigate if really interested.
On Mon, Apr 22, 2013 at 1:00 AM, rowbot james.row...@microfocus.com wrote:
Found this..
If someone contributes it, yes. Want to send a pull request against wix38
with that?
On Mon, Apr 22, 2013 at 9:05 AM, John Cooper jocoo...@jackhenry.com wrote:
I've got a product that now has a dependency on PowerShell version 3.0.
The POWERSHELLVERSION property in the PS extension only
Seems reasonable probably not implemented originally because we didn't
expect many layout-only Payloads. They are usually very rare (like maybe an
autorun.inf or readme.txt).
On Thu, Apr 18, 2013 at 10:56 AM, tom tomer.d...@intergraph.com wrote:
add
PackageGroupRef inside the chain
--
, Apr 19, 2013 at 5:24 PM, Rob Mensching r...@robmensching.com
wrote:
What you are seeing is the recommended best practices for Windows. Don't
elevate until necessary. Only put the shield on the button that causes
elevation. Burn does all that, except you have to put the shield on the
Install
If the [LogPathVariable] was passed as an empty string that means the
variable was interpreted, it just interpreted to empty string. Logging for
ExePackage's has to be done essentially manual since .exe based installs
are all very different. However Burn provides a little to help you. The
Did you ever get this sorted out?
On Tue, Apr 9, 2013 at 5:57 AM, Theo Landman tland...@justcroft.com wrote:
Hello,
I'm confused about how Impersonate works. I want to run a console
migration executable using the WiX CAQuitExec. The migration executable
copies files from a previous version
The log file shows that Burn believes the package is already installed
therefore no operations are necessary. Not clear to me what the issue is
(however, setting your InstallCondition to 1 is very strange thing to do
and could have interesting side effects in the future).
On Tue, Apr 23, 2013 at
, beyond my cage match, I'll also be floating around at the
conference (when I'm not sharpening my sword) so if you're going to be
around let me know.
You can get more details about the conference here:
http://www.regonline.com/builder/site/Default.aspx?EventID=1224520
virtually,
Rob Mensching
Use the Bundle/@Condition attribute. It was designed for this scenario.
On Wed, Apr 24, 2013 at 3:25 AM, Sam Boman s...@samb.se wrote:
Hello,
Today we have a bootstrapper, taking care of first installing .NET 4.5, and
then the MSI with the application. If the user runs Windows XP, or any
It's very possible the COM+ CA in WiX toolset doesn't do exactly that.
Perhaps you could take a look at the code and see what is wrong? Code is
in src\ext\ComPlusExtension. I know nothing about COM+ so I'm not much help
beyond that.
On Wed, Apr 24, 2013 at 12:04 AM, Bart van Lierop
What version of the .NET Framework are you using? It certainly could be a
bug. Not many people use Windows XP as a development box any longer so we
might not get much coverage there.
On Wed, Apr 24, 2013 at 12:18 AM, Pawel Fujcik pfuj...@proximetry.plwrote:
Hello!
I'm have got wix 3.7
or NETFX 3.5.
On Wed, Apr 24, 2013 at 5:34 AM, Pawel Fujcik pfuj...@proximetry.pl wrote:
.NET Framework 4.0
Od: Rob Mensching [r...@robmensching.com]
Wysłano: 24 kwietnia 2013 14:29
Do: General discussion for Windows Installer XML toolset.
Temat: Re
That's standard in Markdown to mark a word with *emphasis*.
On Wed, Apr 24, 2013 at 7:19 AM, sleon sergioleonc...@gmail.com wrote:
Why did you put stable between asterisks? Is there a caveat? What does it
mean?
Or use Heat with the -ag switch to make it generate *stable* GUIDs.
--
View
The WiX documentation has a topic about launching an executable at the end
of install. Unless you explicitly launched your installation elevated, it
will launch as the normal user.
On Wed, Apr 24, 2013 at 6:42 AM, TimM timmay...@smarttech.com wrote:
We have a WiX (.msi) installer that has to
701 - 800 of 5072 matches
Mail list logo
