Hi Blair,
First of all I have to mention that the partner problem is just for our
sale people. To make everything clearer: all the clients, which mean
_our_ and _their_ clients, will have _our_ logo, so I need a
"workaround" only for our sale people, who for whatever reason want only
for their
Fantastic! All fixed ... now to try and deal with the right click - Repair
option ... hmm ...
Thanks Blair,
James
-Original Message-
From: wix-users-boun...@lists.sourceforge.net
[mailto:wix-users-boun...@lists.sourceforge.net] On Behalf Of Blair
Sent: 24 November 2010 02:16
To: 'Genera
I am not familiar with merge module, but taking in account the scenario
I described as a reply to Blair's email (same thread), do you think it
would help me?
I will actually put here the reply to Blair's email just for easier
reference:
"First of all I have to mention that the partner problem
Can I ask how I am to do self registration of com dll?
I've been using SelfRegCost='0' on the file element
Even it's not advisable as seen below because it's quick and easy.
http://www.symantec.com/connect/blogs/resons-avoiding-self-registration
I remember trying to do it the proper way
Hi folks!
This might be a noob question, but I haven't been able to find the
answer. My scenario is really straight forward:
I have a windows application with several files that lands in a "Program
files..." folder. These files are divided into components depending on
what kind of functionality t
If you want to install in products parallel, obviously the files will be
installed to different locations. When you change the location in a
components keypath, you must change the GUID, so the answer is yes.
http://msdn.microsoft.com/en-us/library/aa370561%28VS.85%29.aspx
-Original Message
thanks, Rob
I read your blog about component rules already, but the special case
(different file paths)
is new information for me. Now it makes sense and also limitation on
resources in component
to be in one directory only.
Jan
On Tue, Nov 23, 2010 at 4:38 PM, Rob Mensching wrote:
> No. You can
Thanks for your quick answer Peter! Unfortunately this means that we are
in a state where we can make mistakes in the future when dealing with
branches.
>From an installation point of view, what I want to achieve is
super-simple!
I have a bunch of files that goes into the Program Files--folder.
I
If you don't want to use 1 file per component with "*" GUID, write an
app or script to parse through your .wxs files & regenerate the GUIDs
for you. I wrote a little C# app a while back to do this & it was
probably less than 50 lines of code as one of our deployment scenarios
is identical to yours.
Add a LaunchCondition which checks the REINSTALLMODE property is not set
but make sure you test patching/upgrading if you're going to be shipping
MSP's and/or major upgrades in the future as they set it too IIRC.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F:
THANK YOU!
I was using a standard C# class library project type (apparently I was blind to
the other WiX project types).
It is working great now. Thank you for your help and quick response.
Bob
From: Blair [os...@live.com]
Sent: Tuesday, November 23, 2
Thanks for that Palbinder!
James
-Original Message-
From: wix-users-boun...@lists.sourceforge.net
[mailto:wix-users-boun...@lists.sourceforge.net] On Behalf Of Pally Sandher
Sent: 24 November 2010 11:03
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Set
In the original MSI you give to your sales people, create the MyLogo
component with an empty guid. It will get left behind, and the presence of
the bundle file will prevent its overwrite.
-Original Message-
From: MeCoco [mailto:vcotirl...@hotmail.com]
Sent: Wednesday, November 24, 2010 1:
For most programs most of the time one-component-per-file is exactly what
you want. Being able to use "*" makes it easy to use that model.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Wednesday, November 24, 2010 3:01 AM
To: General discussion for Windows
By way of explanation for anyone interested: the WiX DTF project types
create a *.CA.DLL file that bundles your managed code and calls the
appropriate method based on the entry point you marked/indicated. If you use
the "standard" class library project types you have to create and manage
your own "
If you know the exact registry entries for the registration you can just
author entries into a "cleanup" component to remove them from the registry
and to delete the file. Removals always are scheduled before writes, and you
can schedule the "cleanup" component to run just one time by giving it an
Yes, it is possible to generate working MSPs targeting v2-generated MSIs
(many of us have done so). I don't know what is giving your error, and the
small portion of the log isn't enough information. What is really needed are
the MSI, the MSP, and the entire verbose log.
If you need that support un
Is there a way of finding these outy, other than trawling the registry?
Would heat help here?
Cheers
Sean.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: 24 November 2010 12:39
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] removing a co
Hi Blair,
Thanks a lot for your answer! That was exactly the code I just wrote and
I was testing just now all of the scenarios.
Thanks,
MeCoco
On 11/24/2010 1:23 PM, Blair wrote:
> In the original MSI you give to your sales people, create the MyLogo
> component with an empty guid. It will get l
Thanks for the input guys, I really appreciate it!
However, it seems like wix isn't able to handle this simple scenario. It
seems like I can choose between two evil things:
1. Create a tool (which is easy) that generates guids. But using a tool
for something that really isn't central for the deve
I'd be tempted to write a cleanup tool that I would chain at the
beginning of my new installation. This way I wouldn't have the cleanup
code messing up my wix.
If the previous installer did self registration you could use that to
'clean it up'.
If you want a pure msi solution, you can use heat to
Hi Blair,
I seem to still have a problem: because I want the files that were
placed with an empty GUID to be deleted when a real uninstall happens
(not update or repair, but an uninstall from add/remove programs), I
also added the code:
(NOT UPGRADINGPRODUCTCODE) AND (REMOVE=ALL)
but thi
You don't need to change UpgradeCode, two major versions (1.0 and 2.0
for example) can be installed at same time.
I also thought that i need to change guid of components but that's not
true in case you don't change structure of components,
but Rob told me today in thread "how to manage guids for my
Hmm
is that best practice to install 2 major versions without changing the
UpgradeCode?.
I think handling so makes things more complicated.
Whats happen if u want to upgrade one of the version?..U should keep 2
versions of the installer or not?
Abdoul
I highly recommend reading:
http://robmensching.com/blog/posts/2003/10/18/Component-Rules-101. The
Component Rules are not as simplistic as you are making them out to be.
Also, there are serious negative impliciations to creating multiple file
Components which is why no one recommends them.
Remind
It is a best practice if that's what you want. The WiX toolset ships with
the same UpgradeCode because they are not side-by-side.
On Wed, Nov 24, 2010 at 7:32 AM, wrote:
> Hmm
> is that best practice to install 2 major versions without changing the
> UpgradeCode?.
> I think handling so makes
SelfReg is evil. Run heat against your .dll and it will try to extract the
registry keys. If it can't for some reason (usually because your .dll has
difficult dependencies) then you can write the Class, ProgId, TypeLib
registration by hand.
On Wed, Nov 24, 2010 at 1:30 AM, Yu, Brian wrote:
> Can
I have a hard time saying that anything about the Component Rules make sense
but, yeah, that's what they are.
On Wed, Nov 24, 2010 at 1:50 AM, Jan Gregor wrote:
> thanks, Rob
> I read your blog about component rules already, but the special case
> (different file paths)
> is new information for
Greetings all,
I am trying to modify an installation so it warns users (by displaying an
additional dialog during the installation process) if the installation will
perform a major upgrade. For some reason, Windows Installer is not behaving the
way I expect, presumably because I've done somethi
I am building a C# Custom Action that will be called from dialog button
"Publish". The C# CA is working when called from the Publish Event="DoAction".
However, I can not get it to access the properties that have been set on the
dialog page that the push button control is on. After researchi
What version are you using?
On Mon, Nov 22, 2010 at 8:26 PM, Yann Normand wrote:
> Hi all,
>
> I call HeatDirectory task from a MSBuild file. When the MSBuild file is
> launched from a TFS 2010 Build Server on a x64 system, it fails with the
> following error:
>
> F:\Builds\1\MyApplication\CIBuil
Thanks for the reply. Unfortunately it didn't work. I tried both and
in both cases it sets checkbox next to "Special permissions" (Folder
Properties > Security) and "List folder content" checkbox is
unchecked.
On Mon, Nov 22, 2010 at 12:28 AM, Blair wrote:
> Just a guess (I haven't tried it) but
FWIW, I am using 3.5.2020.0. I have the same problem, but what I did was set
the TFS Build setting to be X86, rather than automatic. That has allowed us to
continue working.
Its not ideal, but it might get you going.
Rob, his subject line says 3.5.2312... are you suggesting that it has been
Ugh, missed that, sorry. There was a fix that should have fixed a regression
so the tools ran out of proc with MSBuild by 3.5.2312. If that didn't fix
the problem, I expect this is a repro of a heat bug that heat doesn't handle
cross process code well. I think:
https://sourceforge.net/tracker/?func
Probably. All the usual caveats apply as to the possible accuracy of heat
capturing self-registration data, but that is a very viable option.
-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
Sent: Wednesday, November 24, 2010 5:05 AM
To: General discussion for Wi
You have complete control over the Upgrade table, so you can choose to leave
builds on side-by-side if you wish while removing very old versions that are
not compatible with your side-by-side scheme at the same time.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Se
PREVIOUSVERSIONSINSTALLED
NOT
PREVIOUSVERSIONSINSTALLED
Somewhere on this list someone once described the case where, if more than
one NewDialog event has a TRUE condition, it uses the highest-ordered one
and ignores all the others. You have to have all of your NewDialog (and
SpawnDialog, if I rec
If it isn't a validation issue, make your C# CA run as immediate in the
execute sequence (not the UI sequence) sometime before the RemoveRegistry
standard action and populate the Registry table with new temporary rows for
each of the registry entries it needs to generate. If you feed it the same
pr
With regard to folders and comparing WinNT.h from SDK 7.1 and WiX v3.0 RTM,
here are how the permission bits map into the directory-related constants
(how they line up with or what they are named in the shell's security dialog
inside the Property's wizard I'm not sure):
GENERIC_READ
Hi, all
I want to show HTML format License(both in local or on web) in my dialog,
but I cannot find any control type can support HTML widget. So I have some
questions about this requirement.
1> Does Wix support HTML widget in Control to show a HTML format EULA.
2> If not, how can I define my own
Hi all,
Sorry if this has already been discussed recently, I haven't looked at WiX
for quite some time and I now find myself needing to develop a relatively
simple installer.
Is WiX 3.5 the way to go these days, or should I stick with 3.0? I've just
been googling and I see that 3.5 is still in b
41 matches
Mail list logo
