* Add SqlConnectionInfo.AccessTokenFactory
* Make SqlConnectionInfo public
* Expose ShardMapManagerFactory methods with SqlConnectionInfo
* Expose SqlConnectionInfo methods for ShardMap
* Expose SqlConnectionInfo methods on ListShardMap and RangeShardMap
* Update release notes
* Update SqlShardMapManagerCredentials.EnsureCredentials to check AccessToken
* Throw NotSupportedException when using AccessToken on downlevel framework
* Inline CreateSqlShardMapManager which is only called in one place
* Remove CreateSqlShardMapManager whose unique param is always null
* Remove CreateSqlShardMapManager which is never called
* Upstack SqlConnectionInfo in CreateSqlShardMapManager
* Remove TryGetSqlShardMapManager whose unique value is always null
* Upstack SqlConnectionInfo in (Try)GetSqlShardMapManager
Implemented GetMappings and TryGetMappings with LookupOptions for ListShardMap and RangeShardMap with LookupOptions.LookupInStore as the default (for compabitility).
Building targeting net452 does not define NET451 (for example), so I added a NETFRAMEWORK defineconstant to represent any framework version (as opposed to .net standard).
MappingOptions allow a user to specify if validation should be performed
on the affected shard in a mapping. When a mapping is taken offline,
users can specify whether or not they want open connections
to affected shard from being killed.
These implementations are decompiled from the generated ElasticScale.Client.Fakes.dll. This is the first step in breaking our build dependency on fakes.
- Unit tests fail to compile because they cannot properly reference the ElasticScale.Client Project. They will have to be updated to use a xproj project file.
- Now the same project will produce outputs for both Net451 and NetStandard16.
- Unit tests failing to build.
- "dotnet pack" has incorrect package "id" <https://github.com/dotnet/cli/issues/2677>