64-bit Version of Windows Meeting SDK & Support of C#-Wrapper

We are currently using the JavaScript Web Meeting SDK for a proctoring feature in our software Safe Exam Browser. Unfortunately, we have found the JavaScript API to be very limited and furthermore impacted by various issues (e.g. CORS restrictions).

Thus we’d like to switch to the Desktop Meeting SDK. However, it appears to be the case that we won’t be able to use the SDK at the moment due to the following issues we have found:

  1. The Desktop Meeting SDK is only available for x86 platforms. Why is that the case, and are there any plans (including a timeline) to also support x64 platforms?
  2. We’d need the C# wrapper for the Desktop Meeting SDK. However, it appears to be the case that the currently existing wrapper is not officially supported nor maintained. Are there any plans to officially provide a C# Desktop Meeting SDK resp. wrapper?
  3. How realistic would it be to maintain a wrapper by ourselves, i.e. how high is the cadence of (possibly breaking) changes and how far reaching are these changes from one version to another?

Hi @sdk_testing, thanks for the post.

The Desktop Meeting SDK is only available for x86 platforms. Why is that the case, and are there any plans (including a timeline) to also support x64 platforms?

This is no longer the case. The Windows Meeting SDK now supports 64 bit architectures.

We’d need the C# wrapper for the Desktop Meeting SDK. However, it appears to be the case that the currently existing wrapper is not officially supported nor maintained. Are there any plans to officially provide a C# Desktop Meeting SDK resp. wrapper?

We do not have plans to begin actively maintaining the C# wrapper at this time, as it was initially developed with the intention of becoming a community-driven project. We may create a repo for the developer community to contribute to it in the future, but we do not have a planned timeline for this at the moment.

How realistic would it be to maintain a wrapper by ourselves, i.e. how high is the cadence of (possibly breaking) changes and how far reaching are these changes from one version to another?

Looking back at the releases over the past 1-2 years, the breaking changes that were introduced tended to be on the mild-to-moderate side. That being said, we cannot make any guarantees about the frequency or scope of future breaking changes. It’s unlikely that we will introduce large breaking changes or major rewrites of public APIs in multiple consecutive releases, but it isn’t impossible.

Thanks!