Home/ Questions/Q 898005
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T14:58:21+00:00

I’m about to begin working on a Accessibility project for Windows (targeting XP through

  • 0

I’m about to begin working on a Accessibility project for Windows (targeting XP through 7) and would like some advice on the pros an cons of using managed code vs unmanaged code. Basically the software will need to be able to read text from open windows, access menus, and other common functions programs like a JAWS or another screen reader would be able to do. The question is, can I do this with C# or do I need to use C++?

For the last two years I’ve been developing a lot of C# code so it seems the quickest way to get started would be to play around with the System.Windows.Automation namespace. On the other hand, I haven’t done much C++ or COM programming in quite a while and would have to spend some time refreshing before using unmanaged code.

What are the limitations of using C# code for Accessibility software? Are they severe enough to justify putting in a fair amount of time to refresh my C++ and COM skills because I’d run into a lot of things that just wouldn’t be possible (or much more difficult) with managed code? Is the Automation namespace compatible with older applications (not using .NET or WPF)?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Definitely managed code

    Even if you run into situations where you’re comfortable using COM/unmanaged you can use COM/unmanaged for those modules.

    .NET offers seamless interop between managed and unmanaged code.
    with .NET 4.0 and C# 4.0 interop is even better ..

    And above all else make sure you design a loosely coupled system so that there’s always room for plugging in another module in an entirely different technology..

    Just my two cents..

    • 0