Cleanup

Author: ViktorHofer

Directory.Build.props

@@ -195,18 +195,13 @@
       limitations in the way the .NET SDK finds shared frameworks and targeting packs. It allows
       tests to use the shared frameworks and targeting packs that were just built.
 
-      However, source-build needs this to not happen while building projects that rely on the
-      AppHost framework pack. Source-build installs an SDK in a custom location outside this
+      However, the VMR needs this to not happen while building projects that rely on the
+      AppHost framework pack. The VMR installs an SDK in a custom location outside this
       repository, and setting NetCoreTargetingPackRoot to a different location causes source-build
       to restore the AppHost pack as a prebuilt rather than using the one that's present in the SDK.
-      Source-build doesn't run tests, so the property is simply conditioned out.
+      The dotnet product build doesn't run tests, so the property is simply conditioned out.
     -->
     <NetCoreTargetingPackRoot Condition="'$(DotNetBuild)' != 'true'">$(LocalDotNetRoot)packs\</NetCoreTargetingPackRoot>
-    <!-- This is not correct and needs attention eventually. This is primarily used to find the nethost headers in the apphost pack.
-         These should be coming from a restored apphost pack, rather than a hard-coded local SDK. In fact, aspnetcore
-         should not rely on a local SDK or mutating one to build. -->
-    <NetCoreTargetingPackRoot Condition="'$(DotNetBuild)' == 'true'">$(DotNetRoot)packs\</NetCoreTargetingPackRoot>
-
   </PropertyGroup>
 
   <Import Project="eng\tools\RepoTasks\RepoTasks.tasks" Condition="'$(MSBuildProjectName)' != 'RepoTasks' AND '$(DesignTimeBuild)' != 'true'" />