Re: [WiX-users] Is click once what we should be using?

2006-12-06 Thread John Vottero
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: [WiX-users] Is click once what we should be using?


Hi;
 
We have a WIX built installer that works great. And we are
working on creating a bootstrapper for the prerequisites that would call
our msi at the end to complete the install.
 
Should we be looking at click once?
 
thanks - dave

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] **Spam** 200 -Dual **Re: VS2005 C++ and Custom Actions

2006-12-06 Thread Matthew Kowalski
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: Tuesday, December 05, 2006 1:47 PM
To: Matthew Kowalski
Cc: wix-users@lists.sourceforge.net
Subject: **Spam** 200 -Dual **Re: [WiX-users] VS2005 C++ and Custom
Actions

I was in a similar situation and just statically linked the runtime
library. Of course, I was running an executable instead of 
trying to access a DLL, so that might not be helpful information.

--

Eric Fesh
Customer Support Engineer/Software Test Engineer
Verari Systems Software, Inc.
110 12th Street North, Suite D103
Birmingham, AL 35203
Phone +1-205-397-3141 ext. 3149
Fax +1-205-397-3142
[EMAIL PROTECTED]
http://www.verarisoft.com/

The information contained in this communication may be confidential and
is
intended only for the use of the recipient(s) named above.  If the
reader of
this communication is not the intended recipient(s), you are hereby
notified
that any dissemination, distribution, or copying of this communication,
or
any of its contents, is strictly prohibited.  If you are not a named
recipient or received this communication by mistake, please notify the
sender
and delete the communication and all copies of it.


Matthew Kowalski wrote:
 I've created a simple C++ .dll in VS2005 to do some checks for me
during 
 the install after a user has selected an installation folder. The 
 problem I am having is with the VS2005 C++ runtime (msvcp80.dll). The 
 compiled .dll apparently needs to have the runtime installed otherwise

 the installation fails when attempting to execute the custom action 
 (Dependent Assembly Microsoft.VC80.CRT could not be found). Is there

 any way to get around having to install the redistributable package 
 (vcredist_x86.exe) before running my install?
 
  
 
 Any help would be greatly appreciated!
 
 


 


-
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to
share your
 opinions on IT  business topics through brief surveys - and earn cash

http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDE
V
 
 


 
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] length of candle command line

2006-12-06 Thread Don Tasanasanta
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 Tasanasanta

VIACK Corporation

Redmond Washington

425-605-7423

 

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] GenerateBootstrapper questions

2006-12-06 Thread David Thielen
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/
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/
html/custom_pkg.asp 
http://msdn2.microsoft.com/en-us/library/ms164294.aspx
http://www.gotdotnet.com/workspaces/workspace.aspx?id=ddb4f08c-7d7c-4f44
-a009-ea19fc812545

Sorry for all the questions - there is a lot of content about using the
bootstrapper to do X but none I could find about all the properties for
anything other than the samples shown. And unfortunately none showed
requiring J# (a prerequisite for us).

After reading the above (and some other pages) I have the following
questions about using this:
1) Where is complete documentation for GenerateBootstrapper - including
what to put in the package.xml to download from Microsoft (not included
in the package and not download from us but downloaded from MS if
needed):
a) .NET 2.0 framework
b) .NET 2.0 language pack if appropiate
c) J# 2.0 framework
d) J# 2.0 language pack if appropiate
e) whatever windows setup a wix built msi needs

2) Is there anywhere to get the Bootstrapper Manifest Generator and is
it worth using? The download link at
http://www.gotdotnet.com/workspaces/workspace.aspx?id=ddb4f08c-7d7c-4f44
-a009-ea19fc812545 does not work.

3) How do I set it to run our msi installer when it is done with the
prerequisites? And is it embedded in the created setup.exe or downloaded
at that time? If an option, which is recomended.

4) How do I put out name and text in the dialogs for setup.exe?

5) Is this a single file? Or is this a set of files that we need to
write an installer for?

6) Is there a way to make Sql Server Express an option and not show it
as an option if Sql Server regular or express (not only express) is
already installed?

7) Are there any samples of how we should set up our part of package.xml
and the rest of our settings - both in our msbuild.proj file and in the
xml files that list what goes in to the bootstrapper.

8) Can this be set so that it will look first on disk for the needed
install files and then on MS' website so if we put this all on disk we
can use the same bootstrapper?

8b) And if so, where do we get those files and what is the directory
structure?

I hope with answers to the above I will have at most 1 - 2 followup
questions.

thanks - dave

 

 

David Thielen

www.windwardreports.com

303-499-2544 x1185

 

Cubicle Wars - http://www.windwardreports.com/film.htm

 

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] length of candle command line

2006-12-06 Thread Rob Mensching
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: [WiX-users] length of candle command line

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 Tasanasanta
VIACK Corporation
Redmond Washington
425-605-7423

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Is click once what we should be using?

2006-12-06 Thread Scott Palmer

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 Installer.  That's why ClickOnce frustrates me so.




Seems like they were just trying to make something to compete with Java Web
Start, and not a full Windows installer solution.

Scott
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] length of candle command line

2006-12-06 Thread Don Tasanasanta
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; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] length of candle command line

 

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: [WiX-users] length of candle command line

 

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 Tasanasanta

VIACK Corporation

Redmond Washington

425-605-7423

 

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] length of candle command line

2006-12-06 Thread Rob Mensching
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 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; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] length of candle command line

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: [WiX-users] length of candle command line

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 Tasanasanta
VIACK Corporation
Redmond Washington
425-605-7423

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] GenerateBootstrapper questions

2006-12-06 Thread Erv Walter
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 package.xml file at all unless you are
creating a redistributable package.  If you need to do that, you put the
HomeSite in the product.xml file.
 
#2.  Never tried it.  Don't know if it is useful.
 
#3.  In your msbuild project you set the ApplicationFile attribute to
the filename of your .msi on the GenerateBootstrapper task (see my
sample in a previous email).  It's not embedded.  It sits side by side
with the setup.exe.  I believe you can have it be downloaded using the
ApplicationUrl attribute (at least the documentation implies that), but
I have not tested it.
 
#4.  The only things you can control are the name for your application
(using the ApplicationName attribute).  The rest of the UI is
un-configurable.
 
#5.  The bootstrapper generates a setup.exe to sit beside your .msi (and
any of your dependencies if you are not downloading them).  You could
use tools like PackageForTheWeb to pack them into a single file if you
need to, or you might be able to have everything be downloaded including
your .msi (see above) so that they only get the setup.exe.
 
#6.  You might be able to copy the existing SQL Express package and
adjust the rules in its product.xml file to make it not be installed if
SQL is already installed (you'll have to look at the product.xml and
learn its syntax by a combination of insight and trial and error--I
don't know of any documentation, but the format is pretty intuitive when
you look at it).  But you can't make dependecies optional for the user
to decide with this bootstrapper.  It doesn't support that.
 
#7. I sent you a previous email with a sample msbuild project file.  You
put your list of dependencies in the BootstrapperItems ItemGroup. 
 
#8.  No, it only supports either always downloaded or always local.
 
#8b.  If you are doing local, when you run the msbuild project, by
default it will copy the files to the output directory in the proper
directory structure.
 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Thielen
Sent: Wednesday, December 06, 2006 12:07 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] GenerateBootstrapper questions



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/
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/
html/custom_pkg.asp 
http://msdn2.microsoft.com/en-us/library/ms164294.aspx
http://www.gotdotnet.com/workspaces/workspace.aspx?id=ddb4f08c-7d7c-4f44
-a009-ea19fc812545

Sorry for all the questions - there is a lot of content about using the
bootstrapper to do X but none I could find about all the properties for
anything other than the samples shown. And unfortunately none showed
requiring J# (a prerequisite for us).

After reading the above (and some other pages) I have the following
questions about using this:
1) Where is complete documentation for GenerateBootstrapper - including
what to put in the package.xml to download from Microsoft (not included
in the package and not download from us but downloaded from MS if
needed):
a) .NET 2.0 framework
b) .NET 2.0 language pack if appropiate
c) J# 2.0 framework
d) J# 2.0 language pack if appropiate
e) whatever windows setup a wix built msi needs

2) Is there anywhere to get the Bootstrapper Manifest Generator and is
it worth using? The download link at
http://www.gotdotnet.com/workspaces/workspace.aspx?id=ddb4f08c-7d7c-4f44
-a009-ea19fc812545 does not work.

3) How do I set it to run our msi installer when it is done with the
prerequisites? And is it embedded in the created setup.exe or downloaded
at that time? If an option, which is recomended.

4) How do I put out name and text in the dialogs for setup.exe?

5) Is this a single file? Or is this a set of files that we need to
write an installer for?

6) Is there a way to make Sql Server Express an option and not show it
as an option if Sql Server regular or express (not only express) is
already installed?

7) Are there any samples of how we should set up our part of package.xml
and the rest of our settings - both in our msbuild.proj file and in the
xml files that list what goes in to the bootstrapper.

8) Can this be set so that it will look first on disk for the needed
install files and then on MS' website so if we put this all on disk we
can use the same bootstrapper?

8b) And if so, where do we get those files and what is the directory
structure?

I hope with answers to the above I will have at most 1 - 2 followup
questions.

thanks - dave

 

 

David Thielen


Re: [WiX-users] GenerateBootstrapper questions

2006-12-06 Thread Wilson, Phil
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 resource #41, and opening the exe in VS 2005, looking at
the resources and exporting resource #41's SETUPCFG as a text file
will do it. In conjunction with the MSDN Magazine Bootstrapper article,
this is pretty much enough to figure things out. 

Phil Wilson 




From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Erv Walter
Sent: Wednesday, December 06, 2006 11:07 AM
To: David Thielen; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] GenerateBootstrapper questions


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 package.xml file at all unless you are
creating a redistributable package.  If you need to do that, you put the
HomeSite in the product.xml file.
 
#2.  Never tried it.  Don't know if it is useful.
 
#3.  In your msbuild project you set the ApplicationFile attribute to
the filename of your .msi on the GenerateBootstrapper task (see my
sample in a previous email).  It's not embedded.  It sits side by side
with the setup.exe.  I believe you can have it be downloaded using the
ApplicationUrl attribute (at least the documentation implies that), but
I have not tested it.
 
#4.  The only things you can control are the name for your application
(using the ApplicationName attribute).  The rest of the UI is
un-configurable.
 
#5.  The bootstrapper generates a setup.exe to sit beside your .msi (and
any of your dependencies if you are not downloading them).  You could
use tools like PackageForTheWeb to pack them into a single file if you
need to, or you might be able to have everything be downloaded including
your .msi (see above) so that they only get the setup.exe.
 
#6.  You might be able to copy the existing SQL Express package and
adjust the rules in its product.xml file to make it not be installed if
SQL is already installed (you'll have to look at the product.xml and
learn its syntax by a combination of insight and trial and error--I
don't know of any documentation, but the format is pretty intuitive when
you look at it).  But you can't make dependecies optional for the user
to decide with this bootstrapper.  It doesn't support that.
 
#7. I sent you a previous email with a sample msbuild project file.  You
put your list of dependencies in the BootstrapperItems ItemGroup. 
 
#8.  No, it only supports either always downloaded or always local.
 
#8b.  If you are doing local, when you run the msbuild project, by
default it will copy the files to the output directory in the proper
directory structure.
 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Thielen
Sent: Wednesday, December 06, 2006 12:07 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] GenerateBootstrapper questions



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/
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/
html/custom_pkg.asp 
http://msdn2.microsoft.com/en-us/library/ms164294.aspx
http://www.gotdotnet.com/workspaces/workspace.aspx?id=ddb4f08c-7d7c-4f44
-a009-ea19fc812545

Sorry for all the questions - there is a lot of content about using the
bootstrapper to do X but none I could find about all the properties for
anything other than the samples shown. And unfortunately none showed
requiring J# (a prerequisite for us).

After reading the above (and some other pages) I have the following
questions about using this:
1) Where is complete documentation for GenerateBootstrapper - including
what to put in the package.xml to download from Microsoft (not included
in the package and not download from us but downloaded from MS if
needed):
a) .NET 2.0 framework
b) .NET 2.0 language pack if appropiate
c) J# 2.0 framework
d) J# 2.0 language pack if appropiate
e) whatever windows setup a wix built msi needs

2) Is there anywhere to get the Bootstrapper Manifest Generator and is
it worth using? The download link at
http://www.gotdotnet.com/workspaces/workspace.aspx?id=ddb4f08c-7d7c-4f44
-a009-ea19fc812545 does not work.

3) How do I set it to run our msi installer when it is done with the
prerequisites? And is it embedded in the created setup.exe or downloaded
at that time? If an option, which is recomended.

4) How do I put out name and text in the dialogs for setup.exe?

5) Is this a single 

Re: [WiX-users] GenerateBootstrapper questions

2006-12-06 Thread David Thielen
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 assume that the install programs for things like the .NET framework
are downloaded with setup.exe which eliminates the whole purpose of it.

 

Thanks - dave

 

 

David Thielen

www.windwardreports.com

303-499-2544 x1185

 

Cubicle Wars - http://www.windwardreports.com/film.htm



From: Erv Walter [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, December 06, 2006 12:07 PM
To: David Thielen; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] GenerateBootstrapper questions

 

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 package.xml file at all unless you are
creating a redistributable package.  If you need to do that, you put the
HomeSite in the product.xml file.

 

#2.  Never tried it.  Don't know if it is useful.

 

#3.  In your msbuild project you set the ApplicationFile attribute to
the filename of your .msi on the GenerateBootstrapper task (see my
sample in a previous email).  It's not embedded.  It sits side by side
with the setup.exe.  I believe you can have it be downloaded using the
ApplicationUrl attribute (at least the documentation implies that), but
I have not tested it.

 

#4.  The only things you can control are the name for your application
(using the ApplicationName attribute).  The rest of the UI is
un-configurable.

 

#5.  The bootstrapper generates a setup.exe to sit beside your .msi (and
any of your dependencies if you are not downloading them).  You could
use tools like PackageForTheWeb to pack them into a single file if you
need to, or you might be able to have everything be downloaded including
your .msi (see above) so that they only get the setup.exe.

 

#6.  You might be able to copy the existing SQL Express package and
adjust the rules in its product.xml file to make it not be installed if
SQL is already installed (you'll have to look at the product.xml and
learn its syntax by a combination of insight and trial and error--I
don't know of any documentation, but the format is pretty intuitive when
you look at it).  But you can't make dependecies optional for the user
to decide with this bootstrapper.  It doesn't support that.

 

#7. I sent you a previous email with a sample msbuild project file.  You
put your list of dependencies in the BootstrapperItems ItemGroup. 

 

#8.  No, it only supports either always downloaded or always local.

 

#8b.  If you are doing local, when you run the msbuild project, by
default it will copy the files to the output directory in the proper
directory structure.

 

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Thielen
Sent: Wednesday, December 06, 2006 12:07 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] GenerateBootstrapper questions

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/
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/
html/custom_pkg.asp 
http://msdn2.microsoft.com/en-us/library/ms164294.aspx
http://www.gotdotnet.com/workspaces/workspace.aspx?id=ddb4f08c-7d7c-4f44
-a009-ea19fc812545

Sorry for all the questions - there is a lot of content about using the
bootstrapper to do X but none I could find about all the properties for
anything other than the samples shown. And unfortunately none showed
requiring J# (a prerequisite for us).

After reading the above (and some other pages) I have the following
questions about using this:
1) Where is complete documentation for GenerateBootstrapper - including
what to put in the package.xml to download from Microsoft (not included
in the package and not download from us but downloaded from MS if
needed):
a) .NET 2.0 framework
b) .NET 2.0 language pack if appropiate
c) J# 2.0 framework
d) J# 2.0 language pack if appropiate
e) whatever windows setup a wix built msi needs

2) Is there anywhere to get the Bootstrapper Manifest Generator and is
it worth using? The download link at
http://www.gotdotnet.com/workspaces/workspace.aspx?id=ddb4f08c-7d7c-4f44
-a009-ea19fc812545 does not work.

3) How do I set it to run our msi installer when it is done with the
prerequisites? And is it embedded in the created setup.exe or downloaded
at that time? If an option, which is recomended.

4) How do I put out name and text in the dialogs for setup.exe?

5) Is 

Re: [WiX-users] GenerateBootstrapper questions

2006-12-06 Thread Wilson, Phil
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, December 06, 2006 1:15 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] GenerateBootstrapper questions



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 assume that the install programs for things like the .NET framework
are downloaded with setup.exe which eliminates the whole purpose of it.

 

Thanks - dave

 

 

David Thielen

www.windwardreports.com

303-499-2544 x1185

 

Cubicle Wars - http://www.windwardreports.com/film.htm



From: Erv Walter [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, December 06, 2006 12:07 PM
To: David Thielen; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] GenerateBootstrapper questions

 

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 package.xml file at all unless you are
creating a redistributable package.  If you need to do that, you put the
HomeSite in the product.xml file.

 

#2.  Never tried it.  Don't know if it is useful.

 

#3.  In your msbuild project you set the ApplicationFile attribute to
the filename of your .msi on the GenerateBootstrapper task (see my
sample in a previous email).  It's not embedded.  It sits side by side
with the setup.exe.  I believe you can have it be downloaded using the
ApplicationUrl attribute (at least the documentation implies that), but
I have not tested it.

 

#4.  The only things you can control are the name for your application
(using the ApplicationName attribute).  The rest of the UI is
un-configurable.

 

#5.  The bootstrapper generates a setup.exe to sit beside your .msi (and
any of your dependencies if you are not downloading them).  You could
use tools like PackageForTheWeb to pack them into a single file if you
need to, or you might be able to have everything be downloaded including
your .msi (see above) so that they only get the setup.exe.

 

#6.  You might be able to copy the existing SQL Express package and
adjust the rules in its product.xml file to make it not be installed if
SQL is already installed (you'll have to look at the product.xml and
learn its syntax by a combination of insight and trial and error--I
don't know of any documentation, but the format is pretty intuitive when
you look at it).  But you can't make dependecies optional for the user
to decide with this bootstrapper.  It doesn't support that.

 

#7. I sent you a previous email with a sample msbuild project file.  You
put your list of dependencies in the BootstrapperItems ItemGroup. 

 

#8.  No, it only supports either always downloaded or always local.

 

#8b.  If you are doing local, when you run the msbuild project, by
default it will copy the files to the output directory in the proper
directory structure.

 

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Thielen
Sent: Wednesday, December 06, 2006 12:07 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] GenerateBootstrapper questions

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/
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/
html/custom_pkg.asp 
http://msdn2.microsoft.com/en-us/library/ms164294.aspx
http://www.gotdotnet.com/workspaces/workspace.aspx?id=ddb4f08c-7d7c-4f44
-a009-ea19fc812545

Sorry for all the questions - there is a lot of content about using the
bootstrapper to do X but none I could find about all the properties for
anything other than the samples shown. And unfortunately none showed
requiring J# (a prerequisite for us).

After reading the above (and some other pages) I have the following
questions about using this:
1) Where is complete documentation for GenerateBootstrapper - including
what to put in the package.xml to download from Microsoft (not included
in the package and not download from us but downloaded from MS if
needed):
a) .NET 2.0 framework
b) .NET 2.0 language pack if appropiate
c) J# 2.0 framework
d) J# 2.0 language pack if appropiate
e) whatever windows setup a wix built msi needs

2) Is there anywhere to get the Bootstrapper Manifest Generator and 

Re: [WiX-users] GenerateBootstrapper questions

2006-12-06 Thread David Thielen
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

www.windwardreports.com

303-499-2544 x1185

 

Cubicle Wars - http://www.windwardreports.com/film.htm



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wilson,
Phil
Sent: Wednesday, December 06, 2006 2:06 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] GenerateBootstrapper questions

 

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 resource #41, and opening the exe in VS 2005, looking at
the resources and exporting resource #41's SETUPCFG as a text file
will do it. In conjunction with the MSDN Magazine Bootstrapper article,
this is pretty much enough to figure things out. 

Phil Wilson 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Erv Walter
Sent: Wednesday, December 06, 2006 11:07 AM
To: David Thielen; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] GenerateBootstrapper questions

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 package.xml file at all unless you are
creating a redistributable package.  If you need to do that, you put the
HomeSite in the product.xml file.

 

#2.  Never tried it.  Don't know if it is useful.

 

#3.  In your msbuild project you set the ApplicationFile attribute to
the filename of your .msi on the GenerateBootstrapper task (see my
sample in a previous email).  It's not embedded.  It sits side by side
with the setup.exe.  I believe you can have it be downloaded using the
ApplicationUrl attribute (at least the documentation implies that), but
I have not tested it.

 

#4.  The only things you can control are the name for your application
(using the ApplicationName attribute).  The rest of the UI is
un-configurable.

 

#5.  The bootstrapper generates a setup.exe to sit beside your .msi (and
any of your dependencies if you are not downloading them).  You could
use tools like PackageForTheWeb to pack them into a single file if you
need to, or you might be able to have everything be downloaded including
your .msi (see above) so that they only get the setup.exe.

 

#6.  You might be able to copy the existing SQL Express package and
adjust the rules in its product.xml file to make it not be installed if
SQL is already installed (you'll have to look at the product.xml and
learn its syntax by a combination of insight and trial and error--I
don't know of any documentation, but the format is pretty intuitive when
you look at it).  But you can't make dependecies optional for the user
to decide with this bootstrapper.  It doesn't support that.

 

#7. I sent you a previous email with a sample msbuild project file.  You
put your list of dependencies in the BootstrapperItems ItemGroup. 

 

#8.  No, it only supports either always downloaded or always local.

 

#8b.  If you are doing local, when you run the msbuild project, by
default it will copy the files to the output directory in the proper
directory structure.

 

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Thielen
Sent: Wednesday, December 06, 2006 12:07 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] GenerateBootstrapper questions

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/
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/
html/custom_pkg.asp 
http://msdn2.microsoft.com/en-us/library/ms164294.aspx
http://www.gotdotnet.com/workspaces/workspace.aspx?id=ddb4f08c-7d7c-4f44
-a009-ea19fc812545

Sorry for all the questions - there is a lot of content about using the
bootstrapper to do X but none I could find about all the properties for
anything other than the samples shown. And unfortunately none showed
requiring J# (a prerequisite for us).

After reading the above (and some other pages) I have the following
questions about using this:
1) Where is complete documentation for GenerateBootstrapper - including
what to put in the package.xml to download from Microsoft (not included
in the package and not download from us but downloaded from MS if
needed):

Re: [WiX-users] GenerateBootstrapper questions

2006-12-06 Thread 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 www.microsoft.com
http://www.microsoft.com/  and runs it.

 

Thanks - dave

 

 

 

David Thielen

www.windwardreports.com

303-499-2544 x1185

 

Cubicle Wars - http://www.windwardreports.com/film.htm



From: Wilson, Phil [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, December 06, 2006 2:25 PM
To: David Thielen; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] GenerateBootstrapper questions

 

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, December 06, 2006 1:15 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] GenerateBootstrapper questions

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 assume that the install programs for things like the .NET framework
are downloaded with setup.exe which eliminates the whole purpose of it.

 

Thanks - dave

 

 

David Thielen

www.windwardreports.com

303-499-2544 x1185

 

Cubicle Wars - http://www.windwardreports.com/film.htm



From: Erv Walter [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, December 06, 2006 12:07 PM
To: David Thielen; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] GenerateBootstrapper questions

 

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 package.xml file at all unless you are
creating a redistributable package.  If you need to do that, you put the
HomeSite in the product.xml file.

 

#2.  Never tried it.  Don't know if it is useful.

 

#3.  In your msbuild project you set the ApplicationFile attribute to
the filename of your .msi on the GenerateBootstrapper task (see my
sample in a previous email).  It's not embedded.  It sits side by side
with the setup.exe.  I believe you can have it be downloaded using the
ApplicationUrl attribute (at least the documentation implies that), but
I have not tested it.

 

#4.  The only things you can control are the name for your application
(using the ApplicationName attribute).  The rest of the UI is
un-configurable.

 

#5.  The bootstrapper generates a setup.exe to sit beside your .msi (and
any of your dependencies if you are not downloading them).  You could
use tools like PackageForTheWeb to pack them into a single file if you
need to, or you might be able to have everything be downloaded including
your .msi (see above) so that they only get the setup.exe.

 

#6.  You might be able to copy the existing SQL Express package and
adjust the rules in its product.xml file to make it not be installed if
SQL is already installed (you'll have to look at the product.xml and
learn its syntax by a combination of insight and trial and error--I
don't know of any documentation, but the format is pretty intuitive when
you look at it).  But you can't make dependecies optional for the user
to decide with this bootstrapper.  It doesn't support that.

 

#7. I sent you a previous email with a sample msbuild project file.  You
put your list of dependencies in the BootstrapperItems ItemGroup. 

 

#8.  No, it only supports either always downloaded or always local.

 

#8b.  If you are doing local, when you run the msbuild project, by
default it will copy the files to the output directory in the proper
directory structure.

 

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Thielen
Sent: Wednesday, December 06, 2006 12:07 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] GenerateBootstrapper questions

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/
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/
html/custom_pkg.asp 
http://msdn2.microsoft.com/en-us/library/ms164294.aspx
http://www.gotdotnet.com/workspaces/workspace.aspx?id=ddb4f08c-7d7c-4f44
-a009-ea19fc812545

Sorry for all the questions - there is a lot of content about using 

Re: [WiX-users] GenerateBootstrapper questions

2006-12-06 Thread Erv Walter
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 GenerateBootstrapper element in your
msbuild project file to be HomeSite as described here:
 
ComponentsLocation: Specifies a location for the bootstrapper to look
for installation prerequisites to install. This parameter can have the
following values::
 
HomeSite: Indicates that the prerequisite is being hosted by the
component vendor.
Relative: Indicates that the preqrequisite is at the same location of
the application.
Absolute: Indicates that all components are to be found at a centralized
URL. This value should be used in conjunction with the ComponentsUrl
input parameter.
 
If ComponentsLocation is not specified, HomeSite is used by default.
 
If you also want your msi to be downloaded, you specify the location
where the MSI is hosted using the ApplicationUrl attribute.
 
I attached a sample project that uses the things above.  It produces a
single setup.exe (421k) that does the following:

*   

If WIndows Installer 3.1 is not installed (it is required by SQL
Express), it downloads it from Microsoft and installs it.
If .NET 2.0 is not installed, it downloads it from Microsoft and
installs it.
*   
If J# 2.0 is not installed, it downloads it from Microsoft and
installs it.
*   If SQL Express is not installed, it downloads it from Microsoft
and installs it.
*   
It downloads installer.msi from http://localhost/installer.msi
and runs it

In case the attachment doesn't work, here are the contents:
 
Project xmlns=http://schemas.microsoft.com/developer/msbuild/2003;
  ItemGroup
!-- Include the 'Product Code' for every package you want --
BootstrapperFile Include=Microsoft.Net.Framework.2.0
  ProductName.NET Framework 2.0/ProductName
/BootstrapperFile
BootstrapperFile Include=Microsoft.JSharp.2.0
  ProductNameMicrosoft Visual J# .NET Redistributable Package
2.0/ProductName
/BootstrapperFile
BootstrapperFile Include=Microsoft.Sql.Server.Express.1.0
  ProductNameSQL Server 2005 Express Edition/ProductName
/BootstrapperFile
BootstrapperFile Include=Microsoft.Windows.Installer.3.1
  ProductNameWindows Installer 3.1/ProductName
/BootstrapperFile
  /ItemGroup
 
  Target Name=Build
GenerateBootstrapper 
   ApplicationName=My Installer 
   ApplicationFile=installer.msi
   ApplicationUrl=http://localhost/;
   BootstrapperItems=@(BootstrapperFile) 
   Culture=en
   ComponentsLocation=HomeSite
   CopyComponents=False 
   OutputPath=bin\ /
  /Target
/Project
 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Thielen
Sent: Wednesday, December 06, 2006 3:27 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] GenerateBootstrapper questions



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 www.microsoft.com
http://www.microsoft.com/  and runs it.

 

Thanks - dave

 

 

 

David Thielen

www.windwardreports.com

303-499-2544 x1185

 

Cubicle Wars - http://www.windwardreports.com/film.htm



From: Wilson, Phil [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, December 06, 2006 2:25 PM
To: David Thielen; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] GenerateBootstrapper questions

 

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, December 06, 2006 1:15 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] GenerateBootstrapper questions

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 assume that the install programs for things like the .NET framework
are downloaded with setup.exe which eliminates the whole purpose of it.

 

Thanks - dave

 

 

David Thielen

www.windwardreports.com

303-499-2544 x1185

 

Cubicle Wars - http://www.windwardreports.com/film.htm



From: Erv Walter [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, December 06, 2006 12:07 PM
To: David Thielen; wix-users@lists.sourceforge.net
Subject: 

Re: [WiX-users] GenerateBootstrapper questions

2006-12-06 Thread Tony.Bjerstedt
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 PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Thielen
Sent: Wednesday, December 06, 2006 3:27 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] GenerateBootstrapper questions

 

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 www.microsoft.com
http://www.microsoft.com/  and runs it.

 

Thanks - dave

 

 

 

David Thielen

www.windwardreports.com

303-499-2544 x1185

 

Cubicle Wars - http://www.windwardreports.com/film.htm



From: Wilson, Phil [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, December 06, 2006 2:25 PM
To: David Thielen; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] GenerateBootstrapper questions

 

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, December 06, 2006 1:15 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] GenerateBootstrapper questions

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 assume that the install programs for things like the .NET framework
are downloaded with setup.exe which eliminates the whole purpose of it.

 

Thanks - dave

 

 

David Thielen

www.windwardreports.com

303-499-2544 x1185

 

Cubicle Wars - http://www.windwardreports.com/film.htm



From: Erv Walter [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, December 06, 2006 12:07 PM
To: David Thielen; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] GenerateBootstrapper questions

 

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 package.xml file at all unless you are
creating a redistributable package.  If you need to do that, you put the
HomeSite in the product.xml file.

 

#2.  Never tried it.  Don't know if it is useful.

 

#3.  In your msbuild project you set the ApplicationFile attribute to
the filename of your .msi on the GenerateBootstrapper task (see my
sample in a previous email).  It's not embedded.  It sits side by side
with the setup.exe.  I believe you can have it be downloaded using the
ApplicationUrl attribute (at least the documentation implies that), but
I have not tested it.

 

#4.  The only things you can control are the name for your application
(using the ApplicationName attribute).  The rest of the UI is
un-configurable.

 

#5.  The bootstrapper generates a setup.exe to sit beside your .msi (and
any of your dependencies if you are not downloading them).  You could
use tools like PackageForTheWeb to pack them into a single file if you
need to, or you might be able to have everything be downloaded including
your .msi (see above) so that they only get the setup.exe.

 

#6.  You might be able to copy the existing SQL Express package and
adjust the rules in its product.xml file to make it not be installed if
SQL is already installed (you'll have to look at the product.xml and
learn its syntax by a combination of insight and trial and error--I
don't know of any documentation, but the format is pretty intuitive when
you look at it).  But you can't make dependecies optional for the user
to decide with this bootstrapper.  It doesn't support that.

 

#7. I sent you a previous email with a sample msbuild project file.  You
put your list of dependencies in the BootstrapperItems ItemGroup. 

 

#8.  No, it only supports either always downloaded or always local.

 

#8b.  If you are doing local, when you run the msbuild project, by
default it will copy the files to the output directory in the proper
directory structure.

 

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Thielen
Sent: Wednesday, December 06, 2006 12:07 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] GenerateBootstrapper questions

Hi;

I posted this also in the MS forums (no answer) 

Re: [WiX-users] turning logging on for installutil

2006-12-06 Thread Mike Dimmick
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
track where the file is written to.

 

-- 

Mike Dimmick

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Victor Garcia
Aprea
Sent: 05 December 2006 21:05
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] turning logging on for installutil

 


I'm editing with Orca a MSI generated with WiX. In the custom actions table
I have an entry for custom action type 1025:

/Configuration=[INSTALLDIR]SoftwareFactory91.xml
/installtype=notransaction /action=install /LogFile= [#InstallerAssembly]
[#InstallerConfigFile] 

When using the MSI (with verbose logging) I'm noticing that this custom
error is failing so I would like to turn logging on for installutil. I'm
modifying the above entry like this:

/Configuration=[INSTALLDIR]SoftwareFactory91.xml
/installtype=notransaction /action=install /LogFile=blah.log
[#InstallerAssembly] [#InstallerConfigFile]

and I'm not getting any blah.log file...; I'm not sure where this log file
should be writed to but checked a few folders (the current one where the MSI
is, the one where the assembly containing the installer class is, etc)
without any luck... 

Any hints?

thanks!,
-Victor.

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] VS2005 C++ and Custom Actions

2006-12-06 Thread Mike Dimmick
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 DLLs.

 

The WiX custom actions should probably take the lead here and replace calls
to CRT functions with equivalent Windows functions, then replace the
CRT-supplied entry point function with a stub. This could well reduce the
size of the custom action DLLs.

 

-- 

Mike Dimmick

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matthew
Kowalski
Sent: 05 December 2006 19:42
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] VS2005 C++ and Custom Actions

 

I've created a simple C++ .dll in VS2005 to do some checks for me during the
install after a user has selected an installation folder. The problem I am
having is with the VS2005 C++ runtime (msvcp80.dll). The compiled .dll
apparently needs to have the runtime installed otherwise the installation
fails when attempting to execute the custom action (Dependent Assembly
Microsoft.VC80.CRT could not be found). Is there any way to get around
having to install the redistributable package (vcredist_x86.exe) before
running my install?

 

Any help would be greatly appreciated!

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] GenerateBootstrapper questions

2006-12-06 Thread Wilson, Phil
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] GenerateBootstrapper questions



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

www.windwardreports.com

303-499-2544 x1185

 

Cubicle Wars - http://www.windwardreports.com/film.htm



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wilson,
Phil
Sent: Wednesday, December 06, 2006 2:06 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] GenerateBootstrapper questions

 

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 resource #41, and opening the exe in VS 2005, looking at
the resources and exporting resource #41's SETUPCFG as a text file
will do it. In conjunction with the MSDN Magazine Bootstrapper article,
this is pretty much enough to figure things out. 

Phil Wilson 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Erv Walter
Sent: Wednesday, December 06, 2006 11:07 AM
To: David Thielen; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] GenerateBootstrapper questions

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 package.xml file at all unless you are
creating a redistributable package.  If you need to do that, you put the
HomeSite in the product.xml file.

 

#2.  Never tried it.  Don't know if it is useful.

 

#3.  In your msbuild project you set the ApplicationFile attribute to
the filename of your .msi on the GenerateBootstrapper task (see my
sample in a previous email).  It's not embedded.  It sits side by side
with the setup.exe.  I believe you can have it be downloaded using the
ApplicationUrl attribute (at least the documentation implies that), but
I have not tested it.

 

#4.  The only things you can control are the name for your application
(using the ApplicationName attribute).  The rest of the UI is
un-configurable.

 

#5.  The bootstrapper generates a setup.exe to sit beside your .msi (and
any of your dependencies if you are not downloading them).  You could
use tools like PackageForTheWeb to pack them into a single file if you
need to, or you might be able to have everything be downloaded including
your .msi (see above) so that they only get the setup.exe.

 

#6.  You might be able to copy the existing SQL Express package and
adjust the rules in its product.xml file to make it not be installed if
SQL is already installed (you'll have to look at the product.xml and
learn its syntax by a combination of insight and trial and error--I
don't know of any documentation, but the format is pretty intuitive when
you look at it).  But you can't make dependecies optional for the user
to decide with this bootstrapper.  It doesn't support that.

 

#7. I sent you a previous email with a sample msbuild project file.  You
put your list of dependencies in the BootstrapperItems ItemGroup. 

 

#8.  No, it only supports either always downloaded or always local.

 

#8b.  If you are doing local, when you run the msbuild project, by
default it will copy the files to the output directory in the proper
directory structure.

 

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Thielen
Sent: Wednesday, December 06, 2006 12:07 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] GenerateBootstrapper questions

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/
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/
html/custom_pkg.asp 
http://msdn2.microsoft.com/en-us/library/ms164294.aspx
http://www.gotdotnet.com/workspaces/workspace.aspx?id=ddb4f08c-7d7c-4f44
-a009-ea19fc812545

Sorry for all the questions - there is a lot of content about using the
bootstrapper to do X but none I could find about all the properties for
anything other than the samples shown. And unfortunately none showed
requiring J# (a prerequisite for 

[WiX-users] Comparing two MSIs

2006-12-06 Thread Cullen Waters
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 Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Comparing two MSIs

2006-12-06 Thread Peterson, Joel
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
Sent: Wednesday, December 06, 2006 3:28 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Comparing two MSIs

 

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 Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Comparing two MSIs

2006-12-06 Thread 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 MSIs

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
Sent: Wednesday, December 06, 2006 3:28 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Comparing two MSIs

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 Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] bootstrapper - final questions (I think)

2006-12-06 Thread Rob MacFadyen
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 offers a free tool to do
this:
http://www.chilkatsoft.com/ChilkatSfx.asp
 
The also offer a component you can use that offers a few more options.
 
For #2: In the GenerateBootstrapper element there is a Culture and
FallbackCulture attributes. These control the language. If you examine the
following directories:
C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages
you will see under each directory, like dotnetfx, a sub directory titled
en (if you're using english). If you examine the Package.xml file you'll
see the localized strings and the url's for the actual downloads.
 
It's a good question where/how to get the other languages (I don't know...
you could brute force it by installing VS2005 in a virtual PC in all the
languages you need).
 
If you need more than one language you will need to generate more than one
Setup.exe. It _ought_ to be simple enough to stuff each Setup.exe in a
subdirectory by culture (so you end up with en\Setup.exe, es\Setup.exe,
fr\Setup.exe and so on). You would then need a quick and dirty front end
that offers a please pick language facility and then invokes the
appropriate setup. Or you could just have separate downloads for each
language.
 
#3 and #4 are not handled by the GenerateBootstrapper at all. Generally
these sort of requirements are handled by your actual MSI. The general
scheme is to detect whether or not a requirement has been met and if not
display a message say missing component X. For an improved user experience
you could show a single dialog that lists all the required components and
whether or not they are present (only show the dialog if at least one is
missing).
 
Detecting IIS is fairly easy in v3: 

link with WixIIsExtension.dll and then the following just works:

PropertyRef Id=IISMAJORVERSION/

Condition Message=IIS version 5 or 6 must be installed
([IISMAJORVERSION])

  Installed OR (IISMAJORVERSION = #5 OR IISMAJORVERSION = #6)

/Condition

Not sure about Wix v2.
 
Hotfixes might not be too bad to detect if they show up in Add/Remove
Programs. If you can determine thee  upgradecode/productcode for each hot
fix, then the Upgrade elements should be able to help... make sure
OnlyDetect is set though. Take a gawk at:
http://www.tramontana.co.hu/wix/lesson4.php
 
Regards,
 
Rob
 
 
  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David Thielen
Sent: Wednesday, December 06, 2006 6:15 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] bootstrapper - final questions (I think)



First off - THANK YOU very much to everyone who helped and in particular Erv
Walter.

 

I think I have it working. A couple of questions:

1.  If all the prerequisites exist and I use ApplicationUrl what happens
is a window pops up for a split second, goes away, and then nothing while it
is downloading. Then our program pops up. Is there some way to get a message
while this is happening, preferably with a status bar? Otherwise people are
going to think it just went away - especially if their download speed is
slow. 


1.  Note - this is only an issue if all prerequisites are already
installed. If a prerequisite needs to be installed then this download will
show with a status bar. 

2.  If that cannot be done, what's the best way to structure this? It
seems to me it is have a MSI that holds setup.exe and our MSI, it installs
both, runs setup.exe and it calls the other MSI locally at the end. But this
means we then have 2 MSIs and that's ugly. Any other approaches? 

2.  Any idea what to put in for the .NET 2.0 and J# 2.0 language packs? 

3.  Any idea what to put in to get the Office hotfixes (listed at
http://www.windwardreports.com/office_hotfix.htm) to install? Two of them
for Word 200/2002/2003 and one for Word 2003 only. 

4.  Any idea how to make IIS a prerequisite (sort-of essential for an
ASP.NET app). 

 

Thanks - dave

 

 

 

David Thielen

 http://www.windwardreports.com www.windwardreports.com

303-499-2544 x1185

 

Cubicle Wars -  http://www.windwardreports.com/film.htm
http://www.windwardreports.com/film.htm

 

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Comparing two MSIs

2006-12-06 Thread Michael Osmond
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: [WiX-users] Comparing two MSIs



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
Sent: Wednesday, December 06, 2006 3:28 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Comparing two MSIs

 

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 Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] bootstrapper - final questions (I think)

2006-12-06 Thread David Thielen
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 the help here has been invaluable.

 

Thanks - dave

 

 

 

David Thielen

www.windwardreports.com

303-499-2544 x1185

 

Cubicle Wars - http://www.windwardreports.com/film.htm



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
MacFadyen
Sent: Wednesday, December 06, 2006 5:25 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] bootstrapper - final questions (I think)

 

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 offers a free tool to
do this:

http://www.chilkatsoft.com/ChilkatSfx.asp

 

The also offer a component you can use that offers a few more options.

 

For #2: In the GenerateBootstrapper element there is a Culture and
FallbackCulture attributes. These control the language. If you examine
the following directories:

C:\Program Files\Microsoft Visual Studio
8\SDK\v2.0\BootStrapper\Packages you will see under each directory, like
dotnetfx, a sub directory titled en (if you're using english). If you
examine the Package.xml file you'll see the localized strings and the
url's for the actual downloads.

 

It's a good question where/how to get the other languages (I don't
know... you could brute force it by installing VS2005 in a virtual PC
in all the languages you need).

 

If you need more than one language you will need to generate more than
one Setup.exe. It _ought_ to be simple enough to stuff each Setup.exe in
a subdirectory by culture (so you end up with en\Setup.exe,
es\Setup.exe, fr\Setup.exe and so on). You would then need a quick and
dirty front end that offers a please pick language facility and then
invokes the appropriate setup. Or you could just have separate downloads
for each language.

 

#3 and #4 are not handled by the GenerateBootstrapper at all. Generally
these sort of requirements are handled by your actual MSI. The general
scheme is to detect whether or not a requirement has been met and if not
display a message say missing component X. For an improved user
experience you could show a single dialog that lists all the required
components and whether or not they are present (only show the dialog if
at least one is missing).

 

Detecting IIS is fairly easy in v3: 

link with WixIIsExtension.dll and then the following just
works:

PropertyRef Id=IISMAJORVERSION/
Condition Message=IIS version 5 or 6 must be installed
([IISMAJORVERSION])
  Installed OR (IISMAJORVERSION = #5 OR IISMAJORVERSION =
#6)
/Condition

Not sure about Wix v2.

 

Hotfixes might not be too bad to detect if they show up in Add/Remove
Programs. If you can determine thee  upgradecode/productcode for each
hot fix, then the Upgrade elements should be able to help... make sure
OnlyDetect is set though. Take a gawk at:

http://www.tramontana.co.hu/wix/lesson4.php

 

Regards,

 

Rob

 

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Thielen
Sent: Wednesday, December 06, 2006 6:15 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] bootstrapper - final questions (I think)

First off - THANK YOU very much to everyone who helped and in particular
Erv Walter.

 

I think I have it working. A couple of questions:

1.  If all the prerequisites exist and I use ApplicationUrl what
happens is a window pops up for a split second, goes away, and then
nothing while it is downloading. Then our program pops up. Is there some
way to get a message while this is happening, preferably with a status
bar? Otherwise people are going to think it just went away - especially
if their download speed is slow. 

1.  Note - this is only an issue if all prerequisites are
already installed. If a prerequisite needs to be installed then this
download will show with a status bar. 
2.  If that cannot be done, what's the best way to structure
this? It seems to me it is have a MSI that holds setup.exe and our MSI,
it installs both, runs setup.exe and it calls the other MSI locally at
the end. But this means we then have 2 MSIs and that's ugly. Any other
approaches? 

2.  Any idea what to put in for the .NET 2.0 and J# 2.0 language
packs? 
3.  Any idea what to put in to get the Office hotfixes (listed at
http://www.windwardreports.com/office_hotfix.htm) to install? Two of
them for Word 200/2002/2003 and one for Word 2003 only. 
4.  Any idea how to make IIS a prerequisite (sort-of essential for
an 

Re: [WiX-users] VS2005 C++ and Custom Actions

2006-12-06 Thread Bob Arnson

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 
calls to CRT functions with equivalent Windows functions, then replace 
the CRT-supplied entry point function with a stub. This could well 
reduce the size of the custom action DLLs.




Why? Unless we got rid of CRT dependencies entirely...

--
sig://boB
http://bobs.org

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Need recomendation - including .NET redist

2006-12-06 Thread Bob Arnson
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 of fresh
 installation, it was working properly. 

What kind of upgrade did you do? Check a verbose log around 
InstallValidate to see which components MSI thought it needed to install.

-- 
sig://boB
http://bobs.org



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Votive 3 Project Variables

2006-12-06 Thread Ben Rampling
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 exist. I've checked the source to see
what might take their place and didn't find anything.

If the lack of these variables are a deliberate omission from the new
version, what is the best workaround? If I define them manually, the
project can't determine if it should grab files from obj\Debug or
\obj\Release.


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users