Rename PrimeCache to PrimeCacheAsync (keeping older name as obsolete overload). Fixes #246.

Author: SteveSandersonMS

samples/angular/MusicStore/Views/Home/Index.cshtml

@@ -4,8 +4,8 @@
 
 <cache vary-by="@Context.Request.Path">
     <app asp-prerender-module="wwwroot/ng-app/boot-server">Loading...</app>
-    @await Html.PrimeCache(Url.Action("GenreMenuList", "GenresApi"))
-    @await Html.PrimeCache(Url.Action("MostPopular", "AlbumsApi"))
+    @await Html.PrimeCacheAsync(Url.Action("GenreMenuList", "GenresApi"))
+    @await Html.PrimeCacheAsync(Url.Action("MostPopular", "AlbumsApi"))
 </cache>
 
 @section scripts {

src/Microsoft.AspNetCore.AngularServices/PrimeCacheHelper.cs

@@ -11,9 +11,15 @@ namespace Microsoft.AspNetCore.AngularServices
 {
     public static class PrimeCacheHelper
     {
-        public static async Task<HtmlString> PrimeCache(this IHtmlHelper html, string url)
+        [Obsolete("Use PrimeCacheAsync instead")]
+        public static Task<IHtmlContent> PrimeCache(this IHtmlHelper html, string url)
         {
-            // TODO: Consider deduplicating the PrimeCache calls (that is, if there are multiple requests to precache
+            return PrimeCacheAsync(html, url);
+        }
+
+        public static async Task<IHtmlContent> PrimeCacheAsync(this IHtmlHelper html, string url)
+        {
+            // TODO: Consider deduplicating the PrimeCacheAsync calls (that is, if there are multiple requests to precache
             // the same URL, only return nonempty for one of them). This will make it easier to auto-prime-cache any
             // HTTP requests made during server-side rendering, without risking unnecessary duplicate requests.