The next beta drop of the Calling SDK will have the namespace renamed to avoid clashes with the Chat SDK.
Acs Calling SDK in Windows Desktop Application Development
Hi,
I am trying to develop a desktop application using WPF or UWP for communication that consists of chat and calling features using Azure communication services. I am having some issues with calling SDK. In the ACS docs, the calling SDK is implemented in the UWP.
I tried to install the Azure.Communication.Calling SDK in WPF.net5.0(version)
soon after installing
- The XAML design window is showing unhandled exception has occurred
The XAML Designer has exited unexpectedly. (Exit code: 8000808c)
Error:-NETSDK1130 Azure.Communication.winmd cannot be referenced. Referencing a Windows Metadata component directly when targeting .NET 5 or higher is not supported. For more information, see https://aka.ms/netsdk1130
In UWP after installing both the Azure.Communication.Calling SDK Version-latest prerelease 1.0.0-beta28 and Azure Communication.Chat SDK version-1.0.1
occurred Errors are
- While using CommunicationUserldentifier method
CS0433: The type 'CommunicationUserldentifier' exists in both 'Azure.Communication.Common, Version 1.0.0.0, Culture=neutral, PublicKeyToken=92742159e12e44c8' and 'Azure.Communication, Version=255.255.255.255, Culture=neutral, PublicKeyToken=null, ContentType-WindowsRuntime' - While using CommunicationTokenCredential method
CS0433: The type 'CommunicationTokenCredential' exists in both 'Azure.Communication.Common, Version 1.0.0.0, Culture=neutral, PublicKeyToken=92742159e12e44c8' and 'Azure.Communication, Version=255.255.255.255, Culture=neutral, PublicKeyToken=null, ContentType=WindowsRuntime'.
Is there any solution to this problem?
3 answers
Sort by: Most helpful
-
Augusto Righetto 1 Reputation point Microsoft Employee
2021-07-14T21:51:09.11+00:00 -
Grmacjon-MSFT 18,811 Reputation points
2021-07-31T00:39:31.887+00:00 The Calling SDK currently supports .Net Native only. As Augusto mentioned, a solution for the namespace conflict is in the works.
-
AugustoRighetto-0178 1 Reputation point
2021-08-02T18:33:40.89+00:00 The beta 29 package available at https://www.nuget.org/packages/Azure.Communication.Calling has the namespace conflict fixed.