Thanks for the reply.
I had checked the log and the RemoveFiles was returning 0. So initially i
thought that was the problem.
But then i tried out the installer on another fresh machine, it worked fine
including Repair,Uninstall
There may have been some issues with my machine since my ARP is all
cl
Thanks Richard and Palbinder
On Wed, Aug 11, 2010 at 7:27 PM, Pally Sandher wrote:
> 1 - http://blogs.msdn.com/b/astebner/archive/2005/12/24/507294.aspx
> 2 - http://www.joyofsetup.com/2007/09/24/test-your-setups-virtually/
> 3 - Debug the failure & fix it so it doesn't fail?
>
> Palbinder Sandhe
thats correct and that is what is given in the wix.chm of wix v3.0
On Fri, Mar 26, 2010 at 2:53 PM, Viv coco wrote:
>
> Hi,
>
>
>
> Why would one do:
>
>
>
> [code]
>
> [/code]
>
>
>
> In this specific case (as ProgramMenuFolder is a predefined directory) the
> "Name" doesn't have any means at
Check the spelling INSTALLLOCATION in the value attribute
On Fri, Mar 26, 2010 at 2:45 PM, Viv coco wrote:
>
> Hi,
>
>
>
> I want to save the path where my binaries are installed somewhere in the
> registry so I'm doing:
>
>
>
> [code]
>
>
>
>
>
> Guid="9
http://wix.sourceforge.net/manual-wix3/util_xsd_xmlfile.htm.
The xmlfile element can only have a Component element as its parent and not
a file element.
On 3/12/10, Anu Dev wrote:
>
> Hi
>
> One of my friend (in cc) is having an issue while transforming the XSLT to
> a WXS file.
>
> XSLT transf
Check this out
http://www.tramontana.co.hu/wix/lesson1.php
About half a page down..
<*Directory* Id="DesktopFolder" Name="Desktop" />
On Mon, Mar 8, 2010 at 7:53 PM, lewisv wrote:
>
> I am trying to put a few desktop shortcuts on the users screen, but I
> really
> don't know why they a
You can try create a registry entry for the Installation directory and then
make your code read the reg entry for the installation path, or save the
path to the file as you said.
You can get the installation path using [INSTALLDIR] or [INSTALLLOCATION].
This will give you the installation path.
O
1)For the startmenu shortcut you need to list ProgramMenuDir into the
RemoveFolder table.
see the link:
http://robmensching.com/blog/posts/2007/4/27/How-to-create-an-uninstall-shortcut-and-pass-all-the
2) The purpose of creating a registry entry under HKCU is to use it as a
keypath to keep ICE hap
As far as the modification of ini files is concerned, you probably won't
need a custom action. There are some built in elements.
http://wix.sourceforge.net/manual-wix3/wix_xsd_inifile.htm
http://wix.sourceforge.net/manual-wix3/wix_xsd_inifilesearch.htm
On Thu, Feb 18, 2010 at 11:13 AM, sean farro
I am using wix to install a file and its shortcut.
i have to use a non-advertised shortcut. i am also setting ALLUSERS=1 (I am
using Win 2003 and wix 3.0)
But i have the following queries:
1) Non advertised shortcuts require a registry entry under HKCU.
So when some other user uninstalls the produc
> I also had a somewhat similar task at hand and i had realized the following
> -
> Chnage id from StartMenuFolder to MyMenuFolder or . any other id
>
>
>
>
>
> Accordingly update other references.
>
> http://msdn.microsoft.com/en-us/library/aa372025(VS.85).aspx
>
>
>
I also had a somewhat similar task at hand and i had realized the following
-
Chnage id from StartMenuFolder to MyMenuFolder or . any other id
Directory String Identifier reference to Directory element where shortcut
is to be created. When nested under a Component element, this attribute's
value
You can also see the "New Link in the Chain" section on the following link:
http://www.tramontana.co.hu/wix/lesson2.php
Or even this link maybe useful
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
On Thu, Jan 28, 2010 at 5:00 PM, Anu Dev wrote:
> Hi
>
> I would like
Check this link.
http://www.installsite.org/pages/en/isnews/200102/CustomSetupOptions.htm
It says
"There's no way to suppress only the second option, and keep the first. Even
if the feature has no sub features, Windows Installer displays the variant
"this feature, and all sub features" of the inst
Hi Nick,
I am not sure of this, but maybe u can build a merge module which has a 32
bit component to make whatever registry entries u wish to have. Then u
can give a reference to this 32 bit merge module in your 64 bit installer
code.(using Merge and MergeRef elements).
This way ur 64 bit installer
You can see the log to find out where the installation is failing.
Use:
msiexec /i /l*r
On Mon, Jan 18, 2010 at 10:51 AM, C P wrote:
> Hi, my Installer is successfully compiled and can be successfully installed
> on few PCs, but on few PCs it shows FatalError dialog right after running.
>
For making a 64 bit MSI u need to set the Win64 attribute in your Component
elements.
You need to set the platform attribute in package element.
Also ProgramFilesFolder becomes ProgramFile64Folder.(and any similar
variables) in 64 bit.
For component element:
http://wix.sourceforge.net/manual-wix2/
Yes.. I too think dats the only way out..
Thanks for you time.
On Fri, Jan 15, 2010 at 2:54 PM, Rob Hamflett wrote:
> In that case I think you'll need to forget the merge module and just add
> the files as you would
> normally.
>
> Rob
>
> On 15/01/2010 09:06, ricky
rge module get prepended with the merge module ID in
> some way. You might
> want to just add the merge module once, build it, and then see what the
> file ID is in Orca.
>
> Rob
>
> On 15/01/2010 08:31, ricky sundrani wrote:
> > Tried using the copyfile element insi
module, or look at
> adding a CopyFile element.
>
> Rob
>
> On 14/01/2010 18:27, ricky sundrani wrote:
> > There is a link:
> > http://support.microsoft.com/default.aspx/kb/326922.
> > What is currently being followed for msvcr71.dll ? WinSxS or application
> &g
Reposting this question :
Is it possible to use the same merge module twice in the same source file.
The above code is giving error:
Error 1 The merge module 'merge2' conta
, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
> -Original Message-
> From: Rob Hamflett [mailto:r...@snsys.com]
> Sent: 14 January 2010 09:29
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Merge Module for msvcr71.dll
>
&
file (referenced in
the merge module) to two locations is not possible.
Or is there a way to do it?
On Thu, Jan 14, 2010 at 5:47 PM, ricky sundrani wrote:
> The merge module i am using is installing the msvcr71.dll in the directory
> where i am puttin the reference to the merge module.
> U
rge Module for msvcr71.dll
>
> Doesn't the merge module install the file to the Windows system folder?
> If that's the case then you shouldn't need to install the file anywhere
> else.
>
> Rob
>
> On 14/01/2010 09:16, ricky sundrani wrote:
> > I am tryin
I am trying to use a merge module for msvcr71.dll since its strongly
recommended to use merge models for re-distributing c runtime libraries.
But i want to copy this msvcr71.dll to 2 different folders on installation.
But using the same merge module reference twice would cause the same file to
be i
still put it in a component to modify? Is there something that I
> am missing?
>
> Thanks!
>
> -Original Message-
> From: ricky sundrani [mailto:rickysundr...@gmail.com]
> Sent: Friday, January 08, 2010 11:53 AM
> To: General discussion for Windows Installer XML t
Re posting the link.
http://wix.sourceforge.net/manual-wix3/util_xsd_xmlconfig.htm
On Fri, Jan 8, 2010 at 10:20 PM, ricky sundrani wrote:
>
> U'll have to use it under a component.
>
>
>
>
> ...
>
>
>
>
> See the link
> http://wix.sourceforge.ne
U'll have to use it under a component.
...
See the link
http://wix.sourceforge.net/manualwix3/util_xsd_xmlconfig.htm
Here see the parents of the XmlConfig element.
On Fri, Jan 8, 2010 at 8:08 PM, Kerber, Cameron
wrote:
> Well I don't see any file search element under Property. Also w
You can use the XmlConfig element to change any xml file.
You can use the attributes of XmlConfig element like
File:
Action:
On:
ElementPath:
Name :
Node
Sequence: < Sequence no of actions>
Here are some links which maybe useful:
http://stackoverflow.com/questions/1648221/deleteing-whole-se
Doing so will probably
> require a significant amount of work.
>
> On Fri, Dec 25, 2009 at 4:35 AM, ricky sundrani >wrote:
>
> > I want to build WixUtilExtension.dll from wix sources.
> > So first i tried to build util.wixlib , but that has references to
> > caerr.wxi,
I don't think you can have one msi for both 32 and 64 bit machines. But you
can have a single .wxs file which produces two different .msi files
when compiled on different architectures. It does this by reading
environment variables or system variables.(PROCESSOR_ARCHITECTURE).
On Mon, Dec 28, 2009
I want to build WixUtilExtension.dll from wix sources.
So first i tried to build util.wixlib , but that has references to
caerr.wxi, wixca.dll and other files.
Not , I am trying to build wixca.dll from wix sources. But haven't been able
to do so yet. I did go through this blog, but this was not of
Hi Bob,
I set the REINSTALLMODE property to 'p' and its working fine now as per my
requirements.
Thanks.
On Tue, Dec 1, 2009 at 5:59 PM, Bob Arnson wrote:
> ricky sundrani wrote:
> > I have a component whose purpose is to modify the machine.config file.
> What
> >
I have a component whose purpose is to modify the machine.config file. What
it does is add a new line to machine.config using XmlConfig element.
But when i clicked on the repair button for repair, the component described
above is called again i.e the line which was added to machine.config is
added
34 matches
Mail list logo
