work

Author: nkolev92

designs/NuGet-CPPCLI-Support.md

@@ -72,9 +72,9 @@ To understand the proposed changes, here's a mapping of all `C++` project types
 In the background, it is said that C++/CLI projects are supposed to support installing both managed and native packages. This would require some amendments to NuGet's framework model.
 
 `native` framework is not compatible with anything but `native` and that will remain.
-NuGet also has a fallback one.
+NuGet has a fallback compatibility mode as well.
 For example: .NET Core projects have a fallback to .NET Framework with a warning. This is also callled `Asset Target Fallback`.
-If a package supports .NET Core or .NET Standard, it's fully compatible with a .NET Core project. Otherwise if a package has .NET Framework assets, the package is installed, but with a warning.
+If a package supports .NET Core or .NET Standard, it's fully compatible with a .NET Core project. Otherwise if a package has .NET Framework assets, the package is installed, but with a *warning*.
 
 The `Asset Target Fallback` implementation currently suffers from a bug where the dependencies are not pulled in correctly, see [5957](https://github.com/NuGet/Home/issues/5957).
 
@@ -83,6 +83,7 @@ Whatever the effective frameworks turn out to be, there are 2 approaches that we
 * Utilize AssetTargetFallback
 
 This would require project type changes. The project type would specify which target framework to fall back to. This likely requires fixing [5957](https://github.com/NuGet/Home/issues/5957).
+Note that this would *generate* a warning when managed packages are used.
 
 * Introduce a `dedicated dual compatibility` framework