Nuget - Change default CefSharpBuildAction for Exe/WinExe projects when using packages.config

- For Non library projects that use packages.config the default is now Content which should simplify clickonce support
  For libraries the default will remain as None
- For NetCore projects CefSharpBuildAction Content is mapped to default to support upgrading users

Technically this is a breaking change, user impact is expected to be low and can be overridden to restore
the previous behaviour in the edge cases.

Issue #4062

Author: amaitland

NuGet/CefSharp.Common.targets

@@ -96,16 +96,21 @@
   <PropertyGroup>
     <!--
     Allowable options are None, Content, NoAction.
-    None is the default (same as selecting the None Build Action in Visual Studio) for Nuget packages.config
-    Content is the default (same as selecting the None Build Action in Visual Studio) for Nuget PackageReference
+    
+	None is the default (same as selecting the None Build Action in Visual Studio) for Nuget packages.config
+	for WinExe/Exe projects (anything that's not Library) see https://github.com/cefsharp/CefSharp/issues/4062
+	None will copy the dependenceis to a directly referencing project file which is useful for library projects
+	that target packages.config as buildTransitive is not supported.
+	
+    Content is the default (same as selecting the Content Build Action in Visual Studio) for Nuget PackageReference
+	and WinExe/Exe projects (anything that's not Library)
     Technically the older Non-SDK Style project can use PackageReference under VS2019 (possibly VS2017 as well),
     so we use NuGetProjectStyle which is defined in the .nuget.g.props file for projects using PackageReference.
-    For Library projects with Nuget supports buildTransitive we don't include our additional files and packages, the transitive reference should flow directly to the consuming projects.
     For class libraries that are often AnyCPU and consuming Exe/WinExe projects that are x64 or x86 the resulting build output
-    is polluted with extra copies in sub folders.
+    is polluted with extra copies in sub folders. Set CefSharpBuildAction to NoAction to avoid copying the files.	
     -->
     <CefSharpBuildAction Condition="'$(CefSharpBuildAction)' == '' AND '$(NuGetProjectStyle)' != 'PackageReference'">None</CefSharpBuildAction>
-    <CefSharpBuildAction Condition="'$(CefSharpBuildAction)' == '' AND '$(NuGetProjectStyle)' == 'PackageReference'">Content</CefSharpBuildAction>
+    <CefSharpBuildAction Condition="'$(CefSharpBuildAction)' == '' AND ('$(NuGetProjectStyle)' == 'PackageReference' OR '$(OutputType)' != 'Library')">Content</CefSharpBuildAction>
 
     <CefSharpTargetDir Condition="'$(CefSharpTargetDir)' == ''"></CefSharpTargetDir>
     <!-- Ideally we could use EnsureTrailingSlash, was only added on 2017 so unlikely supported in older version of VS -->

NuGet/PackageReference/CefSharp.Common.NETCore.targets

@@ -16,8 +16,12 @@
     https://docs.microsoft.com/en-us/dotnet/core/tutorials/creating-app-with-plugin-support#plugin-with-library-dependencies
     -->
     <CefSharpBuildAction Condition="'$(CefSharpBuildAction)' == '' AND '$(OutputType)' == 'Library' AND '$(EnableDynamicLoading)' != 'true'">NoAction</CefSharpBuildAction>
-    <!-- Current supported values are Default, and NoAction (this target doesn't copy any files.) -->
+    <!--
+	Current supported values are Default, Content, and NoAction (this target doesn't copy any files.)
+	For backwards compatability for the older nuget packages Content will be mapped to Default
+	-->
     <CefSharpBuildAction Condition="'$(CefSharpBuildAction)' == ''">Default</CefSharpBuildAction>
+	<CefSharpBuildAction Condition="'$(CefSharpBuildAction)' == 'Content'">Default</CefSharpBuildAction>
   </PropertyGroup>
   <ItemGroup>
     <_CefSharpBrowserSubProcessFiles Include="$([System.IO.Path]::GetFullPath('$(MSBuildThisFileDirectory)..\runtimes\$(CefSharpRuntimeIdentifier)\native\CefSharp.BrowserSubprocess.runtimeconfig.json'))"/>