Hi,
I had a similar situation, instead of products from multiple
manufacturer, we had to extract out sub set of their installer. What I
did was extract the required files and put them into the main WXS file
and grouped the install as features. We also had a dependency on VC
runtime, so that I inclu
Thanks but I've already had a look at that article before starting this
thread. It doesn't explain how to achieve what I'm after. Once again, I find
myself in situations that (to my surprise) no one else seems to have
encountered before.
I need to get rid of WelcomeDlg completelynot tweak it,
I am out of the office until 08/09/2010.
Please email Cognos RD Build Engineering Support or for urgent matters
contact my team lead Robert Lyonnais or my manager Ben Fowler.
Note: This is an automated response to your message "Re: [WiX-users]
Bootstrapping and Burn" sent on 9/3/10 16:07:03].
You might want to take a look at the extensions in http://msiext.codeplex.com.
There's UI for database selection, credentials, etc. There's no support for
Oracle explicitly, but it works with generic ODBC CAs and extensions.
dB. @ dblock.org
Moscow|Geneva|Seattle|New York
-Original Messa
By the nature of the situation of the company at that time I happened to be
both the manager and the architect. So I didn't complain to myself. I certainly
drank the cool-aid during my MSFT years on Wix ... it was an obvious choice for
me.
Unless you're in the installer business you're not writ
Hello, has anyone had any experience installing a procrun.exe commons
daemon java service with WiX. All configuration is stored in the registry
32bit
HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun
2.0\FooService\Parameters
on 64bit in
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apa
> From: Bruce Cran [mailto:br...@cran.org.uk]
> Sent: Friday, September 03, 2010 6:55 PM
>
> On Fri, 3 Sep 2010 10:31:34 -0700 (PDT)
> Christopher Painter wrote:
>
> > Well said other then I don't agree that InstallShield is the reason
> > people don't want to write installs. ( Although this s
If I recall, InstallShield X used the legacy setup.exe which only let you pick
from a list of MSI and .NET redists. It was very limited. I believe it was
10.5 that introduced the setup prereqs capability which obsoleted the old
ability and greatly extended the system. InstallShield 2008 or
On Fri, 3 Sep 2010 10:31:34 -0700 (PDT)
Christopher Painter wrote:
> Well said other then I don't agree that InstallShield is the reason
> people don't want to write installs. ( Although this seems to be
> supported by tweats and blogs that I read. ) I just can't buy
> it based on my experience
You know what would really be cool? An MSI/WiX summit. I could get a trip to
Redmond funded for sure if there was some event I could put on the expense
report.
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
Well said other then I don't agree that InstallShield is the reason people
don't
want to write installs. ( Although this seems to be supported by tweats and
blogs that I read. ) I just can't buy it based on my experience using the tool
for the last 14 years. Maybe I'm just hard headed enough
dB is right; it is a management problem.
I'm the lead developer for the product I'm involved in (BTW - for both
the software AND the installation). We used Wise for many, many years
until it got so creaky that I had to replace it - and WiX was the
obvious choice.
The problem I had is that manag
dB-
I've mostly gone down your road over the last year and I know have about 50
out
of 250 developers capable ( and they do when needed ) of contributing to
setup. We continue to have 4 setup experts ( really only 2 FTEs because we
split our time on builds where needed ) to guide the entir
It's a management problem.
My developers hated writing installer code and learning anything about it as
long as we had a setup developer. They had no idea how complex it can get and
why they should care. They wanted to write Java code, it seemed better.
Incidentally we had about a 65% failure
Hey all,
i intend to build a msi installer which containing product's of different
manufacturers...This is because my product needs these others products.
These oder products should be appear als feaures (the user should have to
possibilty to install it or not) into my final installer
Now lets ha
Thanks a lot for helping me to solve my problem
MfG
Abdoulaye Souleymanou
@ Rohde&Schwarz München GmbH & Co.KG
abdoulaye.souleyma...@rohde-schwarz.com
Abt. 2GE5, Bau 1/1
089 / 4129 - 13858
Stangl Software Integration
Heat is largely intended to make it easier to create a first draft of
your installer. You're then supposed to edit the results by hand to
create the final product, so that's what I'd recommend.
If you must do repeated, automatic harvesting then you can either rename
your source files or transform y
Try to manually modify one of the component codes after harvesting.
It's not Windows Installer best practice to include the same file
(component) several times in the installation.
Also comp.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Install-the-same-file-into-multiple-directo
See
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Help-me-fo
r-using-Heat-to-generate-script-wxs-file-from-CAB-files-directly-Thanks-
in-advance-td5477665.html#a5477665
-Original Message-
From: Xu, Jun [mailto:jun...@ebay.com]
Sent: 03 September 2010 08:49
To: General di
Hello all,
i have the following problem:
I try to harvest the two directories below using heat:
C:\MyfolderA
C:\MyfolderB
MyFolderA contains: file1.txt, file2.txt
MyFolderB contains file1.txt, file3.txt
file1.txt in MyFolderA and file1.txt in MyFolderB are identical.
Later the collected files
Hello.
I have created a minimal installer with "WixAppFolder" set to
"WixPerUserFolder". Application installs in
HOME\AppData\Local\Apps\APPNAME as expected, but installer shows same UAC
prompt for both per-user and per-machine install (under normal user this
prompt has 'enter administrator passwo
To clean up a custom action during rollback, write a rollback custom
action and schedule it at the same time as you schedule the custom
action.
http://msdn.microsoft.com/en-us/library/aa371369%28VS.85%29.aspx
To remove your files at uninstall, just add DeleteFile elements.
There are other ways yo
Think the problem also comes from the tools for creating installers:
The MSI based IS, Wise and VisualStudio Installer just try to say to
the people " Oh setup creating is very easy. Just some clicks here and
you're done". What happens below on MSI nobody tells. For the core
concept of MSI and a d
Take a look here
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html I think
that should help you.
Neil
Neil Sleightholm
n...@x2systems.com
On 3 Sep 2010, at 08:32, "Ashvin" wrote:
>
> Hi there,
>
> I have a wrapper program that wraps my wix installer. It has it's own
Hi,
Currently, I know I can use Heat to generate a .wxs file based on a folder with
a lot of files in it.
For e.g.
I use following command line to generate My_Activex_P001.wxs which has all
information for each file in c:\files\.
heat dir c:\files\ -gg -o My_Activex_P001.wxs -template product
This reuqirement is not possible by default based upon the MSI
concept. An Installer can be either an x86 or x64 one. X86 ones
running on x64 always target the WOW-directories on x64 operating
systems (like e.g. C:\Windows\SysWOW64). So I'd recommend to build a
native x86 and a native x64 installer
Hi there,
I have a wrapper program that wraps my wix installer. It has it's own
welcome-like dialog so I don't need two. How can I remove WelcomeDlg?
I currently have the following property in UI:
where EULAAgreementDlg is one of my custom dialogs. I'd like to skip
straight to this dialog wit
27 matches
Mail list logo
