There is a topic in the WiX.chm dedicated to this. The title is identical
or nearly identical to the subject of this email.
Thanks Rob for replying me but I am not able to understand what you
replied. Can you please provide some detail related to this.
On Tue, May 8, 2012 at 1:14 PM, Vivek Soni
Sadly no. CRT dies before ever loading Burn code.
On Mon, Apr 30, 2012 at 8:57 AM, Neil Sleightholm wrote:
> I agree with dropping support for Win2k but what is a shame is that
> running the exe doesn't display a more useful error message. I don't
> suppose there is anything that can be done to c
To pass a security review at Microsoft, the VS2010 CRT must be used. The
VS2010 CRT has the latest security defenses built in. Unfortunately, the
VS2010 CRT does not run on Win2K. The bad error message actually happens
in the VS2010 CRT. Our code in Burn doesn't even have the opportunity to
load.
I'd steer clear of DLL self-registrations at all costs. Unless your COM
component is truly shared across multiple applications, I'd suggest
using registration free COM by embedding a manifest (type 24 I believe)
resource into the exe. MT.EXE from the SDK is your friend, and it has an
added benefit
Then use the -ext switch as I showed below. Something like:
candle -ext WixUtilExtension
light -ext WixUtilExtension
On Tue, May 8, 2012 at 1:18 PM, Charles Broadfoot <
charles.broadf...@microsoft.com> wrote:
> I have been using "candle" and "light".
>
> I assume this is not VS.
>
> -Origin
heat -? gives help. What did you try?
I do not believe heat supports COM+. COM+ has very complex registration,
I've never used it personally. Others may have ideas.
On Tue, May 8, 2012 at 10:06 PM, Rakheep wrote:
> How to use heat.exe?? can you give some more information regarding this..
>
> I
ComPlusApplications are for COM+. Are you just trying to register COM
stuff like Class, ProgId, Typelib? If so, use those elements. COM+ is a
much different thing.
On Tue, May 8, 2012 at 10:04 PM, Rakheep wrote:
> I am unable to register a non .net com DLL??.. Please provide a solution
> for
You could try adding the text as temporary data to the ScrollableText
control. MSI UI is kinda' limited and annoying so I try to avoid doing such
things. Good luck!
On Tue, May 8, 2012 at 10:03 PM, Rakheep wrote:
> I need to display a complete list of the selections made while installing..
> som
1. WiX is not our trademark. Our project is technically "WiX toolset".
There is a company out ther called "Wix". Do what you wish with that
information.
2. I think the GPL is mostly political posturing but it's your code so you
can ship it under whatever license you want. We won't ever be able to
Add a RelatedBundle element with Id same as the UpgradeCode of the old
Bundle and Action="Upgrade". Oh and make sure your new Bundle's version is
higher.
On Mon, May 7, 2012 at 2:20 PM, Ian Williams wrote:
> I'll looking to have my burn bundle invoke uninstall on a different burn
> bundle if it
There is a topic in the WiX.chm dedicated to this. The title is identical
or nearly identical to the subject of this email.
On Tue, May 8, 2012 at 12:44 AM, Vivek Soni wrote:
> Hello,
>
> I created an installer which launch an exe if a checkbox in checked. I
> used BinaryKey="WixCA" and DllEntry
1. No. The .NET Framework is not required by wixstdba.
2. You can chain and condition your x86 and x64 packages into a single
Bundle if you like.
On Mon, May 7, 2012 at 7:02 PM, Sean Farrow wrote:
> Hi All:
> I have two queries regarding burn:
> Firstly, does the burn standard bootstrapper requi
It's supposed to. Can you be more specific about "no longer working" to
help investigate?
On Tue, May 8, 2012 at 9:18 AM, Pally Sandher wrote:
> And this is no longer working as of v3.6.2907.0
>
> Palbinder Sandher
> Software Platform Engineer
> T: +44 (0) 141 945 8500
> F: +44 (0) 141 945 8501
>
Feed moved here: http://wixtoolset.org/releases/feed/v3.6
On Tue, May 8, 2012 at 1:13 PM, Bruce Cran wrote:
> On 08/05/2012 13:13, Neil Sleightholm wrote:
> > I asked something similar recently and I don't believe this is available
> yet. As a workaround I download the source and look at the his
How to use heat.exe?? can you give some more information regarding this..
I want to register non .net COM+ dlls.. also.. along with some .net COM
dlls..
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Register-com-objects-tp2555661p7541764.html
Sent
I am unable to register a non .net com DLL??.. Please provide a solution for
this..
Also, the process of COM registering takes a long time, using WIX. Any idea?
Code:
I need to display a complete list of the selections made while installing..
something like a installation summary on a dialog. The information is long,
so I need a control with a vertical scroll bar.. How can I achieve this? I
have tried using custom action and created a file which contains the
ins
Hmm,
What exactly are you trying to accomplish? Burn is for bundling. If
you need some conditional files installed I'd make a separate MSI
package and pass the state you've decided in burn into the Msi package
as parameters.
See MsiProperty in the docs.
-Original Message-
From: Lily Le
Assuming you are using the StdBA, I am mostly certain that the passing
of bootstrapper params to the underlying packages has not been
implemented. Sadly, the native BA is a bit rough around the edges. For
now the "team" has been focusing on the core functionality of burn and
not the BA's. My adv
Hi All,
I am struggle with Burn tool now.
I need to add additional files to destination path. But I can't find out any
elements (for example, CopyFile element in Wix, or etc in Burn elements) Do
you know the way to put additional file when I install the all of package
with Burn?
Please help me.
You can do it by setting "SuppressValidation" property to "true".
-Original Message-
From: dbartm...@tsys.com [mailto:dbartm...@tsys.com]
Sent: Tuesday, May 08, 2012 15:46
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] ICE errors in TFS build
How do y
How do you turn off ICE validation?
Thanks!
--
David Bartmess
Configuration Management
dbartm...@tsys.com
Work: 303-216-3918
Cell: 303-883-9117
From: "Alex Ivanoff"
To: "'General discussion for Windows Installer XML toolset.'"
Date: 05/08/2012 09:
I have been using "candle" and "light".
I assume this is not VS.
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: Tuesday, May 08, 2012 10:00 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Adding paramater to msi that will set va
On 08/05/2012 13:13, Neil Sleightholm wrote:
> I asked something similar recently and I don't believe this is available yet.
> As a workaround I download the source and look at the history.txt file.
http://wix.codeplex.com/SourceControl/list/changesets also has a list of
changes, and it gets upd
Not sure if this has been mentioned, but one of the gotchas is that the
previous version of the install might be installed per-user instead of
per-machine. A per-machine install will not upgrade a per user (and vice versa)
so you get two entries in ARP. That's an InstallShield log, not an MSI lo
Are you trying to build a wix project? The easiest way to do this is to simply
call
msbuild solution.sln
Or perhaps
msbuild project.wixproj
Passing the usual command line arguments to msbuild.
If you are truly looking to call candle.exe, light.exe, etc. then just call
them with the appropria
If you are compiling in visual studio, just add a reference to the
WixUtilExtension in your wixproj. (right click references, add reference
browse to the wix bin folder and choose C:\Program Files (x86)\WiX Toolset
v3.6\bin\\WixUtilExtension.dll)
If you are building some other way you will need to
And this is no longer working as of v3.6.2907.0
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registere
Up until now I have been able to merge VC90 merge modules of both x86 and x64
varieties into the same package without any problem. Now that we've moved on
to Visual Studio 2010 for our applications, I must similarly update my merge
module inclusions. If I attempt to merge just the x86 versions, I g
I'm using VS2010 and WiX 3.6 to create MSI packages and bundle them into
Bootstrapper setup. Here's my Boostrapper code.
http://schemas.microsoft.com/wix/2006/wi";>
I'm sorry to keep going on about this problem. Despite the various suggestions
(some of which I have to admit were over my head!) I am still uncertain where
this problem lies, there seems to be various candidates - a problem with the
original install, a problem with Installshield or a problem w
Make sure the account that TFS Build Agent runs under is a member of
Administrators group. We actually had to turn off ICE validation because
of this.
-Original Message-
From: dbartm...@tsys.com [mailto:dbartm...@tsys.com]
Sent: Tuesday, May 08, 2012 09:37
To: General discussion for Wind
No. How would I do that?
-Original Message-
From: Rob Hamflett [mailto:rob_hamfl...@sn.scee.net]
Sent: Thursday, May 03, 2012 12:43 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding paramater to msi that will set value in config
file
On 02/05/2012 15:07, Charles Br
We are trying to switch over to using TFS as our main build system, and I
am running into the following errors. I finally managed to get TFS to
build the installer, but as you can see, the light.exe is failing on
several ICE errors.
These errors do not occur if I manually run the solution's bu
Hi!
If this is the wrong forum for this message, I apologise. It was the best I
could find.
I'm a software developer, and the company for which I work recently started
using WiX for one of their products. As part of the team that implemented
it, I was quite satisfied with the result.
There are p
1. The detection is for the x86 + x64 package. In plain english you can read
the condition as x86 NetFx key exists and either the machine is not 64-bit or
the x64 NetFx key exists.2. 4.0.3 is an update for .Net 4. It still requires
the original .Net 4 to be installed. Instead of creating yo
Are you sure you have RemoveExistingProducts scheduled?
Sounds to me like when you install the later version, it's incrementing the
Component Reference count which is why uninstalling the old one works fine (all
it does is decrement the Component Reference counts) & would explain why the
direct
You may want to check the values in the Upgrade table. It sounds as though the
existing values do not cover the installation you are trying to upgrade. Pay
specific attention to the listed upgrade codes and the version settings.
Mat Skildum
-Original Message-
From: Ian Brooke [mailt
Thanks for your reply Neil,
I'm not aware of a "Package Code" in Installshield, however the Product Code
has changed and the Version number has changed (from 7.0.2 to 7.0.4) and the
Upgrade Code has remained the same so I have no idea what's going on.
Sounds as though it's an Installshield probl
Cheers Neil, I guess I'll have to start doing the same.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
R
I asked something similar recently and I don't believe this is available yet.
As a workaround I download the source and look at the history.txt file.
Neil
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 08 May 2012 11:41
To: General discussion for Windows I
When WiX was hosted on SourceForge there were handy RSS feeds for the daily
builds along with change lists e.g.
http://wix.sourceforge.net/releases/wix3.6.feed
Sadly since the move to codeplex/wixtoolset.org these no longer exist (or I
can't find them). Could we get these brought back as it was
Hello,
I created an installer which launch an exe if a checkbox in checked. I
used BinaryKey="WixCA" and DllEntry="WixShellExec" to launch the exe. Now
I want to launch another exe after installation. I was trying this using
"InstallExecuteSequence" but I am confused about which BinaryKey and
Dll
43 matches
Mail list logo
