Yes, you should specify -cg switch, providing the name of the
ComponentGroup to be generated:
Heat dir dir_path -cg HelpGroup ...
-- Yan
-Original Message-
From: akapoor [mailto:anupama_kap...@yahoo.com]
Sent: Monday, July 20, 2009 8:10 PM
To: wix-users@lists.sourceforge.net
Subject:
You're probably talking about the document which describes the
installation process, also known as the installation guide. It usually
contains the description of the installation procedure, step by step.
Start from the Welcome screen and proceed explaining what each screen is
for. The best
You may check the Windows Installer SDK. You can author your own validation
DLL's, called .cub files. You typically would write these in C++. The
validations is them called from the command line (msival.exe ?, I forget).
This would be how you could add custom validation to your build.
The
Did you delay-sign it (and not complete the signing)?
The wix sources use strong-name signing (since that is needed for
assembly-name references to the extensions, but not path-references). Turn
off all references to strong-name signing your extension.
-Original Message-
From: Will Page
Dear all,
Maybe someone has already found out this bug and workaround.
If you want to create a new Project based on the Windows Installer XML - C#
Custom Action Project template (v3.5.0710.0) in Visual Studio you may receive
some path errors.
This is because of some old path references to WiX
Right.
I responded to your previous email...
/rafael
-Original Message-
From: Vuchuru, Surekha (SBT US EXT) [mailto:surekha.vuchuru@siemens.com]
Sent: Monday, July 20, 2009 1:57 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Wix warning LGHT1076 :
Thanks, Sascha, for your answer.
My installers will be used by the user, not by me, and I won't my user to
use Orca, that is not very friendly for regular user.
I have problems to create sufficient agent installer by Wix (I'm not strong
in that field) and currently I suppose to use MSI
Rob,
In your reply: If you generate GUIDs every time you build, you won't be
able to do any upgrades or patching.
We are using WiX 2.0 (planning to upgrade to 3.0). No problem to create
patches given ProductCode and UpgradeCode GUIDs are the same, but with
different components' GUIDs. My
Is your MSI built as x86 or x64?
Our product has multiple OCX's COM DLL's which I've harvested using
heat.exe and everything registers fine on both 32-bit 64-bit O/S.
However all our MSI's are built for x86 as our apps are 32-bit so I've
never run across this issue myself.
If you're building an
I am looking for some guidance on IIS configuration. I want to create a
Certificate Trust List and then enable it for the website that I am
installing, is this possible in Wix?
-
HBOS plc,
Hi Yan Sklyarenko,
Thanks a bunch for your suggestion. I got it all working now.
-Anu
Yan Sklyarenko wrote:
If you used heat.exe to generate your help.wxs, then it most likely
contains a ComponentGroup, which includes all the generated components.
The components should be included into
From the Wix documentation:
For the Component element the generated GUID is based on the install
directory and filename of the KeyPath for the component. This GUID will stay
consistent from build-to-build provided the directory and filename of the
KeyPath do not change.
2009/7/21 shibo
Hello,
I need to create a setup for the new major version (v2) of our product. It
should be able to be installed alongside the old version (v1). Each version
is installed in a separate directory. Some assemblies get installed into the
GAC and the assembly version of v1 and v2 differ, but the
What should I do in order to make my installer overwrite all the files while
running in maintenance mode?
Thanks,
Eran.
--
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes!
Specify option 'a' in the REINTALLMODE property:
http://msdn.microsoft.com/en-us/library/aa371182(VS.85).aspx
-- Yan
-Original Message-
From: ערן גבע [mailto:mail.g...@gmail.com]
Sent: Tuesday, July 21, 2009 4:22 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How To
Hi,
I'm trying to install a per-machine application and the best location
for the sample documents seems to be the Public Documents folder (or All
Users' Documents on Windows XP), but I'm not able to find out, how to
reference Public Documents folder in WiX/MSI. According to:
I dont know if this would help but Ive found it best to install sample
files along with the application and have the application make copies of
them into a folder of the user's choice, or to their my documents
folder, when the application runs for the first time, or when they
select some kind of
Hello,
I am trying to make a simple windows installer constisting of these
features:
feature1
feature2
examples.
The feature examples consists of features:
examples_feature1 (will be hidden)
examples_feature2 (will be hidden)
I want to install feature examples_feature1 ONLY if user selected
Short answer: yes change all your Component GUIDs.
I've got the exact same situation as yourself having read all the
information available on Component rules I've changed all ours.
If you want to know what happens if you don't change the GUID's read up
on Component Rules what happens when you
this does not solve my problem.
any suggestions?
2009/7/21 Yan Sklyarenko y...@sitecore.net
Specify option 'a' in the REINTALLMODE property:
http://msdn.microsoft.com/en-us/library/aa371182(VS.85).aspxhttp://msdn.microsoft.com/en-us/library/aa371182%28VS.85%29.aspx
-- Yan
-Original
Could you make examples_feature1 visible and a child feature of
feature1 and examples_feature2 visible and a child of feature2 ?
Remove the feature examples.
The user could select the examples that they wanted to install but they
couldnt install the examples without the corresponding parent
Just a thought but why are you distributing Microsoft.Data.Schema.Sql.dll that
sounds like a Microsoft component to me and should be distributed using their
package (presumably SQL).
Neil
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: 21
Pally Sandher wrote:
If you want to know what happens if you don't change the GUID's read up
MSI supports having multiple products install the same component to
different directories. But it does require even more strict adherence to
all the component rules, so changing GUIDs (or letting
Tamara Kustarova wrote:
The feature examples consists of features:
examples_feature1 (will be hidden)
examples_feature2 (will be hidden)
I want to install feature examples_feature1 ONLY if user selected
feature1 to install and feature examples to install. Similarly, I want
to install
Kevin Jin wrote:
Is it possible to have a multi-tab control in a Dialog?
No, MSI doesn't support that.
--
sig://boB
http://joyofsetup.com/
--
Enter the BlackBerry Developer Challenge
This is your chance to win
Something I've never had to use before but looking at my own machine
(XP64) there's a directory at C:\Documents and Settings\All
Users\Documents\ on my Vista64 VM (potentially Windows 7 too but I
don't have a machine here to check it) there exists a directory at
C:\Users\Public\Documents\ which
Maybe it is not the best way, but you can add the following events on Change
button (or Repair button):
Publish Event=ReinstallMode Value=a Order=11/Publish
Publish Event=Reinstall Value=SomeFeature Order=21/Publish
About Reinstall:
http://msdn.microsoft.com/en-us/library/aa371184(VS.85).aspx
Ondrej Zarevucky wrote:
I coudn't find any other property which will resolve to Public Documents
folder. Can someone hint me, how to install these public/shared samples
there?
WiX provides the WIX_DIR_COMMON_DOCUMENTS property. See OSInfo custom
actions in WiX.chm.
--
sig://boB
thanks for your help!
how do I make the event to run only on maintenance mode ?
בתאריך 21 יולי 2009 16:34, מאת Natalia Gladkova
natalia.gladk...@arcadia.spb.ru:
Maybe it is not the best way, but you can add the following events on
Change
button (or Repair button):
Publish
I want the extension so that existing installer builds using the default
WiX UI installation can transparently swap it out for my UI, in addition
to the (very minor) benefits that you get when decompiling.
On top of that, I plan on writing a real extension to add language
features specific to
Konstantin,
Thanks for your comment.
My tests show that directory / component Ids stay the same from
build-to-build, but not their GUIDs.
Does this mean that only directory / component Ids are used in patching in
WiX 3.0, not GUIDs?
Thanks, Shibo
fromKonstantin Vlasenko
subject Re:
Actually, it's redistributable:
http://blogs.msdn.com/gertd/archive/2008/08/22/redist.aspx
%ProgramFiles%\Microsoft Visual Studio 9.0\VSTSDB\redist-enu.txt
Subject to the license terms for the software, you may redistribute the files
(unmodified) listed below.
It's a x64 MSI. I used the Win64=no setting and sure enough I got ICE80 errors
:-(, but the registration seems to have worked. Any ideas on how to get rid of
the ICE errors - This 32BitComponent X uses 64BitDirectory X
-Arvind
-Original Message-
From: Pally Sandher
Cheers all, that sorted it.
Date: Mon, 20 Jul 2009 12:13:07 +0100
From: dwat...@sdl.com
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] merge modules not working only vcredist.exe
Lol, why didn't I spot that. It is Monday morning I suppose.
-Original Message-
Will Page wrote:
So without understanding what's wrong with this extension, I have little
hope of making a more complex extension work as desired.
You haven't described what's wrong. What error message do you get?
--
sig://boB
http://joyofsetup.com/
shibo wrote:
My tests show that directory / component Ids stay the same from
build-to-build, but not their GUIDs.
Do you change directories?
Does this mean that only directory / component Ids are used in patching in
WiX 3.0, not GUIDs?
No, they all need to be consistent for patching
Arvind Aiyar wrote:
It's a x64 MSI. I used the Win64=no setting and sure enough I got ICE80
errors :-(, but the registration seems to have worked. Any ideas on how to
get rid of the ICE errors - This 32BitComponent X uses 64BitDirectory
X
32-bit components should go to 32-bit
Hi
The CustomAction will set (a list of values) to a ComboBox named TARGETWEBCOMBO
in a Dialog. Then I want to use the (single) value the installer has picked in
that ComboBox as the install directory.
Using the code below, I got this C:\Inetpub\wwwroot\[TARGETWEBCOMBO]\ in the
next dialog.
Edwin
I don't have those on my machine but I would guess that it does some
anti-social stuff when you self register it. Is there any documentation on how
you are supposed to distribute it. You could try running heat and ignoring the
self-reg stuff.
Neil
-Original Message-
From:
The Name attribute of the Directory element is not of Formatted type
(http://msdn.microsoft.com/en-us/library/aa368609(VS.85).aspx
http://msdn.microsoft.com/en-us/library/aa368609(VS.85).aspx ). I think you
should use the type 35 (set a directory) custom action to accomplish what you
want:
Right now I am using -sreg -scom -svb6 on that particular invocation of heat.
There are other files included in that execution so I'm hoping that nothing
really needs any of that registration stuff.
But, if I am understanding you correctly, that dll really is modifying those
registry
So I took your advice and tried to separate my 32-bit and 64-bit components.
Now the 32-bit components install into [ProgramFilesFolder] and the platform
independent ones into [ProgramFiles64Folder]. However, now when I compile my
32-bit MSI, it cribs that I'm using duplicate folder IDs (true,
I'm trying to use XmlConfig to update a file that looks like this:
?xml version=1.0 encoding=utf-8?
SqlCommandVariables
xmlns=urn:Microsoft.VisualStudio.Data.Schema.Project.SqlCmdVars
Version1/Version
Properties
Property
PropertyNamename1/PropertyName
Edwin,
I believe you're missing the Action and Node attributes of the XmlConfig tag.
util:XmlConfig Id=id
File=file
ElementPath=//SqlCommandVariables/Properties/Property[\[]PropertyName='name1'[\]]/PropertyValue
Action=create
I'm having a problem with an ini file search. I'm trying to disallow
installation based on the presence of a value in an ini file.
However, OLDVALUE (the item for which I'm searching) is never set. I've
confirmed the presence of the item in the ini file. The path is correct.
Examining the log, I
Thank you so very much! Your suggestion worked flawlessly!
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
-Original Message-
From: Matthew
Heat (in a default state) runs the DLLs passed to it in a
self-reg-in-a-sandbox environment, so yes, that dll is modifying those registry
values.
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Tuesday, July 21, 2009 2:38 PM
To: General
Is the Tutorial ever going to be updated?
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Wednesday, March 25, 2009 1:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Samples errors follow up
Louis elston wrote:
The samples
Hi Eric,
Are you sure that msi.ini file is in the default windows folder?
Alex
-Original Message-
From: Eric Napier [mailto:napi...@gmail.com]
Sent: Tuesday, July 21, 2009 3:34 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] inifilesearch doesn't execute
I'm having a
Thank you for confirming that!
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
-Original Message-
From: Blair [mailto:os...@live.com]
When I tried to add a VSTO dll to wix, I got the following error:
Error 1 Either
'Microsoft.Tools.WindowsInstallerXml.AssemblyDefaultWixExtensionAttribute' was
not defined in the assembly or the type defined in extension
Shawn Zhou wrote:
When I tried to add a VSTO dll to wix, I got the following error:
Error 1 Either
'Microsoft.Tools.WindowsInstallerXml.AssemblyDefaultWixExtensionAttribute'
was not defined in the assembly or the type defined in extension
Arvind Aiyar wrote:
So I took your advice and tried to separate my 32-bit and 64-bit components.
Now the 32-bit components install into [ProgramFilesFolder] and the platform
independent ones into [ProgramFiles64Folder]. However, now when I compile my
32-bit MSI, it cribs that I'm using
No, it's not in the windows folder. It's in program files\my company\myapp
Does it have to be in Windows for inifilesearch to work? I thought the
directorysearch element told it where to look?
-Original Message-
From: Alex Shevchuk shevc...@live.com
To: 'General discussion for Windows
Read about IniLocator table
(http://msdn.microsoft.com/en-us/library/aa369283(VS.85).aspx):
... The .ini file must be present in the default Microsoft Windows
directory.
Also, it's the other way around. Parent element starts search and child
element continues it with what parent found. So,
Hi,
I am able get available websites on IIS using the Jon sample available @
http://blog.torresdal.net/2008/10/24/WiXAndDTFUsingACustomActionToListAvailableWebSitesOnIIS.aspx
It is displaying websites in ListBox, But I need in ComboBox.
Please suggest me what are the changes should I do
I newbie using wix3.0.5419.0, and I am having a problem finding the Wix
UI library. I have read WixUIExtension.dll is in the directory where I
installed Wix, and all I need to do is run light.exe, and the library
will be found. Some say A full path to light.exe might be required.
In my wxs, in
Try to add *-ext WixUlExtension* to the command lines.
2009/7/22 jo...@msli.com jo...@msli.com
I newbie using wix3.0.5419.0, and I am having a problem finding the Wix
UI library. I have read WixUIExtension.dll is in the directory where I
installed Wix, and all I need to do is run light.exe,
58 matches
Mail list logo
