-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added enhancements on top of Calling Server preview 1 #21686
Changes from all commits
3a31cac
2aac1b8
89e1158
2cdc4b8
8c07b7b
e6322ed
09a1452
bf54682
f1efa58
f3aebeb
720d59c
0161219
c310ffe
37c4531
37c39d4
29ce1ed
1717a69
20e4121
e829b98
162c75e
1a9464f
58ffcc3
2e163e6
f93d076
1657f3e
0a76c1a
e264d03
fbc6d87
b5d2464
beaae94
c5670ab
6d505c9
072566e
4d49521
5b86515
1efe0fd
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,13 @@ | ||
<Project Sdk="Microsoft.NET.Sdk"> | ||
<PropertyGroup> | ||
<Description> | ||
This client library enables working with the Microsoft Azure Communication Service Calling Server APIs. | ||
This client library enables working with the Microsoft Azure Communication CallingServer service. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can we rename to Calling Server, two separate words? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We prefer using "CallingServer" which was "Calling Server" to keep it consistent within SDK library and API |
||
For this release, see notes - https://github.com/Azure/azure-sdk-for-net-pr/blob/master/sdk/communication/Azure.Communication.ServerCalling/README.md and https://github.com/Azure/azure-sdk-for-net-pr/blob/master/sdk/communication/Azure.Communication.ServerCalling/CHANGELOG.md. | ||
</Description> | ||
<AssemblyTitle>Azure Communication Service Calling Server APIs</AssemblyTitle> | ||
<AssemblyTitle>Azure Communication CallingServer Service</AssemblyTitle> | ||
<Version>1.0.0-beta.1</Version> | ||
<!--The ApiCompatVersion is managed automatically and should not generally be modified manually.--> | ||
<PackageTags>Microsoft Azure Communication Calling Server APIs;Microsoft;Azure;Azure Communication Service;Azure Communication Calling Server APIs;Calling;Communication;$(PackageCommonTags)</PackageTags> | ||
<PackageTags>Microsoft Azure Communication CallingServer Service;Microsoft;Azure;Azure Communication Service;Azure Communication CallingServer Service;Calling;Communication;$(PackageCommonTags)</PackageTags> | ||
<TargetFrameworks>$(RequiredTargetFrameworks)</TargetFrameworks> | ||
</PropertyGroup> | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we need .Value?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apis are returning Response object which kind of wrapped http response object. The Value property contain the return value.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
then variable should be named differently - something like callConnectionResponse