You can ignore the custom midl attributes, they are benign.
(They are the version (in binary form), the time and date the midl compiler was run to generate the tlb file (also in binary form), and a string providing the same information.)
So, the answer to:
|is this [these attributes] causing above problem??|
And stdole32.tlb and stdole2.tlb turn up all the time, so they're not the problem (if they were missing, a lot of things would go wrong!)
I have downloaded and built and run the demo project from the tutorial you mention. I had to "hack" the code a little bit to get it to work, but it ran OK for me. (VC++ 2010 wouldn't load the original .dsp files, so I had to recreate the project, and added some pointless .cpp files)
you add the folder where your copy of addobj.dll is located to the include path for the VCClient project? (I had to do that to get it to build)
PS I am not esp. impressed with this tutorial :-/ Esp. as it didn't build until I tweaked the code (issing files, incorrect class name, etc)