CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums
Results 1 to 3 of 3
  1. #1
    Join Date
    May 1999

    Is DCOM still viable?

    I'm finishing off a degree, and the last credits I have outstanding involve a "real world" client/server project. I was hoping to base the architecture on DCOM, using components crafted in ATL 7, but I have concerns about obsolescence.

    Anyone have any thoughts? Is it possible to implement Web services in DCOM and ATL 7 (I'm a total noob here)? Or is DCOM toast, meaning I should use .NET instead?

    Any suggestions are appreciated.

    Thanks, RD

  2. #2
    Join Date
    Feb 2002
    Learn COM/DCOM, but focus on .NET. No matter what developer say, I still think COM/DCOM is Visual Basic oriented.


  3. #3
    Join Date
    Jan 2002
    Scaro, UK
    In my experience DCOM had far too many problems to ever make it a viable way of communicating over a network (the setup was horrible - especially getting the permissions right, didn't work across domains, single threaded DCOM servers could hang infinitely etc etc).

    I think Microsoft has given up and stopped supporting it now.

    I would have expected the .NET way would be much better. Or using raw sockets (which is what I use).

    Socket servers aren't that difficult to write, and much much more stable.

    Darwen. - PInvoker - the .NET PInvoke Interface Exporter for C++ Dlls.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Click Here to Expand Forum to Full Width