Thanks for the help Nick and Phil!
You guys have helped me a lot here. I am beginning to see the light.
I've got SAME_VERSION set to NOT only-detect because we use the 4th part of
the version number for upgrades. I've got to allow version 1.0.0x150 to
upgrade 1.0.0x149, for example.
I have
Now I see the rest of the threads. :/
On Fri, Dec 5, 2014 at 2:13 PM, Jeremiahf wrote:
> Did you set a condition level under the feature Id??
>
>
>
> On Fri, Dec 5, 2014 at 9:27 AM, Marek Mielcarek
> wrote:
>
>> Thank you for your help Jeremiah. I actually tried that before I sent the
>> mess
Did you set a condition level under the feature Id??
On Fri, Dec 5, 2014 at 9:27 AM, Marek Mielcarek
wrote:
> Thank you for your help Jeremiah. I actually tried that before I sent the
> message to this group.
> Apparently, it is not allowed to place "Condition" with a message inside a
> Featu
Based on input in this thread I concluded that using embedded transforms
would not work in a Burn driven scenario reliably. At the time I had
difficulty understanding how to allow the packages to be created with
multiple cultures in separate output folders and then pull those back into
the bundle.
I agree - all you said is very true.
However, as I am sure you know, there is always more to the music than eye can
see... there was an old contract between previous guy and information systems
that installer failure should demonstrate as full-stop of the process. They can
detect that through
I built C# dll with x86 release mode and i Ran heat over it
the heat cmd:
D:\>heat file testcom\testCOMdll32.tlb -srd -sfrag -suid -svb6 -gg -g1 -out
"D:\testcom\testcomtlb.wxs"
Windows Installer XML Toolset Toolset Harvester version 3.9.1006.0
Copyright (c) Outercurve Foundation. All rights rese
That error message and error 193 seem to indicate that Heat is
expecting a Win32 Self Registering COM Dll, not a .NET Dll. What are
you expecting to harvest?
---
Phil Wilson
On Fri, Dec 5, 2014 at 8:24 AM, ssmsam wrote:
> Hi
>
> I am harvesting a x64 C# COM exposed dll using heat.ex
I don't know how much this is related to your problem, but mapped
drive letters are difficult for a number of reasons. They are not
system wide because they belong to the user profile. There's also the
issue that the system account usually has limited access (or none) to
the network. To make it eve
You said that you wanted this to work through automation when deployed to
various machines. Having a message might not be necessary, if, using a
feature condition, you never allow the installer to get into a bad state in
the first place.
Allowing a user (or automated process) to choose a possibly
There's nothing to prevent multiple products being returned - it just
means there are several installed products on the system that share
the same UpgradeCode. In your case, I guess Nick is saying that one of
the multiples returned might be your own. It looks like the different
languages all share
Thank you Rob. That's exactly the way I've taken. And yes, you are correct, the
problem is that although LaunchConditions would have been perfect place, there
is no knowledge of Features because it is too early...
I think we can close this case with CustomActiion being really the best way to
go
If you need to block an installation post-CostFinalize use a conditioned error
custom action. LaunchConditions is not scheduled late enough.
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Marek Mielcarek [mailto:mmielca...@actuate.c
Yes, except that "Condition" cannot use "Message" when placed inside Feature.
I already said that I tried it before even sending question to the group.
Original Message
From: Pavan Konduru
Sent: Friday, December 5, 2014 12:18
To: General discussion about the WiX toolset.
Reply To: General di
This is a good solution from Nick!
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: Friday, December 05, 2014 7:36 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] "Condition" problem
Use a feature condition. A feature condition is where a Conditi
It's about Windows Installer functionality not WiX functionality.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Samir [mailto:samir.elyahia...@hiq.se]
Sent: Friday, Decem
On Fri, 5/12/14, James [via Windows Installer XML (WiX) toolset]
wrote:
Subject: Re: Deploying multiple cultures using Burn/MSI(s). Wix 3.9 issue??
To: "James"
Date: Friday, 5 December, 2014, 9:10 AM
Hi,
Have you found a solut
Hi,
Have you found a solution for this? Are there any pointers for this ?
I have exactly same issue.
-James
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7598436.html
Sen
Hi
I am harvesting a x64 C# COM exposed dll using heat.exe. Though it creates a
component with the file element only.
I throws following warning:
heat.exe : warning HEAT5150 : Could not harvest data from a file that was
expect
ed to be a SelfReg DLL: D:\testcom\testCOMdll.dll. If this file does
It looks like what you have is correct. You have a SAME_VERSION property.
Although you might want to set OnlyDetect to yes if you want to keep the
existing product there and not overwrite it.
Then, use a launch condition to stop the new installation from going through
if SAME_VERSION is found. The
Use a feature condition. A feature condition is where a Condition element is
placed inside a Feature element. There, it can change whether or not that
feature gets installed depending on if the statements evaluates to true.
It does this by changing the Level of the Feature:
If S
Thank you for your help Jeremiah. I actually tried that before I sent the
message to this group.
Apparently, it is not allowed to place "Condition" with a message inside a
Feature.
WiX compiler generates this: "The Condition element contains an unexpected
attribute 'Message'" :(
-Orig
That makes a little more sense now. Try placing a condition in your feature
that includes a condition message. The condition message should reference
the condition using similar to what Pavan gave an example of.
example for .net 4 detection just to give you an idea of what I am talking
about:
A while back I was also struggling with understanding the
DependencyExtension. (My razor is often dull. ) I was trying to
assure that a particular version of one dependency was not removed after my
bundle/packages were installed. I came across Rob's advice in the following
link. Since my scenari
According to the documentation for the Requires elements
(http://wixtoolset.org/documentation/manual/v3/xsd/dependency/requires.html),
it can be put inside of a Product element.
I am wondering if that's a feature that hasn't been implemented yet. What
I'm saying is, it sounds like the WiX team wou
Thanks for the reply Namrata Kumari.
What I'm guessing that you are saying, is that removing files on the network
is not supported by WIX. Since I'm able to delete one of the two folders on
the network drive.
Regards Samir
--
View this message in context:
http://windows-installer-xml-wix-tool
Thanks a lot for Your explanations!
I have defined now a property in my GUI, which contains the complete
installfolder-path.
That's a little bit tricky but what shall You do?
Goodbye and have a nice day!
Patrick
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.
You cannot delete files on a network system where you lack the appropriate
rights and also cannot delete read-only, hidden, or system files.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Cant-get-util-RemoveFolderEx-to-work-on-network-drive-tp759
Hi Jeremiahf,
Thanks for your reply =).
Im saving the path in the registy
()
insted of creating it as a directory
(
)
since I understood that the directory would not be saved to the wix
database.
I'm using RegistryValue insted of Registry Element since the wix
documentation says tha
On 12/05/2014 04:51 AM, Nicolás Alvarez wrote:
> 2014-12-04 4:26 GMT-03:00 Valery Portnyagin :
>> On 12/02/2014 10:15 PM, Phil Wilson wrote:
>>> If you're saying that two MSI products are incompatible and you want
>>> to make sure that a product cannot be installed if another one is
>>> already ins
29 matches
Mail list logo
