blocks|key|3030648|text|它应该和下面的一样简单。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3030649|var+route+=+new+Route("blah/{*path}",+new+MyRouteHandler());
RouteTable.Routes.Add(route);

public+class+MyRouteHandler+:+IRouteHandler
{
++++public+IHttpHandler+GetHttpHandler(RequestContext+requestContext)
++++{
++++++++//+return+some+HTTP+handler+here
++++}
}|code-block|syntax|javascript|3030650|然后在web.config中的HTTP模块下注册System.Web.Routing.UrlRoutingModule，就可以了。|3030651|<add+name="Routing"+type="System.Web.Routing.UrlRoutingModule,+System.Web.Routing,+Version=3.5.0.0,+Culture=neutral,+PublicKeyToken=31BF3856AD364E35"/>|3030652|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

It should be as easy as the below.

<pre><code>var route = new Route("blah/{*path}", new MyRouteHandler());
RouteTable.Routes.Add(route);

public class MyRouteHandler : IRouteHandler
{
 public IHttpHandler GetHttpHandler(RequestContext requestContext)
 {
 // return some HTTP handler here
 }
}
</code></pre>

Then register System.Web.Routing.UrlRoutingModule under HTTP modules in web.config and you should be good to go.

<pre><code>&lt;add name="Routing" type="System.Web.Routing.UrlRoutingModule, System.Web.Routing, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/&gt;
</code></pre>

blocks|key|5286638|text|我被要求将此作为Share+Point评估过程的一部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5286639|我的理解是，uri模板本质上是主机名，后跟递归文件夹结构。|5286640|通过Share+Point将uri截断为255个字符，这将进一步复杂化。因此，如果您有一个特别深或冗长的文件夹结构，那么您的uri可能会变得无效。|5286641|我正在考虑通过遵循人类可读的约定并转换为Share+Point约定来本质上美化/整理uri。即：|5286642|http://myhostname.com/docs/human-resources/case-files/2009/reviews/ed-blackburn.docx|offset|length|5286643|转换为共享点：|5286644|http://myhostname.com/human%2520resources/case%2520files/2009/reviews/ed%2520blackburn.docx|5286645|任何其他所需的服务都可以由控制器控制。|5286646|如果超过255个字符，我最初的建议是使用某种tinyurl方法。|5286647|entityMap|0|LINK|mutability|MUTABLE|url|1|http://myhostname.com/human%2520resources/case%2520files/2009/reviews/ed%2520blackburn.docx^0|0|0|0|0|0|2C|0|0|0|0|2D|1|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@$J|17|K|18|1|19]]|A|$]]|$1|L|3|M|5|6|7|1A|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1B|8|@]|9|@$J|1C|K|1D|1|1E]]|A|$]]|$1|P|3|Q|5|6|7|1F|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1G|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|I]]|10|$5|W|X|Y|A|$Z|11]]]]

I've been asked to look at this as part of an Share Point evaluation process.

My understanding is that the uri template is essentially host name followed by the recursive folder structure. 

This is further complicated by Share Point truncating the uri at 255 characters. So if you have a particularly deep or verbose folder structure then your uri can become invalid.

I was thinking about essentially prettifying / tidying up the uri by follow a human readable convention and convert to the Share Point convention. i.e:

<a href="http://myhostname.com/docs/human-resources/case-files/2009/reviews/ed-blackburn.docx" rel="nofollow noreferrer">http://myhostname.com/docs/human-resources/case-files/2009/reviews/ed-blackburn.docx</a>

converts to Share Points:

<a href="http://myhostname.com/human%20resources/case%20files/2009/reviews/ed%20blackburn.docx" rel="nofollow noreferrer">http://myhostname.com/human%20resources/case%20files/2009/reviews/ed%20blackburn.docx</a>

Any additional required services can be controlled by the controller.

If longer than 255 characters some kind of tinyurl approach would be my initial suggestion.

blocks|key|3875731|text|我最终拿到了Ryan的东西：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3875732|var+route+=+new+Route("blah/{*path}",+new+MyRouteHandler());
RouteTable.Routes.Add(route);
public+class+MyRouteHandler+:+IRouteHandler
{++++
public+IHttpHandler+GetHttpHandler(RequestContext+requestContext)++++
{++++++++
+++++//rewrite+to+some+know+sharepoint+path
+++++HttpContext.Current.RewritePath("~/Pages/Default.aspx");

+++++//+return+some+HTTP+handler+here++
+++++return+new+DefaultHttpHandler();++

}}|code-block|syntax|javascript|3875733|这对我来说似乎没什么问题。|3875734|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I ended up taking what Ryan had:

<pre><code>var route = new Route("blah/{*path}", new MyRouteHandler());
RouteTable.Routes.Add(route);
public class MyRouteHandler : IRouteHandler
{ 
public IHttpHandler GetHttpHandler(RequestContext requestContext) 
{ 
 //rewrite to some know sharepoint path
 HttpContext.Current.RewritePath("~/Pages/Default.aspx");

 // return some HTTP handler here 
 return new DefaultHttpHandler(); 

}}
</code></pre>

That seems to work ok for me.

I'm trying to setup some friendly URLs on a SharePoint website. I know that I can do the ASP.Net 2.0 friendly URLs using RewritePath, but I was wondering if it was possible to make use of the System.Web.Routing that comes with ASP.NET 3.5 SP1. 

I think I've figured out how to get my route table loaded, but I'm not clear on what method to use to get the correct IHttpHandler to pass out.

Thanks!

Using ASP.Net 3.5 SP1 Routing with SharePoint 2007

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我正在尝试在SharePoint网站上设置一些友好的URL。我知道我可以用RewritePath做ASP.Net 2.0友好的SP1，但是我想知道是否有可能使用ASP.NET 3.5 URL附带的URL。我想我已经知道了如何加载我的路由表，但是我不清楚应该使用什么方法来获得正确的IHttpHandler。谢谢!

问将ASP.Net 3.5 SP1路由与SharePoint 2007配合使用
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将ASP.Net 3.5 SP1路由与SharePoint 2007配合使用EN