microsoft.public.dotnet.framework.setup

Phil Wilson

8/19/2006 8:38:00 PM

1. Just select the files you need and add them to the appropriate folder in
the File System on target machine 0drag and drop works).

There are a number of reasons why Dlls are not included in the setup, the
main one being that since Windows 2000 pretty much every Dll in the System32
folder is part of the OS and you do not redistribute them, and System File
Protection won't let you replace them.

2. A VS 2005 setup project builds a standard MSI setup like most other tools
that builds setups. You go to Add/Remove Programs to uninstall them.
--
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.ht...

"jimmy5 via DotNetMonster.com" <u15997@uwe> wrote in message
news:64dbdd6a1e71e@uwe...
> Hi
>
> I have a few of simple questions regarding VS 2005's setup Project.
>
> 1. In the past, I only use the package tool of VB 6 to create
> installation
> file for this VB 6 application. I like to know if I can use VS 2005's
> setup
> project for a VB 6 application. I have tried a bit. But I cannot find a
> way
> to let the setup project to include all DLLs needed in VB 6 application
> (there is at least one DLL written in C++ that I must have). The old VB6
> tool
> seems easy to use since it includes all DLLs needed. Am I missing
> something?
> I thought VS 2005's tool should include DLLs (third-party DLL or those
> Microsoft DLL in system32 folder) automatically.
>
> 2. The old VB 6 tool creates a uninstall.exe file, the new VS 2005 seems
> not.
> Or I need to change setting somewhere?
>
> Thank you!
>
> Jimmy
>
> --
> Message posted via DotNetMonster.com
> http://www.dotnetmonster.com/Uwe/Forums.aspx/dotnet-setu...
>