PDF Using MFC and ATL Special Edition

Free download. Book file PDF easily for everyone and every device. You can download and read online Using MFC and ATL Special Edition file PDF Book only if you are registered here. And also you can download or read online all Book PDF file that related with Using MFC and ATL Special Edition book. Happy reading Using MFC and ATL Special Edition Bookeveryone. Download file Free Book PDF Using MFC and ATL Special Edition at Complete PDF Library. This Book have some digital formats such us :paperbook, ebook, kindle, epub, fb2 and another formats. Here is The CompletePDF Book Library. It's free to register here to get Book file PDF Using MFC and ATL Special Edition Pocket Guide.

I liked swapping and sharing programmes with my best pal who is the IT director for a mobile telephone company.

61 Best MFC Books of All Time - BookAuthority

EXE for him on to a 1. At that point as I said I really didn't see the point. Although from what we have discussed before it sounds like PowerBASIC would have been the best choice in that scenario! Last edited on Oct 26, at am UTC. Back in a Motel again and headed home soon so I can reply. Wasn't familiar with the CodeProject Tutorial but am very, very familiar with the Jeff Glatt Tutorial, which has been considered by all as ground breaking on that topic.

I'm surprised you are interested in this stuff. Not many are.

Navigation menu

I guess from my standpoint, the reason I was always interested in it, was the 'cross-language' thing. I always felt it was cool to be able to build an application out of various code building blocks where it doesn't matter if the various parts are written in different programming languages. One can only see what is going on in C. When I first started working on it my first efforts, which occupied many months of fooling around with it, were to attempt to 'dump' the memory contents of various blocks of memory to see how the various objects were constructed.

The objects consist of several different memory allocations, with member variables and virtual function table pointers in one location, and the virtual function tables which contain pointers to the member functions in other places. Given a pointer to an object, one must understand where the virtual function table pointers to the various interfaces are located, and within the COM Object itself, how to switch among them. That Tutorial 2 explains all that.

That MSFlxGrd. It took me several years of intense effort to get that far. I was greatly influenced by the work of Jose Roca on this stuff who I and many others consider to be something of a genius. It was kind of an ultimate solution, actually. Well, maybe not. Fact is, they were pretty bloated, just like everything Microsoft touches. I recall writing a major application at work, which had previously been a major mainframe application, and I had written maybe 15, lines of code. It was a database type application, where a database on a server was accessed, and the data was viewed in grids throughout the application.

That seemed out of kilter to me.

  • Translations and Alternate Editions;
  • Web Penetration Testing with Kali Linux (2nd Edition)?
  • Psychotherapy and Counseling with Older Women: Cross-Cultural, Family, and End-of-Life Issues?

At that point I wondered if I couldn't create a grid control myself that was smaller, or use something else. The 'something else' option actually is an option.

ISBN 13: 9780789707512

But there is an alternate Windows Control architecture, and that would be 'Custom Control' architecture. I moved to that and used it for many years. This occupied my best efforts for many years. As an aside, I eventually accomplished that, and my most recent version of it I have built in x64 and it is a full featured grid control and its only something like 16k!!! But to accomplish that I had to write my own C Runtime, because, like I said, Microsoft bloats everything it touches.

Get this edition

But I've posted something very similiar here couple years ago that you could run, and that would be about the same type code that utilizes the Microsoft Internet Explorer Shell. Explorer ActiveX Control. In that code I posted, if one were building with one of the old Mingw build chains, you could build a browser in about 12k or so. I'll see if I can find that link from this web site Last edited on Oct 26, at pm UTC.

Oct 26, at pm UTC. Those prerequisites would be understanding several Registry entries, and understanding function pointers. Now that we have 64 bit one needs to understand two places in the Registry where these are located. Most folks use the switch for this. That doesn't scale well though, and many of my applications involve tens of thousands of lines of code. Oct 27, at am UTC. I think it is the very intricacy which holds my attention.

I also think it is that same intricacy which leads some people to consider it 'difficult' or tricky. I have read several times now through the first Jeff Glat example and I thought I was starting to twig what was going on. But then I hit the very pothole that you mention--the fact he only includes one 'interface'. I then read again through your example Therefore, so far the main thread I have gathered from your example is the beginnings of an understanding--I stress so far , as I will need to read and re-read the material several times over to properly digest--of what is 'really going on'.

If I am putting it together correctly then I think that COM is basically a codified system of pointers to functions and ways to allocate, share and delete the underlying data they point to. That is a lot to think about and cogitate over. Last edited on Oct 27, at am UTC.

Oct 28, at pm UTC. It amazes me you like this stuff Lucian. Just so happens I do too. You must be pretty smart.


This is an amazing observation That's pretty close. I think that 2nd tutorial of mine where I do everything in C will clear it up for you. I admit its hard. But yes, every interface which is really a struct containing function pointers contains as its first three members QueryInterface , AddRef and Release. That's what inheritance means. Another ponderous way of putting it is that every interface is polymorphic in IUnknown.

Think that one over for awhile! Actually, in ObjBase. Oct 30, at am UTC. You are very kind Freddie!

I don't think I am especially smart, but I have always liked to 'know what they know' as it were and I have a genuinely evangelical passion that anyone can learn anything. Its a bit off-topic, but in my opinion nothing is actually 'hard', it is just a case of understanding the framework around the material you are trying to learn, where it fits in and more importantly why. The concept of 'emergent behaviour' applies here and also fascinates me--I have been a die-hard Trekker since the late sixties and I think emergent behaviour is a real-world example of what the Vulcans call 'IDIC'.

Anyway that is a long way away from the matter at hand! I have now gone over several times the valeriyabobko tutorial and then cross-referenced this to both your first tutorial and the Jeff Glatt material.

  1. How Successful People Think;
  2. Asterix Obelix and Co..
  3. Baltic Independence and Russian Foreign Energy Policy;
  4. MFC support in ATL project??.
  5. Rare Diseases in the Age of Health 2.0?
  6. Account Options.
  7. I think I have a pretty good grasp of 'interfaces' and how to inherit from IUnkown. I am now trying to get a similar grip on the 'Class Factory' concept. I am hoping these texts along with your tutorials, those from Glatt and valeriyabobko will cover this thing from all the angles I need! Last edited on Oct 30, at am UTC. Oct 30, at pm UTC. Symetry exists between the concepts of 'emergence' and 'reduction'. Emergent phenenomen can't be 'reduced' to its constituents.

    For example, there is nothing one can learn about hydrogen atoms or oxygen atoms that would be useful in predicting the qualities of water.


    Special Edition Using Mfc and Atl

    The qualities of water are emergent. I haven't tried that yet Thanks Jonas, that looks promising. I was using the redist from the website but I have SP1 on my development machine so I'll try the updated version. Jay, is there a reason you are trying to do this? I've tried both the debug and release builds I understand the redist doesn't include the debug libs. Note that the redistributable above may not run applications compiled in Visual Studio Service Pack 1 as such executables want slightly revised versions of the runtime DLL's. It took us some while here to figure that out and thought it wasn't well documented.

    This is correct.

    • Translations and Alternate Editions.
    • Special Edition Using Mfc and Atl - Ebooks.
    • Brills companion to Roman tragedy.
    • Using MFC and ATL / written by Clayton Walnum, with Paul Robichaux. - Version details - Trove?
    • Prostate Biopsy: Indications, Techniques, and Complications?
    • KickAss Delphi Programming: Cutting-edge Delphi Programming with an Attitude!

    This is not new policy for VS Bob, I think you have a different issue. Perhaps start another discussion on this. Please be specific in description of your build environment and mention what versions of VS you have installed. I thought Manifests were an end to DLL hell - but it just seems that now we have manifest hell.