Change target framework of AuthenticationAssemblyLoadContext to netcareapp2.1 (#17425)

* New-AzVM fix, error stating "VMCustomization feature is not allowed on your subscription" (#17409) (#17423)

* potential fix for vmcustomization usage

* dev fix, vm tests pass

* changelog

* changelog cleanup

* Update ChangeLog.md

Co-authored-by: Dingmeng Xue <[email protected]>
Co-authored-by: Beisi Zhou <[email protected]>

Co-authored-by: Adam Sandor <[email protected]>
Co-authored-by: Dingmeng Xue <[email protected]>

* change target framework to netcoreapp2.1

Co-authored-by: Adam Sandor <[email protected]>
Co-authored-by: Dingmeng Xue <[email protected]>

Author: 3 people

src/Accounts/Accounts/ChangeLog.md

@@ -19,6 +19,7 @@
 -->
 
 ## Upcoming Release
+* Changed target framework of AuthenticationAssemblyLoadContext to netcoreapp2.1 [#17428]
 
 ## Version 2.7.3
 * Fixed the issue that authorization does not work in customized environment [#17157]

src/Accounts/AuthenticationAssemblyLoadContext/AuthenticationAssemblyLoadContext.csproj

@@ -1,12 +1,12 @@
-<Project Sdk="Microsoft.NET.Sdk">
+<Project Sdk="Microsoft.NET.Sdk">
   <PropertyGroup>
     <PsModuleName>Accounts</PsModuleName>
   </PropertyGroup>
 
   <Import Project="$(MSBuildThisFileDirectory)..\..\Az.props" />
 
   <PropertyGroup>
-    <TargetFramework>netcoreapp3.1</TargetFramework>
+    <TargetFramework>netcoreapp2.1</TargetFramework>
     <AssemblyName>Microsoft.Azure.PowerShell.AuthenticationAssemblyLoadContext</AssemblyName>
     <RootNamespace>Microsoft.Azure.PowerShell.AuthenticationAssemblyLoadContext</RootNamespace>
   </PropertyGroup>