OASIS-2504 [C#] Release 2.0.0-beta1 (#71)

* Revert "Eventdispatcherissue (#35) (#54)"

This reverts commit 5df7cfb.

* Bump version to 2.0 beta.

* Update OptimizelySDK.nuspec

* AssemblyVersion = 2.0.0.0

* Improved 1.3.1 DemoApp

* Updated OptimizelySDK.Package and OptimizelySDK.nuspec

* keypair.snk for *.sln, *.csproj

* CHANGELOG.md corrections

* SDK_VERSION synch with NuGet package version.

* Make 'UserAttributes userAttributes = null' optional in 5 API's

* Update verifysn.ps1 and DemoApp.csproj to 2.0.0-beta1

Author: kellyroach-optimizely

CHANGELOG.md

@@ -1,26 +1,25 @@
 ## 2.0.0-beta1
-
 March 29th, 2018
 
-This major release of the Optimizely SDK introduces APIs for Feature Management. It also introduces some breaking changes listed below.
+This major release of the Optimizely SDK introduces APIs for Feature Management.
 
 ### New Features
-* Introduces the `isFeatureEnabled` API to determine whether to show a feature to a user or not.
+* Introduces the `IsFeatureEnabled` API to determine whether to show a feature to a user or not.
 ```
-var enabled = optimizelyClient.isFeatureEnabled("my_feature_key", "user_1", userAttributes);
+var enabled = OptimizelyClient.IsFeatureEnabled("my_feature_key", "user_1", userAttributes);
 ```
 
 * You can also get all the enabled features for the user by calling the following method which returns a list of strings representing the feature keys:
 ```
-var enabledFeatures = optimizelyClient.getEnabledFeatures("user_1", userAttributes);
+var enabledFeatures = OptimizelyClient.GetEnabledFeatures("user_1", userAttributes);
 ```
 
 * Introduces Feature Variables to configure or parameterize your feature. There are four variable types: `Integer`, `String`, `Double`, `Boolean`.
 ```
-var stringVariable = optimizelyClient.getFeatureVariableString("my_feature_key", "string_variable_key", "user_1");
-var integerVariable = optimizelyClient.getFeatureVariableInteger("my_feature_key", "integer_variable_key", "user_1");
-var doubleVariable = optimizelyClient.getFeatureVariableDouble("my_feature_key", "double_variable_key", "user_1");
-var booleanVariable = optimizelyClient.getFeatureVariableBoolean("my_feature_key", "boolean_variable_key", "user_1");
+var stringVariable = OptimizelyClient.GetFeatureVariableString("my_feature_key", "string_variable_key", "user_1", userAttributes);
+var integerVariable = OptimizelyClient.GetFeatureVariableInteger("my_feature_key", "integer_variable_key", "user_1", userAttributes);
+var doubleVariable = OptimizelyClient.GetFeatureVariableDouble("my_feature_key", "double_variable_key", "user_1", userAttributes);
+var booleanVariable = OptimizelyClient.GetFeatureVariableBoolean("my_feature_key", "boolean_variable_key", "user_1", userAttributes);
 ```
 
 ## 1.3.1
@@ -68,7 +67,7 @@ OptimizelyClient.Track(eventKey, userId, attributes, eventTags);
 
 * Introduce Forced Variation - This allows you to force users into variations programmatically in real time for QA purposes without requiring datafile downloads from the network.
 ```
-var result = OptimizelyClient.setForcedVariation(experimentKey, userId, forcedVariationKey);
+var result = OptimizelyClient.SetForcedVariation(experimentKey, userId, forcedVariationKey);
 ```
 
 * Upgrade to use new [event API](https://developers.optimizely.com/x/events/api/index.html).

OptimizelySDK.DemoApp/Content/Images/item_1.png

@@ -1,5 +1,4 @@
 body {
-    padding-top: 50px;
     padding-bottom: 20px;
 }