This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
So I'm trying to develop an application in Visual Studio (C#, .NET 4.7.2 framework) and I've added the azure.communication.calling NuGet package, but it appears that it requires UWP? I was under the impression that Azure Communication Services was not restricted to only UWP applications, or is that not so? It's surprisingly difficult to find further information on this.
You'd better explain clearly what is "it appears that it requires UWP". NuGet.org clearly states this package to be compatible with .NET Framework 4.6.1 and above.
So, if you setup a new project, say a WPF, .NET 4.7.2 for example (we're not using UWP here), and then try using Azure.Communication.Calling, you'll find errors pop up which don't appear in a UWP project.
So for instance, create a new CallClient, let's name it myCallClient.
Using "await myCallClient.CreateCallAgent(token, callAgentOptions)" gives you the error:
"The type IAsyncOperation<> is defined in an assembly that is not referenced. You must add a reference to assembly 'Windows.Foundation.FoundationContract, Version=255.255.255.255 ..." etc.
Okay, so I add in the references to Windows.winmd and System.Runtime.WindowsRuntime.dll to get around these problems.
However then something else will pop up, again, only in a WPF project. Trying to create an instance of Azure.WinRT.Communication.CommunicationTokenCredential for example, will give you a runtime error: "System.TypeLoadException: Requested Windows Runtime type is not registered / COMException: Class not registered"
Seems like I'm constantly battling all kinds of errors which don't show up when you create a UWP application. And I can't seem to find any examples anywhere of people using anything other than UWP with Azure Communication Services - so that leads me to believe it's the only option?
"The type IAsyncOperation<> is defined..." can be easily resolved by adding NuGet package of Microsoft.Windows.SDK.Contracts. However, those "Class not registered" exceptions remain, which seems to indicate that deep down inside those COM objects are not exposed for desktop apps (like .NET Framework WPF) to consume. That's normal, as desktop apps only only consume a small set of Windows Runtime based API. Alternatively, you might build the functionality upon the Azure Communication Services JavaScript SDK or UWP and then use inter-process communication to connect that separate component to your WPF app on .NET Framework.
Well, perhaps you're aware of some alternatives I can use for video calling?
Basically I just want to create an application that can use the computer's webcam and microphone and perform P2P video calls, but it has to be a C# .NET desktop application.
Any ideas?
JamesBiz-3753, Apologies for the delay from over the weekend. I'm discussing on this internally and will get back to you shortly. Thanks for your patience!