Re: Updating the VB EXE
- From: "Nobody" <nobody@xxxxxxxxxx>
- Date: Wed, 7 Oct 2009 12:09:27 -0400
"Rick Raisley" <heavymetal-A-T-bellsouth-D-O-Tnet> wrote in message
news:e2qEnD1RKHA.220@xxxxxxxxxxxxxxxxxxxxxxx
"Nobody" <nobody@xxxxxxxxxx> wrote in message
news:%23dMwcrzRKHA.1796@xxxxxxxxxxxxxxxxxxxxxxx
I already tried it on Windows 2000. I renamed a copy of MSPAINT.EXE while
it's open, and it was successful. I then tried to delete the file, and
Windows wouldn't let me. So the file is open somehow.
Interesting. I didn't know that either. Sure enough, I ran a VB program
I'd compiled, and of course, I cannot delete the EXE while it's running.
And I can't copy of the EXE while it's running, as that amounts to a
Delete and copy.
I assume that you meant "move" instead of "copy". Move implies deleting the
original, which can't be done while the file is in use.
But I CAN Rename the exe that is running, the copy the newer version to
the exe's original name. All that's left is to deleted the renamed
original after the program ends.
I'll definitely have to consider that in my next updating procedure. ;-)
Yes, that's how the article suggests doing it. Also, you don't have to keep
the .exe extension. You can rename it to "old.tmp", and this won't effect
the running program.
.
- Follow-Ups:
- Re: Updating the VB EXE
- From: Rick Raisley
- Re: Updating the VB EXE
- References:
- Updating the VB EXE
- From: Tony Toews [MVP]
- Re: Updating the VB EXE
- From: Michel Posseth [MCP]
- Re: Updating the VB EXE
- From: Eduardo
- Re: Updating the VB EXE
- From: Nobody
- Re: Updating the VB EXE
- From: Eduardo
- Re: Updating the VB EXE
- From: Nobody
- Re: Updating the VB EXE
- From: Rick Raisley
- Updating the VB EXE
- Prev by Date: Re: Statusbar
- Next by Date: Re: VB6/Distinct Intelliterm screen scraping/painting
- Previous by thread: Re: Updating the VB EXE
- Next by thread: Re: Updating the VB EXE
- Index(es):
Relevant Pages
|