Re: Visual Basic executable file
- From: "MikeD" <nobody@xxxxxxxxxxx>
- Date: Fri, 14 Apr 2006 18:48:04 -0400
"Saga" <antiSpam@xxxxxxxxxxxxx> wrote in message news:%23O7WwABYGHA.3936@xxxxxxxxxxxxxxxxxxxxxxx
No, simply use the the Package & Deployment wizard to create a setup
package for your app.
I think this reply is misleading. I have nothing against PDW and to this day still use it for *some* installations. But, there are well-known problems using PDW, particularly if the dev PC is running a later version of Windows and the app is subsequently installed on a PC running an older version of Windows.
The "fix" for most problems is quite simple. Simply update VB6 on the dev PC to SP5. This puts copies of critical system files into the Redist folder so that PDW includes those instead of what's actually installed.
But even if you do that, there ARE other problems that can arise. For example, as best as I can recall, the Setup program will "run" under a non-Admin login, but it won't be successful (unfortunately, I don't recall if it gives an error at some point, bombs, or "appears" to be successful but the app won't run). The reason I don't recall what happens is that I've modified Setup1 to check whether it's running under an Admin login.
--
Mike
Microsoft MVP Visual Basic
.
- Follow-Ups:
- Re: Visual Basic executable file
- From: Saga
- Re: Visual Basic executable file
- References:
- Re: Visual Basic executable file
- From: Saga
- Re: Visual Basic executable file
- From: Saga
- Re: Visual Basic executable file
- From: Pinto1uk
- Re: Visual Basic executable file
- From: Saga
- Re: Visual Basic executable file
- Prev by Date: Re: Visual Basic executable file
- Next by Date: Re: Place to initialialize globals in an OCX?
- Previous by thread: Re: Visual Basic executable file
- Next by thread: Re: Visual Basic executable file
- Index(es):
Relevant Pages
|