It is not really related to your question, but I had a question about
popup message box from custom action and I got an answer from Bob
Arnson:
Set a property in the CA and use that property as the condition in a
SpawnDialog control event to show a message box. Never show UI from a
CA; there's no
Hi Rob!
Do you mean, that you use xslt to modify the heat-generated wxs files in
an automated way?
Can you give me an example for that?
br,
Markus
On Dec 9, Rob Mensching r...@robmensching.com wrote:
I usually just write an XSL transform. heat supports that.
On Wed, Dec 9, 2009 at 9:45 PM,
Markus,
The heat.exe has a switch -t:transform.xsl. If you specify this switch
running heat, the 'transform.xsl' will be applied to the regular output
of you heat command. The final resulting wxs file will contain
transformed xml.
There are no special requirements for that XSL transform.
Hope
On 09/12/2009 17:55, Wilson, Phil wrote:
All the CommonFilesFolder values in merge modules are by convention appended
with a mangled guid, but as far as I can tell the mechanism that rationalizes
all the folder name properties from merge modules (such as
CommonFilesFolder.guid) at merge
Hi All,
I've got a problem with my condition using a property.
I set this property in the UI with my own dialog buttons which have the
following code.
!--The DEPLOYMENTTYPE buttons--
Control Id=AllInOne Type=PushButton Height=41 Width=41 X=72
Y=80 Bitmap=yes Text=AllInOneImg
Publish
Hello Again
The Allusers were not the same. I set them both to Allusers = 1.
I received the following results:
In Major Update:
- in case that the OnlyDetect='yes' :
There are two entries in the Add Remove Programs
- in case that the OnlyDetect='no' :
There are is one entry in the
A little while ago I was having some problems when uninstalling our
application. I managed to get round this by defining the
MSIRESTARTMANAGERCONTROL property as disable to revert back to the
FilesInUse dialog. This works perfectly fine in Server 2008. However I have
encountered an issue when
Hi,
I have the following scenario.
- MSI installs a service.
- MSI makes MAJOR upgrade to this installed service (uninstalls old
version and installs new version)
- During the major upgrade if it fails, it makes rollback and the
service uninstalls completely.
Is it possible to tell MSI that if
Ha ya, good idea. It looks like I need to read up on how to make a
bootstrapper. If anyone has any tips/urls that would help me that'd be
great.
Thanks guys for your help :)
On Thu, 2009-12-10 at 09:14 +1100, Sascha Beaumont wrote:
One file? Then use a self-extracting bootstrapper :)
On
You can use http://dotnetinstaller.codeplex.com for this.
The installer becomes two things:
- a new application that you write that prompts which instance to modify and
invokes the right msiexec command
- your msi
You can condition the first to appear when you have at least one instance and
Hi Yan!
I tried an example found at
http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg27515.html
-- but I'm unable to get it going :(
I want to ignore
Component Id=cmp20CFFB2FF46488AF2CD00E2C9543E202 Directory=INSTALLDIR
Guid=*
(which includes one file)
I used the
Hey Blair-2, I'd be happy to share a log of the installation but
unfortunately I'm doing this for a company and I'm not allowed to post the
information for a log. I've studied the logs myself during patching and it
looks like it doesn't recognize that the install path is different from
I'm writing an install that will create a sql database. I've got my server
set to Windows and Sql Authenication mode.
When I run the install and ask for a user with permission to install the
database, I've got two scenarios:
1) Using a windows network based user. This user is a sql user
You want to match the component element [with a given ID] in order to
omit it, not match the Id attribute:
xsl:template
match=compone...@id='cmp20CFFB2FF46488AF2CD00E2C9543E202'] /
Also be careful to match the exact case of the element and attribute
names.
If it still doesnt work, check that
We've dealt with this extensively.
It's because Windows authentication doesn't work by supplying a
username/password (that's SQL auth). The calling process must be running as
that user, so what you need is impersonation.
You need to ask the user whether he wants to do SQL or Windows auth. If
You will increase your success rate by doing these things:
- Get rid of your self-registration and use the built-in Windows platform
support for services (the Service* elements in WiX).
* the above will require that you perform all your registration using
Registry entries, etc. in the MSI
If you want to omit that component completely, try the following XSL
template:
xsl:template
match=wix:ComponentGroup/wix:compone...@id='cmp034A7A0245A16CFBB38E35D5
1794CF21']
!-- JUST DO NOTHING HERE --
/xsl:template
This should find the mentioned component and write nothing to the
Hoorryy! That's doing it :-)
I wonder how complicated something as simple as grep -v can be ...
Anyway, I'm going to wix now :)
Thanks a lot, Yan! (and also Peter)
Markus
On Dec 10, Yan Sklyarenko y...@sitecore.net wrote:
If you want to omit that component completely, try the following
A cursory look suggests that dotNetInstaller will be a fantastic
solution. Thanks much!
On Thu, 2009-12-10 at 09:15 -0500, dB. wrote:
You can use http://dotnetinstaller.codeplex.com for this.
The installer becomes two things:
- a new application that you write that prompts which
You dont need to specify wix or component group. The component element
will be matched when the matching algorithm reaches it and component is
not used in any other contexts so specifying Component by itself is
fine.
However, since it appears wix is not your default namespace, you will
need to
The best practice for install path is
%ProgramFiles%\company\product, correct? We allow the customer to
(optionally) change the install path during install. This is where I
get confused. Do we allow them to change the whole path including
product? Or just %ProgramFiles% portion? Just the
On Dec 10, Tony yellowjacketl...@gmail.com wrote:
The best practice for install path is
%ProgramFiles%\company\product, correct?
Although I've seen this sometimes, it doesn't seem to be used generally.
If I look at my Program Files folder, most seem to be product or
company product.
What does the log say about the component statuses?
-Original Message-
From: XorPtr [mailto:reaper4...@gmail.com]
Sent: Thursday, December 10, 2009 6:27 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching problems with alternate directories
Hey Blair-2, I'd be
All of the components are listed as:
Installed: Local; Request: Local; Action: Local.
Blair-2 wrote:
What does the log say about the component statuses?
-Original Message-
From: XorPtr [mailto:reaper4...@gmail.com]
Sent: Thursday, December 10, 2009 6:27 AM
To:
And yes, we need to make this experience better. There just wasn't time to
get all the way there in WiX v3.0.
On Thu, Dec 10, 2009 at 7:35 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote:
You dont need to specify wix or component group. The component element
will be matched when the matching
Yes, there definitely is. Feel free to file a bug then use .wixlibs instead
of Merge Modules. wink/
On Thu, Dec 10, 2009 at 1:03 AM, John Aldridge j...@jjdash.demon.co.ukwrote:
On 09/12/2009 17:55, Wilson, Phil wrote:
All the CommonFilesFolder values in merge modules are by convention
We develop multiple applications using the same framwork, hence we put some
DLL files in the GAC.
Now I’m trying to patch an assembly in the GAC to a new version. I’m giving
it a new strong name by increasing the build number and are then updating my
application by reinstalling the MSI (minor
Hello,
You may have already tried this but sometimes opening the msi and
applying the patch with Orca can point out things that are buried in a
verbose log like removing a component from a feature during a patch etc.
Thanks,
Tom
-Original Message-
From: XorPtr
Ok, but this localization is for generic errors while processing virtual
dirs? If is, I can't edit it to show specific error.
-Mensagem original-
De: Rob Mensching [mailto:r...@robmensching.com]
Enviada em: quinta-feira, 10 de dezembro de 2009 05:35
Para: General discussion for Windows
I definitely reviewed the tables for both my installer msi as well as my
patch msp while trying to figure out this problem. I've never heard of
applying a patch using orca before though, I took at look but didn't see an
obvious way of doing this. Could you let me know how to use orca to apply
I cannot for the life of me work out how to add files when using a delta
patch. It works easily enough without the delta flag even when not creating
a new component for the new files (just adding them to an exisiting one).
However with the delta patch i always get
Info 1334. The file
Yes, that is what I wanted.
Why? well, the default installation will be C:\PF\ProductName\VX.Y where we do
not expose the ProductName\VX.Y (to make sure we control that path on SxS
installations)
But if the user selects the advance installation, we only want to show C:\PF
for them to see
I'm using WiX 3.0 in Visual Studio 2008.
I have created an MSI using WiX. I now have an issue with the displayed file
size in the Custom Setup screen. I have 9 features to install: the core files,
plus 8 optional files. These optional files are quite large, between about 60
and 150 MB each.
Thanks for the tip Tom, I'm looking into at least one discrepency that I saw
come up after the Orca/patch transform. I'm not sure if it's causing this
error or not but chances are it would have caused problems down the road.
The second issue you mentioned I was curious about as well. Do you
You said something I was not aware of. add that local user/group to the
appropriate domain group. Can you really add local users and groups to a
domain group? Where can I find documentation that explains how to do that? I'm
an AD newbie.
How would you handle a database deployment that needs to
Hello,
Try looking at the property dump section of a verbose log and compare
the directory table entry values between a good default install and a
bad patch/repair/uninstall. INSTALLDIR is has been an issue for me in
the past.
Thanks,
Tom
-Original Message-
From: XorPtr
http://www.tramontana.co.hu/wix/lesson6.php#6.7
Also, verify that it is not defined twice. AFAIR, certain WiX UI mode has it
defined...
-- Yan
From: Robert Hermann [mailto:rob.herm...@nicewareintl.com]
Sent: Thu 12/10/2009 20:51
To: General discussion for
Something here on that:
http://blogs.msdn.com/astebner/archive/2008/08/10/8847259.aspx
and you should keep the assembly name values the same (so don't change the
strong name).
Phil Wilson
-Original Message-
From: DanR [mailto:daniel.roberts...@repab.se]
Sent: Thursday, December
Thanks for all the pointers! I grouped the non file data in this recommended
method and it is working beautifully.
Thanks!
Uma-
-Original Message-
From: John Nannenga [mailto:john.nanne...@microsoft.com]
Sent: Wednesday, December 09, 2009 7:50 PM
To: General discussion for Windows
On 10/12/2009 17:10, Rob Mensching wrote:
Yes, there definitely is. Feel free to file a bug then use .wixlibs instead
of Merge Modules. wink/
On 09/12/2009 17:55, Wilson, Phil wrote:
All the CommonFilesFolder values in merge modules are by convention
appended with a mangled guid, but as far
One thing to consider with this type of requirement, is how to define
the scope of installation
Many setup developers consider install as a much narrower scope than
those who are defining the requirements. Leveraging a configuration
utility on MSI setup completion (via a bootstrapper or the
If the file didn't exist in the baseline image there really shouldn't be a
difference for that file by merely adding the delta switch.
Is this something where you can share the wixmst file with me?
-Original Message-
From: nearnick [mailto:n...@nearglobal.com]
Sent: Thursday, December
In article 4d6ef6e1711cde4e93d1f1e591a614d6345...@nl1mail0302.global.sdl.corp,
Igor Paniushkin ipaniush...@sdl.com writes:
It is not really related to your question, but I had a question about
popup message box from custom action and I got an answer from Bob
Arnson:
Set a property in
43 matches
Mail list logo
