From 3663e13d3b129bafca0149eda5bce35aba8c48ee Mon Sep 17 00:00:00 2001
From: Peter Collins <pecolli@microsoft.com>
Date: Tue, 31 Mar 2020 15:50:38 -0400
Subject: [PATCH] [.NET 5] Start adding some project capabilities

Context: https://github.com/xamarin/xamarin-android/pull/4383

Visual Studio uses CPS to load SDK-style projects. In CPS, most things
are keyed-off so-called capabilities[0] which replace other methods that
were used previously like project type GUIDs.

While capabilities can be defined in the IDE, they make most sense to be
directly expressed in the targets themselves where CPS will pick them up
automatically.

After discussing with @kzu, simply using `Android` could be confusing
with native C++ Android project that export the same capability. By
combining `Managed + Mobile + Android` we can make a clear distinction
that we are dealing with a Xamarin.Android project.

[0]  https://github.com/microsoft/VSProjectSystem/blob/master/doc/overview/about_project_capabilities.md
---
 .../targets/Xamarin.Android.Sdk.targets                    | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/src/Xamarin.Android.Sdk/targets/Xamarin.Android.Sdk.targets b/src/Xamarin.Android.Sdk/targets/Xamarin.Android.Sdk.targets
index a0bd986a9a0..ffd24e1dcef 100644
--- a/src/Xamarin.Android.Sdk/targets/Xamarin.Android.Sdk.targets
+++ b/src/Xamarin.Android.Sdk/targets/Xamarin.Android.Sdk.targets
@@ -16,4 +16,11 @@
   <Import Project="$(MSBuildThisFileDirectory)..\tools\Xamarin.Android.Common.targets" />
   <Import Project="$(MSBuildThisFileDirectory)Xamarin.Android.Sdk.Tooling.targets" />
 
+  <!-- Automatically supply project capabilities for IDE use -->
+  <ItemGroup>
+    <ProjectCapability Include="Mobile" />
+    <ProjectCapability Include="Android" />
+    <ProjectCapability Include="AndroidApplication" Condition="$(AndroidApplication)" />
+  </ItemGroup>
+
 </Project>