Home/ Questions/Q 659461
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T23:02:49+00:00

We use an open source library written in C# wrapping Windows BITS COM component.

  • 0

We use an open source library written in C# wrapping Windows BITS COM component. However, the code is only safe to run it in x86 mode. I would like to contribute to the library by making it safe for both x86 and x64, however I have no deep knowledge in this field.

Could you please list here good/bad practices, typical issues, maybe principles also, etc, what to watch out for?

For example, I have seen in the code IntPtr is casted to System.Int32, which does not fly well on x64. How would you address this and similar issues in a platform agnostic manner?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I think you are talking about SharpBits.NET, a wrapper for the BITS component. Yes, there are several places where the author fumbled the interop. There is otherwise no reason why it couldn’t work, BITS is available both as a 32-bit and a 64-bit COM server. One example of such a fumble is in this thread.

    Getting the P/Invoke declaration wrong or improperly manual marshaling is the vast majority of all 64-bit interop problems. I’ve left lots of hints on 64-bit coding problems in this thread.

    • 0