blocks|key|2556840|text|有几种方法可以实现这样的目标。一种可能是根据路线动态更改布局，即对AMP使用模板X，否则使用Y模板。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2556841|更强大的解决方案是视图位置扩展器。这通常也被认为是显示模式的后继。视图位置扩展器基本上是一种机制，它允许您对Razor引擎查找视图的物理位置进行后处理。因此，您可以使用它有条件地修改或扩展视图所在的路径。|offset|length|style|BOLD|2556842|在您的情况下，您可能想要更改行为，以便当通过AMP访问您的网站时，Razor应该在退回到<view>.cshtml之前首先查找<view>.amp.cshtml。|CODE|2556843|为了做到这一点，你必须实现IViewLocationExpander。在PopulateViews中，您必须检测是否处于AMP模式；然后在ExpandViewLocations中，您可以修改视图位置。|2556844|这可能看起来有点像这样(未经测试，作为如何实现的想法)：|2556845|public+class+AmpViewLocationExpander+:+IViewLocationExpander
{
++++private+const+string+ValueKey+=+"ampmode";

++++public+void+PopulateValues(ViewLocationExpanderContext+context)
++++{
++++++++//+magic+utility+method+that+determines+whether+this+is+within+an+AMP+context
++++++++var+isAmp+=+context.ActionContext.HttpContext.IsAmp();

++++++++//+persist+the+value+on+the+context+to+allow+the+cache+to+consider+this
++++++++context.Values[ValueKey]+=+isAmp.ToString();
++++}

++++public+IEnumerable<string>+ExpandViewLocations(ViewLocationExpanderContext+context,
++++++++IEnumerable<string>+viewLocations)
++++{
++++++++//+when+in+AMP+mode
++++++++if+(context.Values.TryGetValue(ValueKey,+out+var+isAmpValue)+&&+isAmpValue+==+"True")
++++++++{
++++++++++++return+ExpandAmpViewLocations(viewLocations);
++++++++}

++++++++//+otherwise+fall+back+to+default+locations
++++++++return+viewLocations;
++++}

++++private+IEnumerable<string>+ExpandAmpViewLocations(IEnumerable<string>+viewLocations)
++++{
++++++++foreach+(var+location+in+viewLocations)
++++++++{
++++++++++++//+yield+the+AMP+version+first
++++++++++++yield+return+location.Replace("{0}",+"{0}.amp");

++++++++++++//+then+yield+the+normal+version+as+a+fallback
++++++++++++yield+return+location;
++++++++}
++++}
}|code-block|syntax|javascript|2556846|完成后，您只需在ConfigureServices中的AddMvc调用之后注册扩展器|2556847|services.AddMvc()
++++.AddRazorOptions(options+=>
++++{
++++++++options.ViewLocationExpanders.Add(new+AmpViewLocationExpander());
++++});|2556848|然后，您只需要为AMP创建您的备用视图。|2556849|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.razor.iviewlocationexpander|1|https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.razor.iviewlocationexpander.populatevalues|2|https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.razor.iviewlocationexpander.expandviewlocations^0|0|9|7|0|18|D|1R|H|0|D|L|10|D|1X|J|D|L|0|10|D|1|1X|J|2|0|0|0|8|H|R|6|0|0|0^^$0|@$1|2|3|4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1C|8|@$D|1D|E|1E|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1F|8|@$D|1G|E|1H|F|J]|$D|1I|E|1J|F|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|1K|8|@$D|1L|E|1M|F|J]|$D|1N|E|1O|F|J]|$D|1P|E|1Q|F|J]]|9|@$D|1R|E|1S|1|1T]|$D|1U|E|1V|1|1W]|$D|1X|E|1Y|1|1Z]]|A|$]]|$1|M|3|N|5|6|7|20|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|21|8|@]|9|@]|A|$R|S]]|$1|T|3|U|5|6|7|22|8|@$D|23|E|24|F|J]|$D|25|E|26|F|J]]|9|@]|A|$]]|$1|V|3|W|5|Q|7|27|8|@]|9|@]|A|$R|S]]|$1|X|3|Y|5|6|7|28|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|29|8|@]|9|@]|A|$]]]|10|$11|$5|12|13|14|A|$15|16]]|17|$5|12|13|14|A|$15|18]]|19|$5|12|13|14|A|$15|1A]]]]

There are a few ways to achieve something like this. One possibility would be to dynamically change your layout depending on the route, i.e. use template X for AMP or Y otherwise.

A more powerful solution would be the view location expander. This is also generally considered as a successor to the display modes. The view location expander is basically a mechanism that allows you to post-process the physical locations where the Razor engine will look for views. So you can use this to conditionally modify or expand the paths where your views are located.

In your case, you might want to change the behavior so that when accessing your site through AMP, Razor should first look for a <code>&lt;view&gt;.amp.cshtml</code> before falling back to <code>&lt;view&gt;.cshtml</code>.

In order to do that, you would have to implement <a href="https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.razor.iviewlocationexpander" rel="nofollow noreferrer"><code>IViewLocationExpander</code></a>. In <a href="https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.razor.iviewlocationexpander.populatevalues" rel="nofollow noreferrer"><code>PopulateViews</code></a> you would have to detect whether you are within AMP mode or not; and in <a href="https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.razor.iviewlocationexpander.expandviewlocations" rel="nofollow noreferrer"><code>ExpandViewLocations</code></a> you could then modify the view locations.

That could look somewhat like this (untested, as an idea on how to approach this):

<pre><code>public class AmpViewLocationExpander : IViewLocationExpander
{
 private const string ValueKey = "ampmode";

 public void PopulateValues(ViewLocationExpanderContext context)
 {
 // magic utility method that determines whether this is within an AMP context
 var isAmp = context.ActionContext.HttpContext.IsAmp();

 // persist the value on the context to allow the cache to consider this
 context.Values[ValueKey] = isAmp.ToString();
 }

 public IEnumerable&lt;string&gt; ExpandViewLocations(ViewLocationExpanderContext context,
 IEnumerable&lt;string&gt; viewLocations)
 {
 // when in AMP mode
 if (context.Values.TryGetValue(ValueKey, out var isAmpValue) &amp;&amp; isAmpValue == "True")
 {
 return ExpandAmpViewLocations(viewLocations);
 }

 // otherwise fall back to default locations
 return viewLocations;
 }

 private IEnumerable&lt;string&gt; ExpandAmpViewLocations(IEnumerable&lt;string&gt; viewLocations)
 {
 foreach (var location in viewLocations)
 {
 // yield the AMP version first
 yield return location.Replace("{0}", "{0}.amp");

 // then yield the normal version as a fallback
 yield return location;
 }
 }
}
</code></pre>

Once you have that, you only have to register the expander after the <code>AddMvc</code> call within your <code>ConfigureServices</code>:

<pre><code>services.AddMvc()
 .AddRazorOptions(options =&gt;
 {
 options.ViewLocationExpanders.Add(new AmpViewLocationExpander());
 });
</code></pre>

And then you only need to create your alternate views for AMP.

I'm trying to create an AMP page with ASPNET Core MVC. I haven't been able to find many documents if any. For ASPNET, it was suggested to use <code>DisplayModes</code> to create a Google AMP Display. However, ASPNet Core doesn't support <code>DisplayModes</code> and I'm trying to figure a way to work around it. Any suggestions would be greatly appreciated!

<pre><code>@model Models.Article
@{
 Layout = null;
}

&lt;!doctype html&gt;
&lt;html amp&gt;
 &lt;head&gt;
 &lt;meta charset="utf-8"&gt;
 &lt;link rel="canonical" href="/article.cshtml"&gt;
 &lt;link rel="amphtml" href="/article.amp.cshtml"&gt;
 &lt;meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1"&gt;
 &lt;style amp-boilerplate&gt;body{-webkit-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-moz-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-ms-animation:-amp-start 8s steps(1,end) 0s 1 normal both;animation:-amp-start 8s steps(1,end) 0s 1 normal both}@@-webkit-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@@-moz-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@@-ms-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@@-o-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@@keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}&lt;/style&gt;
 &lt;noscript&gt;
 &lt;style amp-boilerplate&gt;
 body {
 -webkit-animation: none;
 -moz-animation: none;
 -ms-animation: none;
 animation: none
 }
 &lt;/style&gt;&lt;/noscript&gt;
 &lt;script async src="https://cdn.ampproject.org/v0.js"&gt;&lt;/script&gt;
 &lt;/head&gt;
 &lt;body&gt;
 &lt;article&gt;
 &lt;h2&gt;@Html.DisplayFor(model =&gt; model.Title)&lt;/h2&gt;
 &lt;div&gt;@Convert.ToDateTime(Model.PublishedDate).ToString("dddd, MMMM d, yyyy")&lt;/div&gt;
 &lt;/article&gt; 
 &lt;/body&gt;
&lt;/html&gt;
</code></pre>

Apply Google AMP (Accelerated Mobile Pages) to ASP.NET Core site

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在尝试用ASPNET Core MVC创建一个AMP页面。我找不到很多文档。对于ASPNET，建议使用DisplayModes来创建Google AMP显示。然而，ASPNet核心不支持DisplayModes，我正在尝试找到一种方法来解决这个问题。如有任何建议，我们将不胜感激！@model Models.Arti...

Google AMP (Accelerated Mobile Pages)在ASP.NET核心站点中的应用-腾讯云开发者社区-腾讯云

问Google AMP (Accelerated Mobile Pages)在ASP.NET核心站点中的应用
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Google AMP (Accelerated Mobile Pages)在ASP.NET核心站点中的应用EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Google AMP (Accelerated Mobile Pages)在ASP.NET核心站点中的应用
EN