I think you should look at the GenerateBootstrapper MSBuild task.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Thielen
Sent: Tuesday, December 05, 2006 10:19 PM
To: wix-users@lists.sourceforge.net
Subject:
That seems like it would be a good stop-gap solution for now. I'm
wondering how the WiX Extensions work since at the heart of those is C++
code. Seems like I'll have to do some more digging...
Thanks for the reply!
-Original Message-
From: Eric Fesh [mailto:[EMAIL PROTECTED]
Sent:
I have run into an interesting problem using candle.exe. I have
apparently run into a command line length problem when trying to compile
my install project. Is there a command line length limit to candle? And
if so... is there also one for light?
Don
Hi;
I posted this also in the MS forums (no answer) and the MSDN managed
newsgroups (useless answer). I am hoping someone here can help.
First off, I have read the following:
http://msdn.microsoft.com/msdnmag/issues/04/10/Bootstrapper/
No, but there is a command-line limit in Windows. Use a response file to get
around it
candle @commands.rsp
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Don Tasanasanta
Sent: Wednesday, December 06, 2006 10:04
To: wix-users@lists.sourceforge.net
Subject:
On 12/5/06, Rob Mensching [EMAIL PROTECTED] wrote:
I've found that there are very few degrees of freedom in ClickOnce. What
is even more frustrating is that the Windows Installer supports all of the
basic needs and everyone would have benefited if an auto-update story was
built for the Windows
Thanks, that'll help tremendously.
What is the syntax inside an .rsp file?
Don Tasanasanta
425-605-7423
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 06, 2006 10:10 AM
To: Don Tasanasanta;
Same as all compiler response files, each command is white space delimited.
From: Don Tasanasanta [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 06, 2006 10:55
To: Rob Mensching; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] length of candle command line
Thanks, that'll help
Some answers to your questions (sorry, not all):
#1. The official documentation for GenerateBootstrapper (the MSBuild
task) is http://msdn2.microsoft.com/en-us/library/ms164294.aspx. I
don't know where the official documentation for the bootstrapper itself
it. You don't need to make a
Just to add that if one wanted to see a consolidated list of how the
bootstrapper manifest checks and installs products (and this includes
SQL and J# 2.0), build a Visual Studio 2005 SetupDeployment project
bootstrapper with all the prerequisites checked. This builds an exe with
the manifest in
Hi;
I think I'm not understanding something. I want the bootstrapper to give
me a small setup.exe that will download things like the .NET framework
only if needed on that user's computer. And I need the download to be a
single file to make it easy. How can I build this? The examples I see
all
You mean you want the download for Windows Installer, SQL Express, .NET
Framework, J# etc to be all in one file? Just trying to understand.
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Thielen
Sent: Wednesday,
Hi;
I looked for that the other day. In Setup and Deployment all I have is
Setup Project, Merge Module Project, CAB Project, Web Setup
Project, Setup Wizard, and Smart Device CAB Project.
Is it one of those or do I need to download something?
Thanks - dave
David Thielen
No, the oppisate. I want setup.exe to be very small and it then will
download the needed installers and run them only if needed. And it will
download them from the MS website.
So the user runs setup.exe and then when running, if they don't have
.NET framework installed, it downloads it from
I'm sorry that I'm confusing you and that we aren't communicating well.
I thought I answered that twice now. I'll try again.
In your MSBuild file, you have to specify where the bootstrapper should
get the pre-reqs. You want them to be downloaded. So you set the
ComponentLocation attribute of
The generated setup.exe file behaves as you desire and only downloads
files that it needs to install. Only those files that are necessary to
determine if a package needs to be installed (such as dotnetchk.exe) At
least this is my experience.
From: [EMAIL
InstallUtil is not recommended. Managed code in installers is not
recommended. InstallUtil.dll is not documented. The Visual Studio team might
be able to help, but no-one else.
Your best bet is probably to use FileMon
(http://www.microsoft.com/technet/sysinternals/FileAndDisk/Filemon.mspx) to
It is recommended that custom action DLLs have the fewest dependencies
possible, to avoid problems where the dependencies are not already present
on the target machine.
You should try to eliminate use of the CRT, if possible, and statically link
with it to remove the dependency on the CRT
It's a Setup and Deployment project.
Phil Wilson
(949)639-1680
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Thielen
Sent: Wednesday, December 06, 2006 1:26 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users]
Is there a tool out there to compare two MSIs? I'm moving our MSIs to wixv3,
and I want to verify that the built MSIs are the same as previously.
Cullen Waters
SDET
Office Live
+1 425 706 6809
x 66809
-
Take Surveys. Earn
Orca is a fair good tool and will allow you to eyeball compare the
tables, not sure it has any automatic comparison feature.
Joel Peterson
Quality Assurance Engineer
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cullen
Waters
A lot of our installers are pretty complex, and use a bunch of tables. I was
hoping for something more automated.
From: Peterson, Joel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 06, 2006 3:36 PM
To: Cullen Waters; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Comparing two
David,
For #1: The UI is _not_ configurable (with the exception of the title of the
dialog boxes).
The best way to structure this is to create a Self Extracting EXE that holds
the Setup.exe and your MSI. Configure the Self Extracting EXE to run
Setup.EXE when it is unpacked. ChilkatSoft.com
There's a script in the MSI SDK called WiDiffDb.vbs, I use it on
occasion to do this.
Michael
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peterson,
Joel
Sent: Thursday, 7 December 2006 9:36 AM
To: Cullen Waters; wix-users@lists.sourceforge.net
Subject: Re:
Does this strike anyone else as Rube Goldberg-like? A setup program that
extracts a setup and msi and calls that setup which at the end calls the
msi.
I'm looking forward to WIX adding this functionality.
Again, thank you for all the help. What/how to do this is not easy or
intuitive so
Mike Dimmick wrote:
You should try to eliminate use of the CRT, if possible, and
statically link with it to remove the dependency on the CRT DLLs.
There's nothing wrong with using the CRT as long as you statically link.
The WiX custom actions should probably take the lead here and replace
Pallavi Patrutkar wrote:
Some days before I was facing problem while upgradation from previous
version to newer version. I added a new component that was adding a new
registry value while installation. While upgradation, it was not
installing some of the components properly while at the time
I've recently upgraded some Votive projects from version 2 to version 3.
In version 2, the following preprocessor variables existed:
var.Project.ConfigurationName
var.Project.ProjectDir
var.Project.ProjectDosFileName
var.Project.TargetDir
var.SolutionDir
(etc)
In Votive 3, they don't seem to
28 matches
Mail list logo
