| |
> You *don't* want to use a VB-based program as an installer. Before a VB program
> can run, all the VB-runtime files have to be installed. This means that the
> setup program has to install multi-megabytes of *system* files before the user
> sees anything useful. With the possibility of requiring a reboot mid-install.
> It's *not* pretty.
That is all well and good but remember that is a lot of cases the vb runtime dlls
are going to be installed anyway, when things like LDAO or the like are installed.
--
Jonathan Wilson
wilsonj@xoommail.com
http://members.xoom.com/wilsonj/
|
|
Message has 1 Reply:
 | | Re: Organizing the LDraw CD-ROM
|
| (...) So? In many more cases, the VB runtimes will *not* be installed. And the not-installed machines are more likely to be run by the technically-un-savvy. An easy-to-use installer doesn't do any good if it won't run on the majority of machines. (...) (24 years ago, 8-Feb-00, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
Message is in Reply To:
| | Re: Organizing the LDraw CD-ROM
|
| (...) You *don't* want to use a VB-based program as an installer. Before a VB program can run, all the VB-runtime files have to be installed. This means that the setup program has to install multi-megabytes of *system* files before the user sees (...) (24 years ago, 7-Feb-00, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
28 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
