using .NET installer to install vb6 Application

I wonder if anyone can tell me the advantages that using the .NET installer would make for my situation. We have a vb6 intranet app that does not use or require .NET (we don't want to require the framework either, but we may require it if we have to). Our homemade install program copies files, creates folders, edits registry info, etc, and updates or creates an entire sql server 2000 database from scratch. Is there a good reason to move our installation program into the .NET installer? If we did so, would the .NET Framework have to be installed on any system that we installed on? Thanks much

-D

The .Net Installer is nothing more than a pretty way to create an MSI package and judging by what you are already doing to install an app you probably are using a MSI packaging utility. Another thing you might want to look into is a MSI framework analyzer that the Windows SDK has call (Orca).

In regards to VB6 applications I would not worry about doing the .Net Installer. There are cheaper and more friendly ways to do this via other MSI packagers like (Advanced Installer by Caphyon). I have been using that to deply my VB6 apps for about 1 year now. It works like a champ. Oh and it is very inexpensive for the pro version and free for the simple version.

I have no clue if this helps, but that is what I would do in a similiar situation.