Adobe has a wide range of products, including Photoshop, Premiere, Acrobat,
Acrobat Reader, the Flash suite, Audition, etc. I strongly doubt that
_any_ of those products use .NET in any significant way. It might be used
in an installer or some "dashboard/launcher" style application, but in the
primary code of any those products? Not very likely at all.
As far as recognizing the use of .NET goes, you can use something like the
SysInternals Process Explorer utility, which will show you lots of details
about running processes, including what DLLs are loaded. But without
attaching a debugger and/or using other specialized disassembly tools, you
will not get detailed information about how those DLLs are actually being
Note that at least some commercial programs attempt to limit the use of
debuggers, by detecting their presence and disabling features or refusing
to run outright if one's attached.
Finally, there is of course the question of copyright. The Adobe
implementations of the features you are asking about are almost certainly
protected by copyright. At best, inspecting Adobe's implementation is
valuable to you as a learning exercise, and frankly I think a much better
learning exercise would be for you to study the _behavior_ of the features,
and figure out how to implement them yourself from scratch.
I think you are also a lot less likely to cross the line between legal and
illegal activities as well. There is a whole body of case law addressing
the question of how much reverse-engineering and study of someone else's
technology you can do without violating copyright, so you really need a
lawyer to navigate that area. But in practice it seems to me most people
follow "clean-room" strategies, because otherwise it is very difficult to
prove you did not just lift the technology outright.