I use MTA; Still the same issue. BTW, since the thread created by library function doesn't initialize COM, in my server callback I do a CoInitializeEx to COINIT_MULTITHREADED. From this callback when I try calling Fire_XXX (in the original server object, which is passed via a context param), I still get 8001010e.
Will creating a CWorkerThread/IWorkerThreadClient based thread automatically assume its parent thread COM context?
Yes, Fire_xxx() events work correctly as long as they are called in the correct context.
BTW, I am trying out my good old GIT solution -- only this time I am going to store the sink interfaces in GIT and store the cookie in my vector...I am currently putting together a custom IConnectionPointImpl<> to store/retrieve things properly with out breaking anything;
Custom implementation of IConnectionPointImpl<> to make use of GIT worked like a charm!
I'd seriously advise anyone stuck in a similar situation to try out this trick -- do let me know if you need my implementation (I think it shouldnt be a problem sharing my code, as it doesnt have any project specific details in it!)
Is it possible to have a 32bit client initialize/invoke methods in a 64bit local COM server? If yes, how do I set up the Proxy/stub DLLs? The target OS I have in mind is Vista64 or Win7-64 (so the 32bit client will be running from with in WOW64).
Also, can I go ahead with ATL 8 for implementing the above scenario? Any examples available online? Thanks.
I did a quick check using ATLDUCK sample. Built the atlduck (local com server) in to 64bit, tried connecting to it from duck (32bit). CoCreateInstance worked perfectly, but when duck tried an Advise() to atlduck, it crashed with an error msg "runtime terminated the app" ... trying out some more experiments, will update on the results.
Pk, I am stuck with the error - "duck.exe - An application has requested the Runtime to terminate it in an unusual way". This error comes up whenever the client tries to do an Advise(). I remember seeing this issue in XP (during the VS.NET 2002 days) by installing an hotfix...but, my current testbed is Win7-64..any ideas why this error is coming?
BTW, are there any samples available that do this kind of 32 => 64 => 32bit calls/event_triggers? I am not able to find any (or prob I miss the key words in my search! )...Thanks.
We have one library which is implemented by using STLPort.There is one application which wants to use this library and this application is using microsift STL.
Is there any way by which we can use both microsoft STL and STLPort in same project?
But before going in to this step,I am getting one more porblem.
I am trying to compile my library with "Visual studio 8" first time and it is giving some errors
related to stlport.I found the reason on net that current version of STLport on my system is not compatible with VC++ 8.0 version.
I tried to take the latest version from STLport.org but I am not finding the way by which I can build
stlport library from it.
Could you please help me?
Downloading it and unpacking it reveals a configure.bat file, which you'll use to tell it what options to build into STLport. That builds a makefile which (as the configure script tells you) you use by going to build/lib folder and type "nmake clean install" to build and install STLport to the "lib" and "bin" folders.
Seems simple enough to me...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
Last Visit: 31-Dec-99 18:00 Last Update: 30-Sep-23 7:35