I don't know why your project is getting rebuilt but you can simply sign the
file in the postbuild event and then even if it is rebuilt the signed file
will be picked up.
Umesh
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/I-m-losing-the-digital-
Whole idea of bootstrapper for .NET is to load the prerquisite .NET
libraries to make it possible to run managed applications. How can you have
a managed application driving this bootstrapper?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Net-
A general solution to avoiding 'ugly DOS windows' is to use CAQuietExec from
WixUtilExtension.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/InstallUtil-exe-alternatives-tp6349071p6350583.html
Sent from the wix-users mailing list archive at Nabble
Yes. Your MSI is cached in a subdirectory of Windows. A user won't be
accidentally deleting this.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-User-Where-is-custom-action-dll-when-uninstall-tp6350245p6350535.html
Sent from the wix-users maili
Shouldn't your PathEdit control have Property=_BrowseProperty ?
Look at how _BrowseProperty is used in the DirectoryCombo, DirectoryList and
PathEdit.
http://www.tramontana.co.hu/wix/lesson8.php
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Pro
Better late than never is right!
Install logs do sometime show these error messages but as I have indicated
earlier nothing is amiss. So we decided to ignore the benign error. Thanks
for reassuring me that others have also seen this weird behavior.
It may just be an undocumented bug in the Window
How have you defined the features?
Feature element has a ConfigurableDirectory attribute that should be used if
the user can change the default target directory.
I think that you may have to define different features targeting these
directories if each of these directories can be independently s
When is REP scheduled?
Is the agent installed in GAC?
Depending upon answers to these you maybe running into a bug in Wiindows
Installer.
See if http://support.microsoft.com/kb/905238 is applicable in your case.
Umesh
--
View this message in context:
http://windows-installer-xml-wix-toolset.
I have faced this problem sometime back and I had tried several approaches
based on what others had suggested. I will enumerate them here but I was not
successful in solving this (Perhaps I was committing other errors).
1. Simulate installshield's 'always Overwrite' attribute. You can try
giving
Rule for unversioned files is that if a file is modified after creation then
it will not be overwritten. This is with the rationale that if a user has
modified it then it should be left undisturbed.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX
Hi,
Could someone suggest what can prevent a FilesInUse or MsiRMFilesInUse
dialog from being shown during an upgrade?
I posted this in a wrong subgroup so I am posting it again.
Thanks
Umesh
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/FilesIn
My previous post seems to be mangled in the editor so without giving the
markup I will just suggest the way to do it.
You can do it by publishing property changes depending on the state of the
selection tree in SelectionTree control and then later using those
properties.
This was suggested by Ni
You can do it by publishing property changes depending on the state of the
selection tree in SelectionTree control and then later using those
properties.
and then handling disable for the next button
DisableButton = "1"
DisableButto
Hi,
Can someone explain how to achieve this?
We have a Major Upgrade task which seemed to work with early schedulling of
RemoveExistingProducts.
But it started failing due to a bug in MSI where an assembly was being
placed in GAC and used duing installation for a custom action. During
upgrade th
I faced an identical situation.
New version application has a bootstrapper to upgrade to a higher DotNet
version. Older app crashed as it could not handle the upgrade of dotnet.
I wrote an unmanaged program which stopped older application process and
then launched the installer (with its boot
What access level are you using for OpenProcess() ?
A simple PROCESS_TERMINATE is sufficient. If you are using
PROCESS_ALL_ACCESS it will fail.
I had experienced the same problems and after changing the dwDesiredAccess
param it worked well.
Umesh
--
View this message in context:
http://window
Hi,
I am converting the setup to conditionally build for 32 or 64 bit platform.
Would the following code suffice to make sure that 64 bit WIXCA is used for
64 bit platform?
Code snippet:
.
...
Similarly writing code for
I think, if it is public (All caps as you have shown in your example) and
secure it should be accessible.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Update-property-in-deferred-action-tp5997460p5997559.html
Sent from the wix-users mailing l
I remember using a Windows API to copy files at boot time if they are in use
MoveFileEx (?). Otherwise, files to be copied are copied in a batch file
which is run at boot time through runonce key.
This was before MSI and WIX.
MSi and WIX may have an easier and more acceptable way of doing it a
How do we access it?
Specifically, I would like to show the user in the UI - during upgrade -
that the previous version is installed at "" location and upgrade will
take place by placing newer version in the same directory.
Thanks
Umesh
Rob Mensching-7 wrote:
>
> Hmm, I don't remember
Hi,
I want to allow same version upgrades to take care of the fourth element in
the version numbers.
According to
http://wix.sourceforge.net/manual-wix3/wix_xsd_majorupgrade.htm, I can use
AllowSameVersionUpgrades attribute to do this. However, I am getting build
errors as this element is not re
Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Umeshj [mailto:[hidden email]]
Sent: 18 November 2010 07:21
To: [hidden email]
Subject: Re: [WiX-users] How to refer WIX properties within .wxs files
I have a similar problem. However, this solution does not seem to
I have a similar problem. However, this solution does not seem to work for
me.
I am trying to install an application to
c:\PlatformSpecificProgramFilesFolder\[Manufacturer]\[ProductName]
Here is the relevant directory structure
...
Why are you copying this to the user's system?
Just use it like this:
refer to it with the id.
This way it will stay with your MSI and uninstall will have access to it.
Umesh
sagar shinde wrote:
>
> Hi,
>
> I created one custom action dll file,
> which is copied to destination computer.
Thanks Nick,
It works now. Adding these property change events to the SelectionTree did
it.
Umesh
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/FeatureSelection-Dialog-tp5536563p5540932.html
Sent from the wix-users mailing list archive at Na
Thanks for your help. Unfortunately this does not work.
As you had suggested I created a bootstrapper file. Located it in c:\
Changed to the V3.5 of the framework directory and ran msbuild with the
argument bootstrapper file.
Here is the output.
---
C:\>cd C:\Windows\Microsoft.NET\Framew
Hi,
I know that this group has discussed bootstrapper related questions a number
of times but I cannot find a solution to the following problem.
I think it would help others who may want to use the bootstrapper with the
Wix project so I am posting here.
I am trying to use the Microsoft boot
There is a typo in the post which is not present in the actual code. This was
a result of copy and paste.
Markup should read as:
" TabSkip="no" Default="yes"
>
NOT((&FeatureA=3) OR
(&FeatureB=3))
(&FeatureA=3) OR (&FeatureB=3)
1
1
My
Hi,
In our feature selection dialog we are using SelectionTree control.
The selection tree shows only two features: featureA and featureB.
When no feature is selected the 'Next' button should not allow the user to
continue further. It should be disabled.
Here is the relevant markup for 'Next' b
Sorry for the typos in ConfigurableDirectory.
Umesh
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Configurabble-Install-Directory-tp5351039p5360604.html
Sent from the wix-users mailing list archive at Nabble.com.
---
Hi,
Thanks for your response. Earlier I had tried ..
I was setting "INSTALLDIR" property to the directory of my choice.
Features w
...
..As both features were going to the same directory.
I will try what you had suggested.
Thanks.
Umesh
--
View th
31 matches
Mail list logo