This PR is deliberately against the public repo rather than the private development repo, because we want these changes to be visible immediately while we're still preparing the 2.0.0 release. It's important to get people's attention about the renaming, because if they're only watching the LaunchDarkly.XamarinSdk package in NuGet for updates, and not following GitHub release notifications, they might never notice the release of the new LaunchDarkly.ClientSdk package.
I've copied some of the wording from the version of README.md that's in the private repo, and applied our new standard formatting for the boilerplate content, but I've retained references to LaunchDarkly.XamarinSdk that are still correct for the public code as it is right now.
I also updated the CI configuration to use .NET Core 2.1 instead of 2.0— otherwise no builds would pass, since 2.0 is no longer available.
This PR is deliberately against the public repo rather than the private development repo, because we want these changes to be visible immediately while we're still preparing the 2.0.0 release. It's important to get people's attention about the renaming, because if they're only watching the
LaunchDarkly.XamarinSdkpackage in NuGet for updates, and not following GitHub release notifications, they might never notice the release of the newLaunchDarkly.ClientSdkpackage.I've copied some of the wording from the version of README.md that's in the private repo, and applied our new standard formatting for the boilerplate content, but I've retained references to
LaunchDarkly.XamarinSdkthat are still correct for the public code as it is right now.I also updated the CI configuration to use .NET Core 2.1 instead of 2.0— otherwise no builds would pass, since 2.0 is no longer available.