Stand alone *.exe in VB, is it,possible?
| Author |
Message |
|
Sulta
#1 / 11
|
 Stand alone *.exe in VB, is it,possible? Hi, VB Maniacs- I'm trying to install a VB application on the network where many users will
have the ability to access it. The problem I have with this is how do I
create a stand alone executable. I've never done this before. Please, let me
know of how I can do that if it's possible or perhaps point me into the
right direction. Any help will be very much appreciated.
Sultan
--
"The future belongs to those who believe in the beauty of their dreams."
--Eleanor Roosevelt
|
| Mon, 28 Jul 2003 22:24:38 GMT |
|
 |
|
Ken Halte
#2 / 11
|
Stand alone *.exe in VB, is it,possible? No standalone exe's in VB... All require the standard runtime files.. There are utilities that will merge all of these together to give you the illusion of standalone... but that's about it. You can use the PDW to create a setup package that can be used by all. Just
tell the users to point the installation routine to the server. That way,
only the runtime files will be installed on their system and the exe will be
on the server... Once this is done by one person, the setup package will
detect the presence of the exe in the target folder and skip over it (since
it's already there)... making everything after the first server install go
quickly.
BTW... there really is no such thing as a standalone Windows exe... They all
require runtime files... C++ people are just lucky enough to have the
runtimes already installed on everyones' system.
Quote: > Hi, VB Maniacs- > I'm trying to install a VB application on the network where many users
will
> have the ability to access it. The problem I have with this is how do I
> create a stand alone executable. I've never done this before. Please, let
me
> know of how I can do that if it's possible or perhaps point me into the
> right direction. Any help will be very much appreciated.
> Sultan
> --
> "The future belongs to those who believe in the beauty of their dreams."
> --Eleanor Roosevelt
|
| Mon, 28 Jul 2003 23:23:26 GMT |
|
|
|
Mike
#3 / 11
|
Stand alone *.exe in VB, is it,possible?
Quote: > Hi, VB Maniacs- > I'm trying to install a VB application on the network where many users
will
> have the ability to access it. The problem I have with this is how do I
> create a stand alone executable. I've never done this before. Please, let
me
> know of how I can do that if it's possible or perhaps point me into the
> right direction. Any help will be very much appreciated.
> Sultan
In short, I don't think you can. Even the most basic VB programs need the MSVBVMnn.DLL to be installed on the running machine. (where nn is the version number) There are packages that claim to be able to create a standalone executable from a VB program. But in my experience they create a very large .exe and still need the MSVBVMnn.DLL file to be installed. You could try C++ instead, all windows machines have the visual C run time library installed. Or Delphi, this can create stand alone executables. Hth Mikey :o)
|
| Mon, 28 Jul 2003 23:29:42 GMT |
|
|
|
Sulta
#4 / 11
|
Stand alone *.exe in VB, is it,possible? Ken and Mike - I do appreciate both of your replies very much. My thought was pretty much
the same as your replies but I also thought maybe there is another way
around the problem. Allow me to explain:
If I programmatically include code on the executable to look for certain
runtime errors like some .OCX or .DLL file is missing and from these kind of
errors respond by copying the missing files from a directory on the network
down to the appropriate directories on their hard drive. It sounds possible
to do. Am I getting myself into trouble that isn't worth the time and
effort? I welcome all suggestions.
Sultan
--
"The future belongs to those who believe in the beauty of their dreams."
--Eleanor Roosevelt
Quote: > No standalone exe's in VB... All require the standard runtime files.. There > are utilities that will merge all of these together to give you the illusion > of standalone... but that's about it. > You can use the PDW to create a setup package that can be used by all.
Just
> tell the users to point the installation routine to the server. That way,
> only the runtime files will be installed on their system and the exe will
be
> on the server... Once this is done by one person, the setup package will
> detect the presence of the exe in the target folder and skip over it
(since
> it's already there)... making everything after the first server install go
> quickly.
> BTW... there really is no such thing as a standalone Windows exe... They
all
> require runtime files... C++ people are just lucky enough to have the
> runtimes already installed on everyones' system.
> > Hi, VB Maniacs-
> > I'm trying to install a VB application on the network where many users
> will
> > have the ability to access it. The problem I have with this is how do I
> > create a stand alone executable. I've never done this before. Please,
let
> me
> > know of how I can do that if it's possible or perhaps point me into the
> > right direction. Any help will be very much appreciated.
> > Sultan
> > --
> > "The future belongs to those who believe in the beauty of their dreams."
> > --Eleanor Roosevelt
|
| Tue, 29 Jul 2003 00:03:44 GMT |
|
|
|
Ken Halte
#5 / 11
|
Stand alone *.exe in VB, is it,possible? Actually, these dll's and ocx's can stay on the server... the registry will point to them there.. It's hard to imagine why... after a successful install, there would be any missing files... It's always a good idea to include error traps that can detect missing
parts... but I just throw up a message box that says something like "run
setup again"... which.. in my case.. is what they'll have to do. Haven't
heard any complaints..
Quote: > Ken and Mike - > I do appreciate both of your replies very much. My thought was pretty much
> the same as your replies but I also thought maybe there is another way
> around the problem. Allow me to explain:
> If I programmatically include code on the executable to look for certain
> runtime errors like some .OCX or .DLL file is missing and from these kind
of
> errors respond by copying the missing files from a directory on the
network
> down to the appropriate directories on their hard drive. It sounds
possible
> to do. Am I getting myself into trouble that isn't worth the time and
> effort? I welcome all suggestions.
> Sultan
> --
> "The future belongs to those who believe in the beauty of their dreams."
> --Eleanor Roosevelt
|
| Tue, 29 Jul 2003 00:31:18 GMT |
|
|
|
Mike
#6 / 11
|
Stand alone *.exe in VB, is it,possible? The problem is that the executable will never get that far, the first thing the program will do is check its dependancies, before any of your coding is processed. In short it will abort before you can cater for any errors. Mikey :o)
Quote: > Ken and Mike - > I do appreciate both of your replies very much. My thought was pretty much
> the same as your replies but I also thought maybe there is another way
> around the problem. Allow me to explain:
> If I programmatically include code on the executable to look for certain
> runtime errors like some .OCX or .DLL file is missing and from these kind
of
> errors respond by copying the missing files from a directory on the
network
> down to the appropriate directories on their hard drive. It sounds
possible
> to do. Am I getting myself into trouble that isn't worth the time and
> effort? I welcome all suggestions.
> Sultan
> --
> "The future belongs to those who believe in the beauty of their dreams."
> --Eleanor Roosevelt
> > No standalone exe's in VB... All require the standard runtime files..
> There
> > are utilities that will merge all of these together to give you the
> illusion
> > of standalone... but that's about it.
> > You can use the PDW to create a setup package that can be used by all.
> Just
> > tell the users to point the installation routine to the server. That
way,
> > only the runtime files will be installed on their system and the exe
will
> be
> > on the server... Once this is done by one person, the setup package will
> > detect the presence of the exe in the target folder and skip over it
> (since
> > it's already there)... making everything after the first server install
go
> > quickly.
> > BTW... there really is no such thing as a standalone Windows exe... They
> all
> > require runtime files... C++ people are just lucky enough to have the
> > runtimes already installed on everyones' system.
> > > Hi, VB Maniacs-
> > > I'm trying to install a VB application on the network where many users
> > will
> > > have the ability to access it. The problem I have with this is how do
I
> > > create a stand alone executable. I've never done this before. Please,
> let
> > me
> > > know of how I can do that if it's possible or perhaps point me into
the
> > > right direction. Any help will be very much appreciated.
> > > Sultan
> > > --
> > > "The future belongs to those who believe in the beauty of their
dreams."
> > > --Eleanor Roosevelt
|
| Tue, 29 Jul 2003 00:40:14 GMT |
|
|
|
Ken Halte
#7 / 11
|
Stand alone *.exe in VB, is it,possible? That may be true for the VB runtime files... but if you're creating instances of DLL's, the program won't fail until you try to "Set obj = missing_class". You can trap that..
Quote: > The problem is that the executable will never get that far, the first thing > the program will do is check its dependancies, before any of your coding > is processed. In short it will abort before you can cater for any errors. > Mikey :o)
> > Ken and Mike -
> > I do appreciate both of your replies very much. My thought was pretty
much
> > the same as your replies but I also thought maybe there is another way
> > around the problem. Allow me to explain:
> > If I programmatically include code on the executable to look for certain
> > runtime errors like some .OCX or .DLL file is missing and from these
kind
> of
> > errors respond by copying the missing files from a directory on the
> network
> > down to the appropriate directories on their hard drive. It sounds
> possible
> > to do. Am I getting myself into trouble that isn't worth the time and
> > effort? I welcome all suggestions.
> > Sultan
> > --
> > "The future belongs to those who believe in the beauty of their dreams."
> > --Eleanor Roosevelt
> > > No standalone exe's in VB... All require the standard runtime files..
> > There
> > > are utilities that will merge all of these together to give you the
> > illusion
> > > of standalone... but that's about it.
> > > You can use the PDW to create a setup package that can be used by all.
> > Just
> > > tell the users to point the installation routine to the server. That
> way,
> > > only the runtime files will be installed on their system and the exe
> will
> > be
> > > on the server... Once this is done by one person, the setup package
will
> > > detect the presence of the exe in the target folder and skip over it
> > (since
> > > it's already there)... making everything after the first server
install
> go
> > > quickly.
> > > BTW... there really is no such thing as a standalone Windows exe...
They
> > all
> > > require runtime files... C++ people are just lucky enough to have the
> > > runtimes already installed on everyones' system.
> > > > Hi, VB Maniacs-
> > > > I'm trying to install a VB application on the network where many
users
> > > will
> > > > have the ability to access it. The problem I have with this is how
do
> I
> > > > create a stand alone executable. I've never done this before.
Please,
> > let
> > > me
> > > > know of how I can do that if it's possible or perhaps point me into
> the
> > > > right direction. Any help will be very much appreciated.
> > > > Sultan
> > > > --
> > > > "The future belongs to those who believe in the beauty of their
> dreams."
> > > > --Eleanor Roosevelt
|
| Tue, 29 Jul 2003 01:26:19 GMT |
|
|
|
Sulta
#8 / 11
|
Stand alone *.exe in VB, is it,possible? From what I understand so far, the .exe when run it looks for dependencies first. If that's the case, then what I'm trying to accomplish is impossible. Am I right? Sultan
--
"The future belongs to those who believe in the beauty of their dreams."
--Eleanor Roosevelt
Quote: > That may be true for the VB runtime files... but if you're creating > instances of DLL's, the program won't fail until you try to "Set obj = > missing_class". You can trap that..
> > The problem is that the executable will never get that far, the first
> thing
> > the program will do is check its dependancies, before any of your coding
> > is processed. In short it will abort before you can cater for any
errors.
> > Mikey :o)
> > > Ken and Mike -
> > > I do appreciate both of your replies very much. My thought was pretty
> much
> > > the same as your replies but I also thought maybe there is another way
> > > around the problem. Allow me to explain:
> > > If I programmatically include code on the executable to look for
certain
> > > runtime errors like some .OCX or .DLL file is missing and from these
> kind
> > of
> > > errors respond by copying the missing files from a directory on the
> > network
> > > down to the appropriate directories on their hard drive. It sounds
> > possible
> > > to do. Am I getting myself into trouble that isn't worth the time and
> > > effort? I welcome all suggestions.
> > > Sultan
> > > --
> > > "The future belongs to those who believe in the beauty of their
dreams."
> > > --Eleanor Roosevelt
> > > > No standalone exe's in VB... All require the standard runtime
files..
> > > There
> > > > are utilities that will merge all of these together to give you the
> > > illusion
> > > > of standalone... but that's about it.
> > > > You can use the PDW to create a setup package that can be used by
all.
> > > Just
> > > > tell the users to point the installation routine to the server. That
> > way,
> > > > only the runtime files will be installed on their system and the exe
> > will
> > > be
> > > > on the server... Once this is done by one person, the setup package
> will
> > > > detect the presence of the exe in the target folder and skip over it
> > > (since
> > > > it's already there)... making everything after the first server
> install
> > go
> > > > quickly.
> > > > BTW... there really is no such thing as a standalone Windows exe...
> They
> > > all
> > > > require runtime files... C++ people are just lucky enough to have
the
> > > > runtimes already installed on everyones' system.
> > > > > Hi, VB Maniacs-
> > > > > I'm trying to install a VB application on the network where many
> users
> > > > will
> > > > > have the ability to access it. The problem I have with this is how
> do
> > I
> > > > > create a stand alone executable. I've never done this before.
> Please,
> > > let
> > > > me
> > > > > know of how I can do that if it's possible or perhaps point me
into
> > the
> > > > > right direction. Any help will be very much appreciated.
> > > > > Sultan
> > > > > --
> > > > > "The future belongs to those who believe in the beauty of their
> > dreams."
> > > > > --Eleanor Roosevelt
|
| Tue, 29 Jul 2003 01:47:13 GMT |
|
|
|
Ken Halte
#9 / 11
|
Stand alone *.exe in VB, is it,possible? The only dependancies that absolutely must be there is the VB runtime files... All others are loaded as needed. No advance checking is done... in fact, there's a utility that will add code to your program to do this advance checking for you.. but it doesn't check automatically... Here's the tool (if you're interested)
VersionStamper
http://www.desaware.com/VersionStamperL2.htm
Kind of pricy but if you read the description, you'll see why...
Quote: > From what I understand so far, the .exe when run it looks for dependencies > first. If that's the case, then what I'm trying to accomplish is impossible. > Am I right? > Sultan
> --
> "The future belongs to those who believe in the beauty of their dreams."
> --Eleanor Roosevelt
> > That may be true for the VB runtime files... but if you're creating
> > instances of DLL's, the program won't fail until you try to "Set obj =
> > missing_class". You can trap that..
> > > The problem is that the executable will never get that far, the first
> > thing
> > > the program will do is check its dependancies, before any of your
coding
> > > is processed. In short it will abort before you can cater for any
> errors.
> > > Mikey :o)
> > > > Ken and Mike -
> > > > I do appreciate both of your replies very much. My thought was
pretty
> > much
> > > > the same as your replies but I also thought maybe there is another
way
> > > > around the problem. Allow me to explain:
> > > > If I programmatically include code on the executable to look for
> certain
> > > > runtime errors like some .OCX or .DLL file is missing and from these
> > kind
> > > of
> > > > errors respond by copying the missing files from a directory on the
> > > network
> > > > down to the appropriate directories on their hard drive. It sounds
> > > possible
> > > > to do. Am I getting myself into trouble that isn't worth the time
and
> > > > effort? I welcome all suggestions.
> > > > Sultan
> > > > --
> > > > "The future belongs to those who believe in the beauty of their
> dreams."
> > > > --Eleanor Roosevelt
> > > > > No standalone exe's in VB... All require the standard runtime
> files..
> > > > There
> > > > > are utilities that will merge all of these together to give you
the
> > > > illusion
> > > > > of standalone... but that's about it.
> > > > > You can use the PDW to create a setup package that can be used by
> all.
> > > > Just
> > > > > tell the users to point the installation routine to the server.
That
> > > way,
> > > > > only the runtime files will be installed on their system and the
exe
> > > will
> > > > be
> > > > > on the server... Once this is done by one person, the setup
package
> > will
> > > > > detect the presence of the exe in the target folder and skip over
it
> > > > (since
> > > > > it's already there)... making everything after the first server
> > install
> > > go
> > > > > quickly.
> > > > > BTW... there really is no such thing as a standalone Windows
exe...
> > They
> > > > all
> > > > > require runtime files... C++ people are just lucky enough to have
> the
> > > > > runtimes already installed on everyones' system.
> > > > > > Hi, VB Maniacs-
> > > > > > I'm trying to install a VB application on the network where many
> > users
> > > > > will
> > > > > > have the ability to access it. The problem I have with this is
how
> > do
> > > I
> > > > > > create a stand alone executable. I've never done this before.
> > Please,
> > > > let
> > > > > me
> > > > > > know of how I can do that if it's possible or perhaps point me
> into
> > > the
> > > > > > right direction. Any help will be very much appreciated.
> > > > > > Sultan
> > > > > > --
> > > > > > "The future belongs to those who believe in the beauty of their
> > > dreams."
> > > > > > --Eleanor Roosevelt
|
| Tue, 29 Jul 2003 02:17:31 GMT |
|
|
|
Sulta
#10 / 11
|
Stand alone *.exe in VB, is it,possible? Ken, Mike, I appreciate your help very much. At least I know where I stand now. Hopefully VB 7 will have a better way to do things like this. Thanks again. Sultan
--
"The future belongs to those who believe in the beauty of their dreams."
--Eleanor Roosevelt
Quote: > The only dependancies that absolutely must be there is the VB runtime > files... > All others are loaded as needed. No advance checking is done... in fact, > there's a utility that will add code to your program to do this advance > checking for you.. but it doesn't check automatically... > Here's the tool (if you're interested)
> VersionStamper
> http://www.desaware.com/VersionStamperL2.htm
> Kind of pricy but if you read the description, you'll see why...
> > From what I understand so far, the .exe when run it looks for
dependencies
> > first. If that's the case, then what I'm trying to accomplish is
> impossible.
> > Am I right?
> > Sultan
> > --
> > "The future belongs to those who believe in the beauty of their dreams."
> > --Eleanor Roosevelt
> > > That may be true for the VB runtime files... but if you're creating
> > > instances of DLL's, the program won't fail until you try to "Set obj =
> > > missing_class". You can trap that..
> > > > The problem is that the executable will never get that far, the
first
> > > thing
> > > > the program will do is check its dependancies, before any of your
> coding
> > > > is processed. In short it will abort before you can cater for any
> > errors.
> > > > Mikey :o)
> > > > > Ken and Mike -
> > > > > I do appreciate both of your replies very much. My thought was
> pretty
> > > much
> > > > > the same as your replies but I also thought maybe there is another
> way
> > > > > around the problem. Allow me to explain:
> > > > > If I programmatically include code on the executable to look for
> > certain
> > > > > runtime errors like some .OCX or .DLL file is missing and from
these
> > > kind
> > > > of
> > > > > errors respond by copying the missing files from a directory on
the
> > > > network
> > > > > down to the appropriate directories on their hard drive. It sounds
> > > > possible
> > > > > to do. Am I getting myself into trouble that isn't worth the time
> and
> > > > > effort? I welcome all suggestions.
> > > > > Sultan
> > > > > --
> > > > > "The future belongs to those who believe in the beauty of their
> > dreams."
> > > > > --Eleanor Roosevelt
> > > > > > No standalone exe's in VB... All require the standard runtime
> > files..
> > > > > There
> > > > > > are utilities that will merge all of these together to give you
> the
> > > > > illusion
> > > > > > of standalone... but that's about it.
> > > > > > You can use the PDW to create a setup package that can be used
by
> > all.
> > > > > Just
> > > > > > tell the users to point the installation routine to the server.
> That
> > > > way,
> > > > > > only the runtime files will be installed on their system and the
> exe
> > > > will
> > > > > be
> > > > > > on the server... Once this is done by one person, the setup
> package
> > > will
> > > > > > detect the presence of the exe in the target folder and skip
over
> it
> > > > > (since
> > > > > > it's already there)... making everything after the first server
> > > install
> > > > go
> > > > > > quickly.
> > > > > > BTW... there really is no such thing as a standalone Windows
> exe...
> > > They
> > > > > all
> > > > > > require runtime files... C++ people are just lucky enough to
have
> > the
> > > > > > runtimes already installed on everyones' system.
> > > > > > > Hi, VB Maniacs-
> > > > > > > I'm trying to install a VB application on the network where
many
> > > users
> > > > > > will
> > > > > > > have the ability to access it. The problem I have with this is
> how
> > > do
> > > > I
> > > > > > > create a stand alone executable. I've never done this before.
> > > Please,
> > > > > let
> > > > > > me
> > > > > > > know of how I can do that if it's possible or perhaps point me
> > into
> > > > the
> > > > > > > right direction. Any help will be very much appreciated.
> > > > > > > Sultan
> > > > > > > --
> > > > > > > "The future belongs to those who believe in the beauty of
their
> > > > dreams."
> > > > > > > --Eleanor Roosevelt
|
| Tue, 29 Jul 2003 02:31:22 GMT |
|
|
|
Mike
#11 / 11
|
Stand alone *.exe in VB, is it,possible? You never know, it's a pain really, Delphi can do it because unless you get fancy, it uses the windows api's for its run of the mill stuff. Great really when you think that they where written by microsoft as was VB, but not Delphi!! Mikey :o)
Quote: > Ken, Mike, > I appreciate your help very much. At least I know where I stand now. > Hopefully VB 7 will have a better way to do things like this. Thanks again. > Sultan
> --
> "The future belongs to those who believe in the beauty of their dreams."
> --Eleanor Roosevelt
> > The only dependancies that absolutely must be there is the VB runtime
> > files...
> > All others are loaded as needed. No advance checking is done... in fact,
> > there's a utility that will add code to your program to do this advance
> > checking for you.. but it doesn't check automatically...
> > Here's the tool (if you're interested)
> > VersionStamper
> > http://www.desaware.com/VersionStamperL2.htm
> > Kind of pricy but if you read the description, you'll see why...
> > > From what I understand so far, the .exe when run it looks for
> dependencies
> > > first. If that's the case, then what I'm trying to accomplish is
> > impossible.
> > > Am I right?
> > > Sultan
> > > --
> > > "The future belongs to those who believe in the beauty of their
dreams."
> > > --Eleanor Roosevelt
> > > > That may be true for the VB runtime files... but if you're creating
> > > > instances of DLL's, the program won't fail until you try to "Set obj
=
> > > > missing_class". You can trap that..
> > > > > The problem is that the executable will never get that far, the
> first
> > > > thing
> > > > > the program will do is check its dependancies, before any of your
> > coding
> > > > > is processed. In short it will abort before you can cater for any
> > > errors.
> > > > > Mikey :o)
> > > > > > Ken and Mike -
> > > > > > I do appreciate both of your replies very much. My thought was
> > pretty
> > > > much
> > > > > > the same as your replies but I also thought maybe there is
another
> > way
> > > > > > around the problem. Allow me to explain:
> > > > > > If I programmatically include code on the executable to look for
> > > certain
> > > > > > runtime errors like some .OCX or .DLL file is missing and from
> these
> > > > kind
> > > > > of
> > > > > > errors respond by copying the missing files from a directory on
> the
> > > > > network
> > > > > > down to the appropriate directories on their hard drive. It
sounds
> > > > > possible
> > > > > > to do. Am I getting myself into trouble that isn't worth the
time
> > and
> > > > > > effort? I welcome all suggestions.
> > > > > > Sultan
> > > > > > --
> > > > > > "The future belongs to those who believe in the beauty of their
> > > dreams."
> > > > > > --Eleanor Roosevelt
> > > > > > > No standalone exe's in VB... All require the standard runtime
> > > files..
> > > > > > There
> > > > > > > are utilities that will merge all of these together to give
you
> > the
> > > > > > illusion
> > > > > > > of standalone... but that's about it.
> > > > > > > You can use the PDW to create a setup package that can be used
> by
> > > all.
> > > > > > Just
> > > > > > > tell the users to point the installation routine to the
server.
> > That
> > > > > way,
> > > > > > > only the runtime files will be installed on their system and
the
> > exe
> > > > > will
> > > > > > be
> > > > > > > on the server... Once this is done by one person, the setup
> > package
> > > > will
> > > > > > > detect the presence of the exe in the target folder and skip
> over
> > it
> > > > > > (since
> > > > > > > it's already there)... making everything after the first
server
> > > > install
> > > > > go
> > > > > > > quickly.
> > > > > > > BTW... there really is no such thing as a standalone Windows
> > exe...
> > > > They
> > > > > > all
> > > > > > > require runtime files... C++ people are just lucky enough to
> have
> > > the
> > > > > > > runtimes already installed on everyones' system.
> > > > > > > > Hi, VB Maniacs-
> > > > > > > > I'm trying to install a VB application on the network where
> many
> > > > users
> > > > > > > will
> > > > > > > > have the ability to access it. The problem I have with this
is
> > how
> > > > do
> > > > > I
> > > > > > > > create a stand alone executable. I've never done this
before.
> > > > Please,
> > > > > > let
> > > > > > > me
> > > > > > > > know of how I can do that if it's possible or perhaps point
me
> > > into
> > > > > the
> > > > > > > > right direction. Any help will be very much appreciated.
> > > > > > > > Sultan
> > > > > > > > --
> > > > > > > > "The future belongs to those who believe in the beauty of
> their
> > > > > dreams."
> > > > > > > > --Eleanor Roosevelt
|
| Tue, 29 Jul 2003 19:37:50 GMT |
|
| |
|
