ATL / WTL / STL

2-Jun-04 3:55

at a quick glance, the error 0x000045a - "A dynamic link library (DLL) initialization routine failed" is probably
caused by differences in a DLL's version (methods, behaviour) between win98 and win2000. When compiling on win2000,
the compile initialization routines may be calling entry points
that are not in the older win98 version of the DLL in
question.

You may want to create an installation program (setup.exe)
with a tool (like installshield or wise or whatever) when
moving from a newer OS to an older OS. these install
programs identify the required versions of the needed
dlls and prompts you to install them during running
og the setup.exe program.

hope this helps at least a little bit.

sas

shell programming

sas22221-Jun-04 8:56

1-Jun-04 8:56

what is the preferred way to share instantiations between
different "instances" of the explorer shell (explorer.exe)?

I have read the Dunn articles on shell programming and
can't seem to share object instantiations between
explorer.exe "instances".

I have a ATL created shell extension that implements the
context menu interfaces and in a single instance
of the explorer, the code works fine;

If i fire up a second instance of explorer.exe
from the start task bar, and right click
on a file, the code crashes, and the debugger
takes me to the windows malloc.c src file.

my memory model is such that I keep instantiated objects in
the main application object (derived from public CWinApp),
and want to use these objects from the new instances
of the coclass that implements the IShellExtInit interfaces.
I have used the SHGetMalloc call to get an IMalloc interface
and use that for my mallocs.

one of the objects is a iDispatch class generated from
a typlib via the class wizard.. other classes are straight C++
impl classes that hold session data.

--

Any help is appreciated!

-

steves

sas

Prakash Nadar2-Jun-04 7:10

Prakash Nadar

2-Jun-04 7:10

From my experince on shell extension you should never initialise anything during InitInstance or thread attach/detach calls.

All initialization should be in the IShellExtInit interface implementation only.

The call to initinstance is very unpredictable and should not be used to initialise internal data.

For example, When the dll it registered, at that time too initinstance is called, and your design could fail if you are assumeing that initinstance is called due to loading of dll by explorer.

I'll write a suicide note on a hundred dollar bill - Dire Straits

sas22222-Jun-04 7:33

2-Jun-04 7:33

thanks for the reply.

THe IshellExitInit initialize method is called each time
the file's context menu is displayed;

At the very least, I need to to persist certain data in memory
across context menu invocations (which works, btw).

best case
scenario is when I can persist data in memory across
invocations of the explorer.exe
(which I can't get working yet)

Has anyone had experience with doing the above, short
of serializing and deserializing at every menu
IshellExitInit::initialize call?

sas

Prakash Nadar2-Jun-04 15:49

Prakash Nadar

2-Jun-04 15:49

Are you tring to presist interface pointer(s) across different instance of the explorer ?

I'll write a suicide note on a hundred dollar bill - Dire Straits

sas22223-Jun-04 6:07

3-Jun-04 6:07

thanks again for the help.

I'm trying to persist instations of
native contructs (like stl maps)
and a straight C++ class instantations across
different "instances" of explorer.exe. by "instances"
of explorer.exe I mean invocations from the start menu
(looking in the task manager process table; there is only
one explorer.exe process however).

from what i understand, IShellExtInit releated coclass
gets created every time the user right clicks on a
file name (bringing up the context menu). I want these
instances of the coclass to be able to access
my instantiations of my straight C++ class
that lives at the app level (CWinApp dervied class).

i'm pretty sure my problem is memory related;

--

is there a good description on how the shell works
when executing a new isntance of the explorer?
It appearsthat the Esposito Shell programming book
is out of print; this book probably has good info in it.

--

any info is further appreciated.

sas

Debugging ATL control

roel_1-Jun-04 5:01

1-Jun-04 5:01

Hi,

I'm writing my first ATL control that will be used inside an HTML page. I used the project wizard to create a simple control, I build it and tested it in the ActiveX test container. Now I want to start making my own changes and stepping through the code a bit to see how it works. How can I test a control and set breakpoints in the Visual Studio debugger so that it stops at that point, just like a 'normal' program? Thanks.

roel_1-Jun-04 5:15

1-Jun-04 5:15

Never mind, I found it (found an article on how to debug a service, it's the same for an activex control): Tools->Debug processes, attach to tstcon32 process.

Jörgen Sigvardsson1-Jun-04 8:49

Jörgen Sigvardsson

1-Jun-04 8:49

You can also for a break point using __asm int 3. That'll halt the program and show you the "program has crashed dialog, do you wish to debug?"-dialog. From there you can attach to the program which embeds your control.

--
Booohoo!

roel_2-Jun-04 4:26

2-Jun-04 4:26

Aha, I didn't know I could do that from an ActiveX control as well. Thanks!

_Magnus_2-Jun-04 2:05

_Magnus_

2-Jun-04 2:05

Or set the tstcon32 as the executable for the debugsession.

/Magnus

- I don't necessarily agree with everything I say

roel_2-Jun-04 4:27