Hi,
I am new to Wix and hence, this question may be rather stupid. However, I did
not find an answer in the manual.
I use a simple setup with the standard WixUI_FeatureTree. When clicking on a
feature, one is allowed to choose to install a feature locally or not and to
install it when
Hi Bob, This is my code. Here, I am removing features using Remove control
event on next button of ComponentType dialog. This dialog is used to make
selection from server, client or developers based installation. if User has
selected “Server based installation” in ComponentType dialog then
I know that it is possible to specify the license file via e.g.
-dWixUILicenseRtf=path\de-de\german_license.rtf
option and that hereby it is possible to use a localized license file.
I use Wix with Visual Studio 2005 and want to pass this parameter to
light.exe but unfortunately, I have no
Hello WiX developers,
I have a serious problem which seems like a bug in IIS extension to me.
I have an installation which can install multiple instances, let's say,
2 for simplicity. Each one installs a web site in IIS 6. So, Instance1
installs WebSite1, Instance2 installs WebSite2.
The
Howdy, Daniel. Let's see if I understand you proposed workflow:
1. The installer contains the SSIS package and custom .NET executable.
2. The installer solicits connection information during setup that you want to
write to an XML config file.
3. The .NET application will execute the package to
Joe, that smells like your MSI can't find either SQLCMD or your SQL script.
I'll bet it's the SQL script; it's either already removed before your call to
SQLCMD or you need to provide the full path to it.
-Original Message-
From: Joe Osman [mailto:joe.os...@tait.co.nz]
Sent: Sunday,
I believe you need to change your Product Id= to use a different GUID than
your previous package and also change the version. You might also need to add a
Package Id=----, but not sure it is required
to remove the previous package.
HTH
-Original
Sorry, I was lost in translation. The attribute is AllowAdvertise=no.
-Original Message-
From: Robert Nickel [mailto:robert.nic...@dcam.de]
Sent: Tuesday, February 03, 2009 11:44 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to disable the option to install a
How to unsubscribe from group.
Thanks Regards,
Chandrashekar vuppala
From: Yan Sklyarenko [mailto:y...@sitecore.net]
Sent: Tue 3/02/2009 4:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] IIS Rollback action deletes all
Hello everyone,
I currently maintain a number of WiX3 based MSI setups that use custom UI.
For the custom UI I create a copy of the wixui sources from the WiX sources
package, customize it, create my own wixlib and link against that instead of
creating a reference to the stock
Hi,
I have a directory tree I want to install at a user-specified location.
It's as simple as that... however, I don't want to manage large xml
definition file with an entry for each file to be packaged.
Is there a way to do that with WiX?
Thanks.
Martin
I'm pretty sure that there used to be, Martin, but I don't see it in v3; IIRC,
wildcard support was explicitly dropped by design.
If you figure it out and I missed it somewhere, LMK! We wrote a custom MSBuild
task to rip through a directory tree and write out include files for WiX to do
this.
Thanks David,
What about using v2? Can you point me to the place to look for the feature?
Martin
David Reed wrote:
I'm pretty sure that there used to be, Martin, but I don't see it in v3;
IIRC, wildcard support was explicitly dropped by design.
If you figure it out and I missed it
V2 is the same as v3 in this regard. No built-in support for wildcard
inclusion of files.
-Original Message-
From: Martin Sustrik [mailto:sust...@fastmq.com]
Sent: Tuesday, February 03, 2009 11:47 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Very
:(
Any other tool that would be basically simple zip/unzip + add a nice
windowsey GUI to the install?
Martin
Chad Petersen wrote:
V2 is the same as v3 in this regard. No built-in support for wildcard
inclusion of files.
-Original Message-
From: Martin Sustrik
And in my case, I'm doing the ripping using Perl instead of MSBuild.
Works for me, at least.
(Of course, the package I'm writing is customized FOR packaging Perl and
perl modules on 32-bit Windows, but a lot of the code should still be
usable, and I may very well generalize it later! AND, it's
Hello Everyone,
I have a checkbox in one of our Installation UIs.
Property Id=DELETE_DB Value=1 /
Control Id=DeleteDb
Type=CheckBox
X=100
Y=100
Width=150
Height=30
Text=Delete previously created databased
Property=DELETE_DB
CheckBoxValue=1
/Control
I have assigned DELETE_DB
1. Don't do it - in the long run it will bite you.
2. Take a look at Inno Setup.
3. If you stay with WiX try using the Heat tool to create the XML, on
simple installs it does a pretty good job.
Neil
-Original Message-
From: Martin Sustrik [mailto:sust...@fastmq.com]
Sent: 03 February
Do you need to handle upgrades? If so, how are you going to handle file
renames, deletions, etc?
I wrote my own utility (in C#) to rip through a directory and generate WiX
source (similarly to heat.exe) except that it specifies FileSource differently
so that I don't have to touch up the
Castro, Edwin (Hillsboro) wrote:
Do you need to handle upgrades? If so, how are you going to handle file
renames, deletions, etc?
Install into single directory. With new version delete the directory and
install in anew. No registry keys. No icons. No menu items. No fancy
stuff :)
Martin
Ok, let me explain the problem.
We have a multiplatform product that's distributed on ~10 platforms.
Handling a separate distro project for windows is not an option - we
would get out of sync pretty quickly. Build system and distribution
system has to be unified.
On other platforms it's
Stefan Kuhr wrote:
Is there meanwhile a simpler way of creating a custom UI? Creating a custom
wixlib gets tedious over time and I always have to update my copy of the
sources if I adopt a new WiX3 build in case files in the wixui extension
have changed. Also, my builds take a much longer time
Robert Nickel wrote:
I know that it is possible to specify the license file via e.g.
-dWixUILicenseRtf=path\de-de\german_license.rtf
option and that hereby it is possible to use a localized license file.
You can also use the WixVariable element in a source file.
--
sig://boB
Martin Sustrik wrote:
This won't work on Windows, so we would like to take the directory, zip
it and deploy it that way.
Then you don't want to use Windows Installer or WiX. Use Inno Setup
instead; it supports what you're looking for without the risks of trying
to twist MSI to make it
Robert Nickel wrote:
Sorry, I was lost in translation. The attribute is AllowAdvertise=no.
Try both; that will show the feature and not let it be advertised or
removed.
--
sig://boB
http://joyofsetup.com/
--
1 create a self extract zip
2 embeed zip file in wix
3 move zip file to directory
4 run custom action to start file like start a exe
on reinstall remove all files from directory then 1-4
Citerar Martin Sustrik sust...@fastmq.com:
Castro, Edwin (Hillsboro) wrote:
Do you need to handle
jagdish.sakhiya wrote:
Hi Bob, This is my code. Here, I am removing features using Remove control
event on next button of ComponentType dialog.
The only way to do that is to set the level of all features to 0, then
AddLocal the ones you want enabled.
--
sig://boB
http://joyofsetup.com/
What about:
1. make zip by hand
2. add the zip file as a single file into a wix project
3. add a custom step that unzips the file
Would that work?
Martin
Curtis Jewell wrote:
And in my case, I'm doing the ripping using Perl instead of MSBuild.
Works for me, at least.
(Of course, the
Thanks Neil.
After hours searching, I found out this:
http://www.dizzymonkeydesign.com/blog/misc/adding-and-customizing-dlgs-in-wix-3/
I followed the instructions in the post above, and I added Desktop Shortcut
support successful.
But, when I tried to followed the same way to add Quick Launch
Thanks Bob.
I'll try the merge module.
/Brian
From: Bob Arnson b...@joyofsetup.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Wednesday, January 28, 2009 7:36:36 PM
Subject: Re: [WiX-users] VC 9.0 Merge
Thx. Will try.
Martin
patrik.torn...@addiva.se wrote:
1 create a self extract zip
2 embeed zip file in wix
3 move zip file to directory
4 run custom action to start file like start a exe
on reinstall remove all files from directory then 1-4
Citerar Martin Sustrik sust...@fastmq.com:
Pardon a lurker.
I only know enough to be dangerous on a *nix box. Seems to me, though,
that if you are shipping your product via what sounds like conventional
*nix ./make ./configure and you want to get the same sort of flavor on a
Windows box then WiX isn't what you want. MSBuild is closer to
Related question: Why should the old version even have to be uninstalled first?
Shouldn't it be enough to just install on top of the old version?
If so, how would one do that?
/Thomas Due
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: 3. februar
Thomas,
Removing the old version is important if the new version is structurally
different (eg different assembly names, different registry keys, different
folder layout). Believe me it happens.
To just go over the top look at Minor Upgrades, these work if you are simply
refreshing existing
34 matches
Mail list logo
