Update NU1011.md (#3347)

Author: jeffkl

docs/reference/errors-and-warnings/NU1011.md

@@ -15,7 +15,7 @@ f1_keywords:
 
 ### Issue
 
-`<PackageVersion />` items cannot contain floating versions.  NuGet's central package management (CPM) is considered an enterprise-level feature which provides easier version
+By default, `<PackageVersion />` items cannot contain floating versions.  NuGet's central package management (CPM) is considered an enterprise-level feature which provides easier version
 management at scale as well as deterministic and secure restores.  The use of floating versions introduces the possibility for a bad package to be introduced into your build
 after it has been pushed to a feed.  This can lead to a situation where you made no changes in your repository but suddenly something is broken and there is no way for you to
 get back into a good state without removing the floating version or pushing a newer version of the package which is fixed.  Using non-floating versions means that every upgrade
@@ -30,4 +30,11 @@ commit in your repository.
 
 ### Solution
 
-Change the floating version to a [non floating version range](../../concepts/Package-Versioning.md#version-ranges).
+It is recommended to change the floating version to a [non floating version range](../../concepts/Package-Versioning.md#version-ranges).  If that is not possible, you can enable
+floating versions with CPM by setting an MSBuild property:
+
+```xml
+<PropertyGroup>
+  <CentralPackageFloatingVersionsEnabled>true</CentralPackageFloatingVersionsEnabled>
+</PropertyGroup>
+```