
Signature
ICQ-UIN: 14011335
Website: http://henrik.heimbuerger.de/en/
You can still use a Visual Studio setup project. It sounds like you'd like
the install to be simpler, and you could do that by deleting some of the
dialogs in the user interface view in the Visual Studio IDE. An alternative
is to still use a setup project, but wrap it into a program and launch your
setup silently with msiexec /i <path to the msi> /qn (or some other /q
flavor, depending how much UI you want to show the user).

Signature
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280
> Hi!
>
[quoted text clipped - 14 lines]
> TIA,
> Henrik Heimbuerger
Henrik Heimbuerger - 14 Dec 2004 14:06 GMT
>You can still use a Visual Studio setup project. It sounds like you'd like
>the install to be simpler, and you could do that by deleting some of the
>dialogs in the user interface view in the Visual Studio IDE. An alternative
>is to still use a setup project, but wrap it into a program and launch your
>setup silently with msiexec /i <path to the msi> /qn (or some other /q
>flavor, depending how much UI you want to show the user).
Good idea! I will do that if I don't find another solution. But this
would still be the source of many errors and I still don't understand
why the functionality of installutil.exe isn't included in the BCL!?
Thanks,
Henrik Heimbuerger

Signature
ICQ-UIN: 14011335
Website: http://henrik.heimbuerger.de/en/