Your comments are very useful, Edwin. I generally agree with you that we
need to buckle down in WiX v4.0 (where we can introduce breaking language
changes if necessary) and really try to simplify the language, as per:
http://robmensching.com/blog/posts/2010/1/16/Glimpses-of-life-with-WiX-v4.0
On T
Yeah, that's a weird behavior of Windows Installer. If your Package is
compressed but the File is not compressed, Windows Installer expects the
file in the root of the install (where the .msi file is).
On Tue, Mar 23, 2010 at 8:01 AM, Sanjay Poria wrote:
> I'm finding that the Directory/@SourceNa
I inherited an installer with some code that looks like the following:
The LOGDIRECTORY is a variable, and the directory name is derived from it.
Unfortunately, this means that LOGDIRECTORY must always be defined, even
when I'm trying to install a component that has nothing to do with the
The library is useful for simple setup requirements. The library becomes
difficult to use if you have complex requirements that could benefit from WiX
extensions. The library allows the install engineer to define managed custom
actions in the same code that defines the installer so it makes it v
The recommended way now is typically to run heat.exe to "harvest" the com
registration information out of your DLL. This way it won't actually run the
code from the DLL at install-time (which is more likely to fail, won't handle
all of MSI's transactionality appropriately, and is generally a non
I'm working on an installer project that has a mix of legacy VB
applications and .NET applications.
Originally, I exposed /dark /to an existing MSI, but I wasn't happy with
the output. So I thought I'd give /heat/ a try; I used /heat /to melt
the old VB apps down to wxs files and I can sort of
> In general, I personally find the library to be limiting but it does try
> to follow some reasonable design principles for simple projects. It has a
I'm not sure if WiX# ready for prime time or not, as there are parts of
WiX which aren't supported in WiX#, but I've found it helpful in learning
W
I'm moving from a Visual Studio Deployment Project to WiX. In my old
visual studio deployment project I'm installing a DLL and registering it
via setting the Register property to vsdrfCOMSelfReg, and I wish to do the
same thing with WiX. I didn't see anything about registering COM DLLs in
the WiX
http://www.csscript.net/WixSharp.html
"Wix# (WixSharp) is a new member in the CS-Script family. Wix# is a managed
interface to WiX (Windows Installer XML toolset for building Windows
installation packages from XML source code)."
"Wix# allows building a complete MSI or WiX source code by execu
http://www.csscript.net/WixSharp.html
As far as info, there is a tutorial on CodeProject on WiX#.
Jeff
> What is Wix# and nbsbuilder? Where can I get more information about them?
>
> Thanks,
> Ken
>
>
> -Original Message-
> From: s...@pacaccess.com [mailto:s...@pacaccess.com]
> Sent: T
What is Wix# and nbsbuilder? Where can I get more information about them?
Thanks,
Ken
-Original Message-
From: s...@pacaccess.com [mailto:s...@pacaccess.com]
Sent: Tuesday, March 23, 2010 9:55 AM
To: nor...@acm.org; General discussion for Windows Installer XML toolset.
Subject: Re: [Wi
Hi,
I have read that the Upgrade Table must be populated based on the Server 2008
certification guidelines.
My setup msi program is not designed to do upgrades of previous versions.
Should I still populate the Upgrade table? If so, what Upgrade code should I
use? (Since it is not designed to upg
It's about file versions, and always has been (with the exception of the GAC
sometimes). Higher file versions replace lower. The latest version and the
winner is the highest file version. This is a standard Windows Installer thing,
no matter what you use to build the MSI file:
http://msdn.micro
Hello,
What is the best practice for dealing with shared binaries like .NET
assemblies or DLL's?
If I have some number of VS projects that each output a a COMMON.DLL to
their respective bin\Release folder, how can WiX know which COMMON.DLL
is the latest version?
Does WiX have any features sim
I'm finding that the Directory/@SourceName property seems to have no effect. If
I define my source files in a fragment as follows (using the initial example I
gave):
The installer still tries to find "doc
This is a timely thread for me as I have been recently going through this
myself. In my research I found there are two ways to bundle the VC++
runtime:
* With a merge module. This approach is documented
(http://wix.sourceforge.net/manual-wix3/install_vcredist.htm) but has the
disadvantage of tak
I would be interested in whether you are able to *remove* your application
after having installed the VC libs via Merge Modules.
I am seeing the UNinstallation take approximately 5 minutes (while the VC
libs are being removed), with the dialog appearing to be 'hung'.
Most users will give up and ca
Any file you put on the machine during install will be removed during
uninstall unless you specifically say not to.
Same goes for any directories created during install as long as they are
empty when msiexec tries to remove them. If your application has created
any logs or configs in those directo
thanks Pally -the condition worked perfectly!
--
View this message in context:
http://n2.nabble.com/Re-installing-on-windows-server-2008-BUMP-tp4777496p4783442.html
Sent from the wix-users mailing list archive at Nabble.com.
-
Thanks Asiri.
yup did that. need the following arguments:
SECURITYMODE=SQL
SAPWD=
--
View this message in context:
http://n2.nabble.com/install-SQL-server-with-mixed-mode-authentication-tp4757132p4783438.html
Sent from the wix-users mailing list archive at Nabble.com.
---
Thanks Pally and Phil.
I have marked the service as stop at uninstall and the remove file is now
after the stop service.
I ahve put remove folders commands in place - would this automatically
delete the files within the folder or would I ahve to put remove file for
each file contained within it?
You can safely ignore them. They're caused by having either of the VC++
runtime merge modules consumed by your MSI. It's not an artifact of
having both v8.0 & v9.0.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
*
Hi all,
I was going through the improvements that have been made in Wix 3.0. I want
further information about some of them like:
1. Support for all MSI 4.0 features where can I find the list of new MSI
4.0 features and how they are supported in Wix 3.0.
2. Standard UI support, what
Hi all,
I am currently writing an installer that needs to install both Visual
Studio 2005 AND 2008 C Runtime Libraries. The reason is that some of
the binaries I have to install (PostgreSQL) are built with Visual Studio
2005, and my own binaries are built with Visual Studio 2008. Everything
m
Ah! I think now I got it.
I have to add the Merge / MergeRef tags in the app / setup file; right !?
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Dienstag, 23. März 2010 03:07
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Votive - MergeModule depend
25 matches
Mail list logo
