I have some questions about building a Setup.exe from VS2005 Pro:

1. I'm confused about how I can configure it to build a SINGLE Setup.exe
that doesn't require any other files. When I set it up for a "CD-ROM"
install, I get a Setup.exe but a bunch of other files are created in the
Installer Directory. Do I need to distribute them too?

2. How can I designate file that are in my Project so that they'll be copied
into the Setup.exe and then installed in the same directory as the
Program.exe when it is installed? I mean files that are not code files.

3. Whe I go to install what I've built on a plain Win XP box, I get an error
"Setup Update Required: Unable to Install or Run the Application. The
application required that assembly stdoleversion 7.0.3300.0 be installed in
the GAC first. Please contact your administrator." Boy, what on earth does
THAT mean?

Thanks.

Hi Alex,

Regarding on the questions on building VS 2005 setup project you mentioned,
here are some of my understanding and suggestion:

1. I'm confused about how I can configure it to build a SINGLE Setup.exe
that doesn't require any other files. When I set it up for a "CD-ROM"
......................
==========================
Are you using the VS setup project to build the install package or use the
clickonce "publish" function? For VS setup project, it will merge the
files you include in the project into a single package file and in the
output folder it will at least contains two package, one is "setup.exe" and
another is "setup.msi". If your setup project have included any
bootstrapper packages(which can not be downloaded from web url), it will
also create folders for those bootstrapper packages. Is this what you get?


2. How can I designate file that are in my Project so that they'll be
copied ....................
===========================
Would you provide some further description about your main project? Such as
its project type, its content and whether it reference any other components
.... Normally, in the setup project's "File System View", you can choose
to include content/files from main project(generally you will choose the
primary output or any content files from the main project). After build
the setup project, they should be merged into a single setup package(msi or
exe).



3. Whe I go to install what I've built on a plain Win XP box, I get an
error...............
===========================
I have performed some research according to this error message, it seems
that the "stdole" is a Office PIA(primary interop assembly). Have you used
any office component(such as chart ...) in your main application? The
office PIA will be installed if you have .net framework and Office 2003
installed on the target machine. You can check this to see whether it
matches your case.

BTW, office PIA redistribute package is available in the following address:

http://www.microsoft.com/downloads/details.aspx?familyid=3c9a983a-ac14-4125-
8ba0-d36d67e0f4ad&displaylang=en

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.



Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.

==================================================



This posting is provided "AS IS" with no warranties, and confers no rights.

1) VS doesn't do that. If you want a single exe, use some 3rd party zipper
that puts exe and MSI into one exe and runs the setup.exe when extracted.
There are good reasons for having the MSI separate and available (a repair
may require access to the original MSI file).
Setup.exe is for prerequisites. If you don't have any, then you only need
the MSI file.

2) See 1. It doesn't work like that so you can't. Setup.exe is
prerequisites, yourfiles are in the MSI file.

3) What did you run? Setup.exe? The MSI? This might be a completely separate
issue that's nothing to do with your app and its setup, but if it's a .NET
app did you install the right framework?
--
Phil Wilson
[Microsoft MVP-Windows Installer]

[quoted text, click to view]