Do I still need to know COM/ATL?

[M]

I'm new to .NET/C# and I've been programming C# for a month or so now.

I'm not a C++ programmer, but I like knowing how stuff works, so I started
reading a C++/COM/ATL book.

I got about halfway through it before I started doing C#, and now I'm
wondering why I should ever learn COM/ATL.

Any reasons for me to tackle that hog? In other words, why should I ever
write new code in COM/C++? Are there specific reasons I should know this
stuff, other than for legacy code?

 

[Arjen Stins]

I'm new to .NET/C# and I've been programming C# for a month or so now.

I'm not a C++ programmer, but I like knowing how stuff works, so I started
reading a C++/COM/ATL book.

I got about halfway through it before I started doing C#, and now I'm
wondering why I should ever learn COM/ATL.

Any reasons for me to tackle that hog? In other words, why should I ever
write new code in COM/C++? Are there specific reasons I should know this
stuff, other than for legacy code?

 

[Arjen Stins]

Hi,

It helps to know several techniques to build functionality. You don't have
to know it in detail, but when the right job comes along you know which
technique you should apply best..
If you only know how to work with a hammer, it's likely to treat every
problem as if it were a nails.

Most of the time I don't need win32 api's, but sometimes I use them if there
are no simpler substitutes. Currently I'm building a filter for DirectX
sound. It's done with C++/COM (never thought I would be using it though).

TYI