To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Repair Problem
>
> Check out the File Versioning Rules topic in the MSI SDK. It explains this
> behavior.
>
>
> On Tue, Dec 11, 2012 at 3:44 PM, Sanjay Poria
> wrote:
>
> > My c
My company moved to using msi around a year and I authored a major product
release and subsequent patch files (small update msp's that do not increment
the baseline version) using wix. The product contains a number of binary
files. Recently we had an issue where the customer manually replaced a
I have a msi built using Wix3.5 which has a conditional check on .NET 3.5 SP 1
being installed on the target machine like so:
This check fails on Windows 8 (x64). Do I need to make a change to this
condition in order to support windows 8? Are there any other general gotch
Hi,
This is only partially a Wix question but if anyone can help, I'd appreciate it.
I am writing a Wix installer for a windows service that will be installed on a
server. The installer puts files (dll, exes) into the ProgramFilesFolder and
starts the service. It is installed for all users. M
John,
I'm not expert on but
I created a different fragment for each component/file in my original
distribution (a rather tedious process) so that only those files I specify in
my patch specification are included. You may want to try that and see if it
fixes your issue. As far as I know, a
ation)?
Thanks
sanjay
> -Original Message-
> From: Sanjay Poria [mailto:sanjay.po...@xanalys.com]
> Sent: 05 February 2012 21:21
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: [WiX-users] Patching and Pyro Warning PYRO1110
>
> I have cr
I have created an MSI product installer for a product that has a main feature
(call it MF) and a sub feature (call it SF). It is mandatory to install the
main feature but the sub feature is optional.
I am experimenting with creating patches (small updates) using Wix 3.5 for this
product. I hav
the products you release
> regardless
> of customer and you may choose to patch any doc MSIs separately.
>
> Dave
>
> -Original Message-
> From: Sanjay Poria [mailto:sanjay.po...@xanalys.com]
> Sent: 25 January 2012 15:46
> To: 'General discussion for Win
I'm hoping for some advice about MSI and Patching using Wix.
I am currently moving one of products from Installshield to MSI using Wix to
generate it. Our product has a number of different variations depending on
which customer we deliver to. Typically all the different versions differ in a
few
s unless
> you
> use the -sfrag switch.
>
> Torch works with all kinds of files. Windows Installer works best if
> your
> executable files have a version resource that specifies the file
> version but
> it'll will handle unversioned binaries too.
>
>
>
what patches are applied to a product. It depends on how
> you
> want to retrieve the information. You can use MsiEnumPatches() from C++
> for
> example. You could also install something to act as a marker.
>
> Useful links include:
> MSDN on Windows installer
> Pet
I am in the process of writing an installer for a company product (we were
previously using Installshield). Once, released we will need the produce
patches for bug fixes and enhancements. The expectation that these patches will
consist of simply updating some of the released files and/or adding
e resulting string is, maybe you
> are beyond the limit there somehow...
>
> As an alternative, you could define a base path using ?define and
> concatenate the strings to get an absolute path; I've done that as
> well...
>
> -Original Message-
> From: Sanjay Por
Hi,
I am hoping someone can help me here. I am defining a component with a file
like this:
I am using the visual studio 10 to do this. When I build the
project, I get an error on this component only (I have loads of others that
work fine): The system cannot fi
I am tasked with writing an installer to deploy some (.NET) web services on
IIS. Typically the deployment will involve some/all of the following:
During install selecting:
. The App pool (test that the AppPool the user chooses is compatible
with the service/application being installed)
> places, and that's not going to work.
>
> Phil Wilson.
>
>
> -Original Message-
> From: Sanjay Poria [mailto:sanjay.po...@xanalys.com]
> Sent: Wednesday, October 12, 2011 6:47 AM
> To: 'General discussion for Windows Installer XML toolset.'
&g
duplicate the registry entries (a
copy in HKCR and HKCR\Wow6432Node), I can start the COM server without issues
in a 32bit or 64bit app.
Cheers
sanjay
> -Original Message-
> From: Sanjay Poria [mailto:sanjay.po...@xanalys.com]
> Sent: 11 October 2011 22:31
> To: wix-users
I have created a Wix installer for a 32-bit application (not .NET) which
installs just fine. Recently, I had to create a COM Server written in .NET
consisting of a single DLL which also had to be installed (and used by) my
original application.
So basically I wrote the COM server in C# (target
I have a custom dialog in my installation UI (Wix 3.5) which captures some
information using Edit Textbox like this:
1
ORACLEDATABASENAME = ""
Basically I want to fo
I achieve this by using a CopyFile elememt (a child of the File element).
Basically I copy it to the install location and then copy the file to another
arbitrary location like this:
MYDIRPATH
Note that you specify t
ate with the **
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
>
> -Original Message-
> From: Sanjay Poria [mailto:san
I have been tasked with writing a installer for an .NET application (consisting
of a few DLLs and an exe) such that I can install it for a user that does not
have admin rights. Presumably this means doing a per-user install of the
application. I simply need to install the application files and c
mbedded CAB file and Folder
>
> On 3/22/2010 6:46 PM, Sanjay Poria wrote:
> > The problem is that when I run the installer, it still expects to
> find files (doc1, doc2) in the main directory (at the same level as the
> msi) instead of the "DocFiles" directory. Whe
ce structure as above (which made me think everything was specified ok).
Any ideas?
Thanks
sanjay
> -Original Message-
> From: Bob Arnson [mailto:b...@joyofsetup.com]
> Sent: 22 March 2010 14:40
> Subject: Re: [WiX-users] Installing from embedded CAB file and Folder
>
> O
Ohh didn't think I could do that. Thanks. Hopefully that's the best way of
achieving what i'm after.
Regards
sanjay
> -Original Message-
> From: wix-users-requ...@lists.sourceforge.net [mailto:wix-users-
> requ...@lists.sourceforge.net]
> Sent: 22 March 2010 14:41
> To: wix-users@lists.
**
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
>
> -Original Message-
> From: Sanjay Poria [mailto:sanjay.po...@x
You can ignore issue (2), I figured that one out. Any help on the COM
registration issue would be much appreciated.
sanjay
> -Original Message-
> From: Sanjay Poria [mailto:sanjay.po...@xanalys.com]
> Sent: 18 March 2010 13:21
> Subject: [WiX-users] Creating ProgramMenuFol
I am creating a Wix 3.0 installer for a product and have come against a number
of issues (migrating from InstallShield). I had a general look around but
cant find the answers so im hoping someone can help me:
1) The doc tells me that I should have one component per file and I want
to h
I have a similar issue. I think you can use the "heat" tool to recursively
traverse the source directory and generate a fragment consisting of a set of
component/file definitions. I have read that this tool should only be used once
is not intended to be used as part of an automated build process
Hi,
I wish to create an msi installer using wix such that most of the application
files will be embedded into the msi (in the usual way ). However, due to our
build process, I wish certain parts of the installation to be taken from a
folder relative to the msi. So after creation of the msi, I
30 matches
Mail list logo
