ATL / WTL / STL

Rob Caldecott14-Dec-05 11:38

Rob Caldecott

14-Dec-05 11:38

Jörgen Sigvardsson wrote:
I don't see how boost comes into the picture..?

Boost has different jam configs when building for VC + STLPort, so I think it must be relevanr somehow...

The Rob Blog
Google Talk: robert.caldecott

Nemanja Trifunovic15-Dec-05 1:47

15-Dec-05 1:47

Jörgen Sigvardsson wrote:
It's also a pain because you'd have to put the DLL next to your binary. You never know which app will overwrite that file.

What do you mean by this?

My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.

Jörgen Sigvardsson15-Dec-05 3:24

Jörgen Sigvardsson

15-Dec-05 3:24

If you rebuild the crt dll, and install it in say Windows\System32, it could be overwritten by another program. Overwritten with the "original" crt dll which has the memory leaks.

If you put the dll alongside the binary, the chances of another application overwriting it is virtually zero. Smile | :)

--
Pictures[^] from my Japan trip.

Nemanja Trifunovic15-Dec-05 4:41

15-Dec-05 4:41

Jörgen Sigvardsson wrote:
If you rebuild the crt dll, and install it in say Windows\System32,

Shudder. Never even cross my mind to install anything in System32, but you are right - many people actually do that

My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.

Jörgen Sigvardsson15-Dec-05 4:59

Jörgen Sigvardsson

15-Dec-05 4:59

Uh huh. I've stopped doing that as well. It used to be "correct practice" once I believe, but it's just asking for headaches. I do DLLs only these days, but I put them side by side with the executable. It won't be much better than .libs from an optimization point of view (shared code, etc). But it is easier from a maintainence point of view, as I only have to patch affected DLLs, and not the entire app.

Another great benefit with DLLs is that it's very easy to debug code on site, as it's just a matter of replacing the DLLs which contains TRACE messages, and/or similar debugging I/O.

I like DLLs. Does it show? Smile | :)

--
Pictures[^] from my Japan trip.

Nemanja Trifunovic15-Dec-05 7:19

15-Dec-05 7:19

Jörgen Sigvardsson wrote:
I like DLLs

Me too. Although it wouldn't hurt if we got some standard C++ module/component system on top of them. The .NET component system is one of the rare things where .NET is really a better development environment than C++. I know there is COM, but a) it is bloated and b) it is not portable.

My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.

Stuart Dootson14-Dec-05 21:42

Stuart Dootson

14-Dec-05 21:42

I'd ask on the Boost Users mailing list - that's probably more likely to get a useful (or at least definitive) reply...

Nemanja Trifunovic15-Dec-05 1:56

15-Dec-05 1:56

Robert Edward Caldecott wrote:
The fix is to rebuild the MSVCRT80.DLL, which is a major undertaking and, IMHO, not worth the pain.

Apparently, there is another "unofficial" way: Look at the third reply from the bottom of this page:[^]

Steps:

1) Open up istream in \Program Files\Microsoft Visual Studio 8\VC\Include
2) Before line 29, insert the following code

explicit __CLR_OR_THIS_CALL basic_istream(_Mysb *_Strbuf, bool _Isstd, bool _Noinit)
: _Chcount(0)
{ // construct from stream buffer pointer
if (!_Noinit)
_Myios::init(_Strbuf, _Isstd);
}

3) In the same file (istream), look for the following line:

: basic_istream<_Elem, _Traits>(_Strbuf, false),

and change it to:

: basic_istream<_Elem, _Traits>(_Strbuf, false, true),

My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.

How to pass Structures/Types as parameters in COM DLL function?

Rob Caldecott15-Dec-05 2:18

Rob Caldecott

15-Dec-05 2:18

Much appreciated Nemanja.

The Rob Blog
Google Talk: robert.caldecott

karnav zaveri11-Dec-05 20:30

karnav zaveri

11-Dec-05 20:30

Hi all,

Does aNy body know how we can pass strucutres ( types in VB ) as parameters of function defined in COM DLL interface ?

For e.g. I have one interface called IDatabase and i want to add method like
"HRESULT SetData([in]USER userData)".
In this case the DLL is compiled successfully, but when it is used in the Visual Basic, it gives error
"user defined object can not be passed by value". The DLL should be used in both VB and VC++ client applicaitons.

Karnav Zaveri

Re: How to pass Structures/Types as parameters in COM DLL function?

Starick11-Dec-05 22:09

Starick

11-Dec-05 22:09

It's not a simple task to pass structures in COM/DCOM.
1. A structure must be of the type VT_RECORD.
2. All the structure's fields must be of an automation-compatible type.
3. The structure must be described in a TLB.
4. The structure must have a GUID (assigned in the IDL file).
5. A special structure-oriented interface IRecordInfo must be used to manipulate structures (IRecordInfo::RecordCreate(), IRecordInfo::RecordDestroy(), etc.).

RogueWave ToolsVC?

Ed K9-Dec-05 5:11

Ed K

9-Dec-05 5:11

Anyone use this product? If so, did you update it for VC7+? If so...I need to talk to you! Big Grin | :-D

ed

~"Watch your thoughts; they become your words. Watch your words they become your actions.
Watch your actions; they become your habits. Watch your habits; they become your character.
Watch your character; it becomes your destiny."
-Frank Outlaw.

atlbase.h line 758 assertion failed

hardworkboy7-Dec-05 21:59

hardworkboy

7-Dec-05 21:59

Dear all,

I am new to ATL COM programming and the question may be silly, but pls help.

In the COM, I have defined one Simple Object Add with the inferface IAdd. Then in the client program I try to get the COM interface using following:

CComPtr<iadd> pAdd;
HRESULT hr = pAdd.CoCreateInstance(CLSID_Add);
here got problem, the following ASSERT failed;
ASSERT(hr==S_OK);

Then I define the connection Container pointer,

IConnectionPointContainer * pCPC;
hr = pAdd->QueryInterface(IID_IConnectionPointContainer, (void **) &pCPC;

Then I got the assertion failure again and it is atlbase.h line 758 assertion failed.

The program is quite simple, but I just don't know where is the problem. Please help! Cry | :((

Lim Bio Liong7-Dec-05 22:29

Lim Bio Liong

7-Dec-05 22:29

Hello hardworkboy,

The assertion failure after the call to CoCreateInstance() could be due to one of many reasons. It is important at this stage to determine what is the value of "hr". We can then proceed to diagnose the problem.

Best Regards,
Bio.

hardworkboy12-Dec-05 21:02

hardworkboy

12-Dec-05 21:02

Dear Bio Liong,

Thank you for your reply.
The hr value is -2147221008. Actually I am using WCE ATL COM AppWizard to create a COM. Then on the class view panel, I "New ATL Object", then I got the interface like "IAdd". In the testing program, I write the following:

CComPtr<iadd> pAdd;
hr = pAdd.CoCreateInstance(CLSID_Add);

here I got the problem.

I am quite unfamiliar with COM creation with ATL. So I may make silly mistakes. I am sorry for that.

Sincerely,
HWB

HWB

Steve S12-Dec-05 21:23

Steve S

12-Dec-05 21:23

You haven't called CoInitialize for the thread making the call to CoCreateInstance.
If anyone here says they've never made that mistake, I wouldn't necessaraily believe them...

Steve S
Developer for hire

Lim Bio Liong12-Dec-05 21:50

Lim Bio Liong

12-Dec-05 21:50

Hello hardworkboy,

I'm echoing Steve. Yes, the error indicates that CoInitialize() has not been called in the thread that invoked "pAdd.CoCreateInstance(CLSID_Add);".

You can easily determine the meanings of HRESULT error codes using the "Error Lookup" tool (this is included in the "Tools" menu of Visual Studio).

By the way, it is important to call CoInitialize() as it determines the apartment in which the calling thread will live in throughout its lifetime. Every thread in an application needs to reside in an apartment.

Apartments are used to control cross-thread access to COM objects.

Best Regards,
Bio.

Jörgen Sigvardsson13-Dec-05 11:34

Jörgen Sigvardsson

13-Dec-05 11:34

I would also like to point out that you should look at HRESULT values in hexadecimal format. That way they will be much easier to remember, trust me on that one! (But then again, I think that when you start to recognize the HRESULT values by heart, you're probably way too deep into it Blush | :O

)

--
Pictures[^] from my Japan trip.

hardworkboy13-Dec-05 14:52

hardworkboy

13-Dec-05 14:52

Thank you, all! Blush | :O

I have add the CoInitialize(NULL) function but this time I got the LNK2019 error which complains __Imp_Coinitialize unreolved symbol. I have tried to add the "Ole32.lib" and the "Objbase.h", still got the same link error.

I am sorry I still need your help.