I'm trying to ship sql express with my setup but it always wants to download
the package instead. The options ComponentsLocation=Realtive and
CopyComponents=True should do the trick but sqlepr32.exe isn't being copied
anywhere. I'm using the latest wix 3 build and studio 2005. Below is my
Shouldn't that be Relative not Realtive?
Andreas Owen ao...@1eeurope.ch
01/20/2009 12:05 AM
Please respond to
General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
To
wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net
cc
Subject
[WiX-users]
Hello WiX community,
It seems I have found a bug in IIS extension. I hope I'm wrong and
somebody will point me to my mistake.
First of all, WiX version is 3.0.4917.0. I'm trying to configure the
existent website in IIS 5.1. Here is my component definition:
Component DiskId=1
hi guys,
thanks for that, we will look into the setupbld options for bootstrapping
yes the protocol handler is just registry keys, i couldnt find a clean
example of creating registry keys within registry keys int the tutorial.
cheers,
barry
Re: [WiX-users] installing Outlook Primary Interop
Hello WiX community,
I am a beginner in WIX toolset. I am using wix 3.0. I have build the
custom.wixlib that contains custom dialogs and localization file for
this dialogs as EMBEDDED resource, building with COMPILE is impossible.
When I use this (custom.wixlib) library in another wix projects an
I need to produce an msi-style installer for a legacy project and I need to
do it fairly quickly. WiX has been recommended to me and so far, so good but
one thing eludes me at the moment. One of the targets is both a Win32
Service *and* a COM server. Does anyone have any details on how to handle
Dylan Moline (Volt) wrote:
Hey everyone,
I am implementing a custom UI where I would like the user to either accept or
decline a radio button. I want the next button to be disabled until they
select EITHER option. I don't care if it is yes or no, I just want them to
make a decision. Here
Andrew Lee wrote:
Your condition of MUAccepted = yes OR no is always going to
evaluate as true. Try an enable condition and new dialog condition of:
MUAccepted = yes OR MUAccepted = no
or you might find it clearer to put:
(MUAccepted = yes) OR (MUAccepted = no)
The parenthesis is
Hello All,
I am in trouble with building my WiX solution using NAnt and MSBuild task on a
server which is running under Windows 2003 x64.
NAnt task is simple:
exec program=msbuild.exe basedir=${ProspX.netFrameworkPath}
workingdir=${wc.branchPath} resultproperty=setup.WiX.result
Greetings all,
I am sure this is simple but I've been banging my head over this for hours
now.
I placed two PathEdits and two PushButtons to their right.
Each button ( on the right of those labels ) should spawn a BrowseDlg.
When the dialog closes I want to update the two properties I have set
I would install the service using the Service elements and then do the
COM bit by writing the relevant registry entries using RegistryValue.
The hard bit is generating the registry values as I don't think heat can
harvest COM servers, if the code is written in C++ you should be able to
get the
RegistryKey is the parent of RegistryValue. Or you can just list a bunch of
RegistryValue elements out flat. Both ways work.
-Original Message-
From: Barry Larkin [mailto:barrylar...@gmail.com]
Sent: Tuesday, January 20, 2009 03:33
To: wix-users@lists.sourceforge.net
Subject: Re:
Yeah, sounds like a bug. Mike made some changes recently to handle COM+
configuration that was not getting cleaned up correctly. It could be this is a
bug introduced by that change. Please do open a bug on SourceForge.
-Original Message-
From: Yan Sklyarenko
I would install the service using the Service elements and then do the
COM bit by writing the relevant registry entries using RegistryValue.
The hard bit is generating the registry values as I don't think heat can
harvest COM servers, if the code is written in C++ you should be able to
get the
The assemblyFileVersion is only applicable when installing into the GAC.
Otherwise, AFAIK, standard file versioning rules apply. The guidance is to use
publisher policy instead of assemblyFileVersion when installing to the GAC.
Also, as it has been related to me, those 90% of Microsoft
I don't know much about DRM in installers but have you looked at the PIDKEY
property in MSI SDK? That seems somehow related to a lot of this stuff.
-Original Message-
From: Marais van Zyl [mailto:li...@projexis.co.za]
Sent: Monday, January 19, 2009 23:02
To: General discussion for
Write an application that does it.
-Original Message-
From: Andy2k8 [mailto:appr...@gmail.com]
Sent: Monday, January 19, 2009 22:24
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] clickThrough in production software
Ok. In that case what is the best way to add automatic
The installation/uninstallation of users is controlled by the parent Component.
The verbose log file should show you what Components are being
installed/uninstalled.
-Original Message-
From: Joe Osman [mailto:joe.os...@tait.co.nz]
Sent: Monday, January 19, 2009 19:01
To: General
Can you provide the command lines for the things you are building?
-Original Message-
From: Alexandr Naumuk [mailto:anau...@stratagem-us.com]
Sent: Tuesday, January 20, 2009 05:02
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Build wixlib with localization
Hello WiX
I received your email. I have forwarded this to John Jr. He's on a job
site but will respond asap. Thanks John
Tel: 713-780-7262
Fax: 713-780-3010
http://www.jmatech.com
This message and its attachments are for the sole use of the intended
recipients. They may contain confidential,
Done: #2524017
-- Yan
-Original Message-
From: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Sent: Tuesday, January 20, 2009 5:51 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bug in iis:WebApplication?
Yeah, sounds like a bug. Mike made
Hello all, its' been a very long time since I checked in here. I've
joyfully had an issue with our installers of late that should be simple
to solve... only I can't solve it.
The situation is this, our clients install many versions of our software
new and old and run them concurrently. We also
Sorry but I couldn't leave it...
1. I have to disagree, I'm sure you have a better inside track than me
but they do it because they want us to all have the same version, even
Office updates work this way. Policy files just don't cut it especially
if you do daily builds - you would need hundreds
Like which ones?
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Tuesday, January 20, 2009 09:04
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installing a service wich is also a COM server
Yes that is probably what I
Thanks, I'll bring this to Mike's attention when we meet on Thursday.
-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net]
Sent: Tuesday, January 20, 2009 08:15
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bug in iis:WebApplication?
You're welcome to do what you want. All I ask is that you be careful about
suggesting doing things against the recommendations. It's one thing to say,
Don't use that technology, it has all kinds of problems. It's another thing
to say, It's too hard to use that technology so use it in a way
I am getting some very odd behaviour when trying to test upgrading my
product.
Up until now I've just uninstalled the previous version before installing
the new version. But now I'm trying to actually upgrade, and what I'm
getting is a little bit baffling.
Just to test the upgrade, I'm only
MSI SDK about Major Upgrades (and others) has pretty much step by step
instructions when the various GUIDs change. It is very terse reading, so it
takes a few times to get all the pieces but that data is there.
The way I think about it, Upgrade code is a family marker. The Upgrade code
draws
I just noticed this at the bottom of section 4.1 in the tutorial:
For some strange reason, small updates and minor upgrades cannot be run
simply by clicking on the .msi file—they give the error: Another version
of this product is already installed. We know, stupid... Anyway, you have
to start
The command-line is a requirement of the Windows Installer. It hasn't changed,
even in MSI 5.0 currently in beta on Windows 7. Many people feel that makes
minor upgrades completely useless without a chainer. I'm inclined to agree
with them.
We do major upgrades for WiX toolset releases
Hi,
Our installer is packed with a post-install bootstrapper that runs installs
some additional software if it is not already present on the target machine.
(That is, it may or may not run.) The main setup also has a ScheduleReboot
action before InstallFinalize. We are running into a problem
Hi,
I have a Wix project in which I am trying to add a shortcut to a command
prompt which calls a batch file as a command line argument. With the code I
have so far (see below), I can get it to work on Windows XP only, because
the environment variable it's using to find the cmd.exe program is
MUAccepted works just fine for enable and new dialog.
I had been hammering at that on no sleep last night and knew I just needed some
fresh eyes who didn't want to pound their fists on their keyboards in
frustration :)
Thanks a ton
-Original Message-
From: Andrew Lee
Alicia Holloway wrote:
I have a Wix project in which I am trying to add a shortcut to a command
prompt which calls a batch file as a command line argument. With the code I
have so far (see below), I can get it to work on Windows XP only, because
the environment variable it's using to find the
Dmitry Ponomarenko wrote:
I am in trouble with building my WiX solution using NAnt and MSBuild task on
a server which is running under Windows 2003 x64.
NAnt will run as a 64-bit process on an x64 machine; for compatibility,
the WiX tools are marked as x86 and NAnt won't be able to load
Joe Osman wrote:
Nothing much in the verbose log - ConfigureUsers action starts and it
removes the users but it doesn't explain why the users are removed.
Is there a way to skip the ConfigureUsers action during a product upgrade?
You said you were doing a minor update but it sounds more
Windows installer has a bunch of properties that you have access to that
will handle this for you.
http://msdn.microsoft.com/en-us/library/aa372057.aspx
Property Id=COMMANDPROMPT[SystemFolder]cmd.exe/Property
Should work except that you might need a custom action to set it.
-Original
I get an error 'Error 1 Expecting '![CDATA['. '
Here's my code
Dialog Id=InstallDlg Width=370 Height=270
Title=!(loc.SetupTypeDlg_Title) NoMinimize=yes
Control Id=Next Type=PushButton X=236 Y=243
Width=56 Height=17 Default=yes Text=!(loc.WixUINext)
I don't believe I am going against Microsoft recommendations:
http://support.microsoft.com/kb/556041
http://msdn.microsoft.com/en-us/library/z5e12zb4.aspx
http://msdn.microsoft.com/en-us/library/aa372360(VS.85).aspx
I have just spent the last hour reading up on this and
Hi,
How to disable cancel button for when certian feature/components are
installed and enabled for others.
--
Monish C Mohan
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your
I am setting system environment variable on a Windows Server 2003 system using
the WiX Environment element like so:
Environment Id=SetMyAppDir Action=set Name=MYAPPDIR
Value=[INSTALLLOCATION] System=yes /
I can verify in control panel - system after the installer runs that the it
was
I ended up writing a method to obtain values from CustomActionData instances:
private static string getCustomActionDataValue(CustomActionData
customActionData, string key)
{
try
{
return customActionData[key];
}
catch
My understanding of the BCL guidelines was that hashtables/dictionaries should
throw when the item is not present. The .NET Framework 1.0 design (which
returned null, not throw) was deemed inferior. I don't maintain DTF but the
optimized pattern for your scenario was to use the bool
Yeah, the last link you provided was what I was operating based off of memory:
Note The in-place type of update overwrites the copy of the assembly in the
global cache, and can break other applications if the new version of the
assembly is not completely backward compatible. The recommended
This worked. And yes, I had to use a custom action to set the SystemFolder
property.
Thanks!
Alicia
On Tue, Jan 20, 2009 at 2:21 PM, Scott Sam s...@clearviewecm.com wrote:
Windows installer has a bunch of properties that you have access to that
will handle this for you.
Hi Bob,
This did work, although it then found (and used) the first instance of
cmd.exe that it came across.
The solution to use a custom action to define the SystemFolder property and
use that ended up working just fine.
Thanks,
Alicia
On Tue, Jan 20, 2009 at 1:59 PM, Bob Arnson
In the case that is working, you are specifying the default culture to
light.exe. In the case that is not working you are not. That's probably the
problem.
-Original Message-
From: Jeremy Lew [mailto:j...@liquidmachines.com]
Sent: Tuesday, January 20, 2009 13:39
To: General discussion
So I have a dll built with two separate functions within. I would like to call
the DLL once before the UI and have it return a value, have a different section
of the UI called based on the value returned from the DLL, and then once the UI
is called, if the user chooses an option, to call the
Sorry it's taken me so long to get back to you. Yes, I've tried a
removeOnUninstall attribute. Here's what my current element looks like:
RemoveRegistryKey Root='HKCU' Key='Software\MyApp\MyProduct'
Action='removeOnUninstall' /
But after an upgrade my registry settings have been wiped clean.
Yeah, that's going to uninstall the previous version before installing the next
version. The settings get deleted on the first uninstall so you are left with
clean settings next.
IMHO, the best way to address the problem is to not delete user data.
-Original Message-
From: Colin
Check your UpgradeCode and Upgrade ID= and make sure they are correct. The
Upgrade ID= should be the UpgradeCode of the product you wish to upgrade. Often
times the UpgradeCode in the new package is also set to the same value. It
basically describes a family of products.
-Original
Yeah I think that's what I'll end up doing. Would it make sense for a
future version of WiX to allow the RemoveRegistryKey to have a condition
inner text like other elements do?
On Tue, Jan 20, 2009 at 4:58 PM, Rob Mensching
rob.mensch...@microsoft.comwrote:
Yeah, that's going to uninstall the
That was the problem. Thanks.!
On Tue, Jan 20, 2009 at 5:14 PM, Ian Elliott (Excell Data Corporation)
a-iae...@microsoft.com wrote:
Check your UpgradeCode and Upgrade ID= and make sure they are correct. The
Upgrade ID= should be the UpgradeCode of the product you wish to upgrade.
Often times
Gotcha.
Rob Mensching-2 wrote:
My understanding of the BCL guidelines was that hashtables/dictionaries
should throw when the item is not present. The .NET Framework 1.0 design
(which returned null, not throw) was deemed inferior. I don't maintain
DTF but the optimized pattern for your
Thanks but it didn't help. I've analysed the verbose log and found that
ConfigureUsers action is called twice: the first time is at the
beginning, after Removefolders - in this case this action is executed
even after using the condition NOT UPGRADINGPRODUCTCODE. and this is the
cause for the
Hi,
I am receiving an error while trying to select the option Select an
application type below in the dropdown of WiX ClickThrough UI. I have attached
the exception detail and an image of it along with this email. I am trying to
use this on Windows Vista 32-bit OS.
Thanks,
Kiran Challa
See
Thank you, sir. That's what I needed to know.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Monday, January 19, 2009 6:34 PM
To: General discussion for Windows Installer XML toolset.
Subject: [LIKELY_SPAM]Re: [WiX-users] 64-bit vs. 32-bit Vista Registry
writing
Kiran Challa wrote:
I am receiving an error while trying to select the option Select an
application type below in the dropdown of WiX ClickThrough UI. I have
attached the exception detail and an image of it along with this email. I am
trying to use this on Windows Vista 32-bit OS.
Dylan Moline (Volt) wrote:
So I have a dll built with two separate functions within. I would like to
call the DLL once before the UI and have it return a value, have a different
section of the UI called based on the value returned from the DLL, and then
once the UI is called, if the user
Joe Osman wrote:
I've edited the MSI
file using Orca and removed all the records containing ConfigureUsers
and RemoveUsers actions but to no avail.
If you removed the actions and they still ran, you're not running the
package you edited. If you just edited in Orca without changing the
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
where i can get source code of light.exe and candle.exe
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
Like which ones?
Implemented Categories:
HKCR\CLSID\{guid1}\Implemented Categories\{guid2}
Any entries for assemblies:
CLSID\{guid}\InprocServer32\1.2.3.4
These are generated from Heat I have to admit I don't know what they
are!
HKCR\Component Categories\{guid1}
1. there is already support for the two most common Implemented Categories.
Do you know others that need support?
2. What is InprocServer32\1.2.3.4?
3. Does anybody actually use that other stuff?
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Tuesday,
Hi
I can't see anything wrong on that row but on the next row and some other
places you have written CData instead of CDATA...
Perhaps you can skip CDATA and write just INSTALLTYPE=ServerFeature instead
of ![CData[NOT (INSTALLTYPE=ServerFeature)]]. I use CDATA as I sometimes
use not equal to
Thanks for the extra information. And you're right, this isn't worth the
extra headache. :)
On Tue, Jan 20, 2009 at 10:03 PM, Rob Mensching rob.mensch...@microsoft.com
wrote:
No, Windows Installer controls that. Remember Component states control the
install and uninstall of resources.
Sudhakaran, Suraj wrote:
I am using WiX2.0.
I have a requirement of patching selected components in a new version.
AFAIK, patching process will include all the modified files from the old
and new installer and include them in the patch.
Is there a way to select what all will be included here
67 matches
Mail list logo
