Thank you very much for explanation. Looking forward for your solution.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Friday, February 19, 2010 1:10 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] How to determine current culture in W
http://wix.sourceforge.net/releases/3.0.5419.0/ProjectAggregator2.msi
On Thu, Feb 18, 2010 at 4:01 PM, Zhou, Lei wrote:
> Could someone please send me a copy of ProjectAggregator2.msi to
> lzhou8(at)yahoo(dot)com?
>
> I know that VS 2008 and later won't need this file. But my company won't
> let
Hi All,
I have a question about installing apache tomcat as prerequisite using WiX
Here is my problem:
I have application that needs Apache Tomcat to be installed before my
application run. First, i try to install jakarta-tomcat-5.0.28.exe via
bootstrapper, but i wait for more than 10minutes and
Hello,
I'm using XmlConfig quite extensively and have run into a few cases where
using Node="value" is not allowing me to do what I want. The default
behavior appears to be:
-If the attribute does not exist, create it with the specified value
-If the attribute does exist, overwrite it with the s
Could someone please send me a copy of ProjectAggregator2.msi to
lzhou8(at)yahoo(dot)com?
I know that VS 2008 and later won't need this file. But my company won't
let us upgrade VS.
Thank you.
Louis Z.
-Original Message-
From: Zhou, Lei [mailto:lz...@sychip.com]
Sent: Wednesday, Febru
If the RegistrySearch/@Win64 attribute is not set to "yes" will always look
in the "32-bit" registry, which means that the "Wow6432Node" part of the
path is inserted for you automatically.
-Original Message-
From: Dane Anderson (Acro Service Corp) [mailto:a-daa...@microsoft.com]
Sent: Thu
Do you know what component(s) install the file in question? If so using
ComponentSearch would likely be a better approach.
--
Bryan
-Original Message-
From: Dane Anderson (Acro Service Corp) [mailto:a-daa...@microsoft.com]
Sent: Thursday, February 18, 2010 2:12 PM
To: wix-users@lists.sour
The culture (as it comes from the .wixproj file) is currently used in
linking and binding, not compiling. It is possible construct the build
system such that you compile just one time and then link for each culture.
As a result, the preprocessor doesn't necessarily ever have a way to know
what cult
>
> Yes.
>
...
>
> I have my installer for my library that installs just fine. For versioning
> controls issues, I need to be able to run the multiple different versions of
> the application. These are installed in the GAC and the file system. The
> file system includes the version number (c:
Yes.
-Original Message-
From: Gary Smith [mailto:gary.sm...@holdstead.com]
Sent: Thursday, February 18, 2010 9:15 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] Same app, different versions
I have my installer for my library that installs just fine.
To understand this issue: your application (when it was per-user) was
installed into the original user's account (not the admin's account). The
admin simply allowed the installation (in UAC it is called
"over-the-shoulder" authorization).
Most installations should have Package/@InstallScope set to
I need to set up a launch condition that prohibits install if a particular file
is NOT installed on the machine. What I have tried
(that did not work) was:
The reason for TWO directory/file s
Hi All,
Is it possible to determine the culture using preprocessors directives?
I.e. I can specify in the Project Properties -> Build -> Cultures to Build
several cultures. For example "en-US;uk-UA". After that I will receive 2
MSIs after the build. But I want to include some specific compo
Repair is feature based, so a feature that has a repair entrypoint (like an
advertised shortcut) will repair when the shortcut is used. If the file that
doesn't restore is in another feature, then it won't repair until an entrypoint
in that other feature is used, or you do a right-click Repair o
I have my installer for my library that installs just fine. For versioning
controls issues, I need to be able to run the multiple different versions of
the application. These are installed in the GAC and the file system. The file
system includes the version number (c:\programs files\myapp\x.x
> Sounds like your package is per-user. See the Package/@InstallScope element.
Yes, setting the InstallScope to perMachine seems to have solved this issue.
Thanks.
--
Download Intel® Parallel Studio Eval
Try the new sof
Sounds like your package is per-user. See the Package/@InstallScope element.
On Thu, Feb 18, 2010 at 8:24 AM, Gary Smith wrote:
> Hello,
>
> I'm run into a situation where the installer generated from WIX doesn't add
> itself to the add/remove programs file. Here is the case when this happens.
>
Hi,
Could you please give me a confirmation, if I understood correctly the next
behavior? If I delete a file (let's say file1.dll) from the installation
directory and after that I start the application (the exe file), the installer
gets into action and reinstalls file1.dll.
If I do the same w
Hello,
I'm run into a situation where the installer generated from WIX doesn't add
itself to the add/remove programs file. Here is the case when this happens.
The OS is Windows 2008.
When I install the msi as myself, I'm prompted for admin account (since I'm a
non-privileged user on the sys
Thanks dude, its work. :)
On 18 February 2010 01:33, Yan Sklyarenko wrote:
> I guess you should save those values to the registry (see RegistryKey /
> RegistryValue elements) and use the RegistrySearch element to populate
> the properties with those values. In this case, your uninstall should go
All - I could use some help in deciding the best approach for creating an
upgrade strategy before the current product is RTM. Just in case I need to make
any changes to the existing installer before releasing it. If there are any
good articles on this please refer them to me.
Background : The e
Hello WiX users,
this not really just a WiX question but a general for MSI based installations.
Is there a good and secure way to detect if another MSI installation is
allready running before starting another one which would fail with Error Code
1618?
I have found two possible ways:
1) There e
I guess you should save those values to the registry (see RegistryKey /
RegistryValue elements) and use the RegistrySearch element to populate
the properties with those values. In this case, your uninstall should go
smoothly.
-- Yan
-Original Message-
From: Thu Rein Win Htet [mailto:trwh
Hi,
I am getting error while uninstalling my application, my database is
not get dropped and the iis web application also not get removed,
instead I am getting error message and the uninstall transaction end
unsuccessfully. I am using property to get the user input in order to
set up db and iis,
I don't think you can do it without custom action. However, it should be
pretty simple:
1. Use the standard RegistrySearch functionality to get the value you
need into a property
2. [CA here] Modify the property the way you need (increment, for
instance)
3. Use the standard RegistryKey/Reg
Keep WixUsers on the thread so others can also learn and contribute.
In WiX 3.0, I only see "raw" used with RegistrySearch and "string" used with
Registry. I don't see anywhere that you have a choice between the two.
-Original Message-
From: sean farrow [mailto:sean.far...@seanfarrow.co.u
26 matches
Mail list logo