Re: Custom Resource
- From: "Igor Tandetnik" <itandetnik@xxxxxxxx>
- Date: Tue, 30 Jan 2007 00:23:58 -0500
"Saul775" <Saul775@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EC49984D-F207-4A95-B89B-623FC78EBAB8@xxxxxxxxxxxxx
Just a quick question. I've an application that I would like to
store some information about various settings current to the
application. However, I'd like to store the settings to the .EXE if
possible.
You can't write to the EXE while that EXE is running. In other words, an
application cannot write into its own executable file. You could, in
principle, create a second executable whose only job is to write the
data into the first one when it shuts down.
Further, it is more and more common for an application to be installed
in a directory an ordinary user has a read-only access to. With Vista
this is the behavior out of the box. An application thus installed won't
be able to modify its executable file either.
All in all, this is a bad idea, in my humble opinion. I suggest you
investigate alternatives.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
.
- Prev by Date: Re: CComPtr::Release
- Next by Date: Re: slow debugging in visual c++ 6.0
- Previous by thread: CreateWindowEx returns 0, but GetLastError reveals no error
- Next by thread: Visual C++ on Linux
- Index(es):
Relevant Pages
|
