blocks|key|1393837|text|您可以始终像使用Web+forms一样使用Request.QueryString集合，但也可以让MVC处理它们并将它们作为参数传递。这是推荐的方法，因为它更容易，并且会自动验证输入数据类型。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1393838|entityMap^0|L|J|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

You can always use <code>Request.QueryString</code> collection like Web forms, but you can also make MVC handle them and pass them as parameters. This is the suggested way as it's easier and it will validate input data type automatically.

blocks|key|1393871|text|只需在操作上使用参数即可接受查询字符串参数。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1393872|public+ActionResult+Foo(string+someValue,+int+someOtherValue)+{...}|code-block|syntax|javascript|1393873|它将接受像.../someroute?someValue=abc&someOtherValue=123这样的查询|offset|length|style|CODE|1393874|除此之外，您可以直接查看请求以获得更多控制。|1393875|entityMap^0|0|0|5|1A|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Query string parameters can be accepted simply by using an argument on the action - i.e.

<pre><code>public ActionResult Foo(string someValue, int someOtherValue) {...}
</code></pre>

which will accept a query like <code>.../someroute?someValue=abc&amp;someOtherValue=123</code>

Other than that, you can look at the request directly for more control.

blocks|key|1608873|text|我推荐使用控制器的ValueProvider属性，这与UpdateModel/TryUpdateModel提取所需的路由、查询和表单参数的方式非常相似。这将防止您的方法签名可能变得非常大，并受到频繁更改的影响。它还使测试变得更容易，因为您可以在单元测试期间向控制器提供ValueProvider。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1608874|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I recommend using the ValueProvider property of the controller, much in the way that UpdateModel/TryUpdateModel do to extract the route, query, and form parameters required. This will keep your method signatures from potentially growing very large and being subject to frequent change. It also makes it a little easier to test since you can supply a ValueProvider to the controller during unit tests.

blocks|key|1393982|text|我想你要找的是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1393983|Request.QueryString["QueryStringName"]|code-block|syntax|javascript|1393984|您可以通过添加@在视图上访问它|offset|length|style|CODE|1393985|现在看看我的示例，，，我用QueryString生成了一个网址|1393986|+var+listURL+=+'@Url.RouteUrl(new+{+controller+=+"Sector",+action+=+"List"+,+name+=+Request.QueryString["name"]})';|1393987|listURL值为/Sector/List?name=value'|1393988|当queryString为空时|1393989|listURL值为/Sector/List|1393990|entityMap^0|0|0|7|1|0|0|0|9|O|0|1|B|0|9|C|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@$I|11|J|12|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|14|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|15|8|@$I|16|J|17|K|L]]|9|@]|A|$]]|$1|S|3|T|5|6|7|18|8|@$I|19|J|1A|K|L]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1B|8|@$I|1C|J|1D|K|L]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|X|$]]

I think what you are looking for is

<pre><code>Request.QueryString["QueryStringName"]
</code></pre>

and you can access it on views by adding <code>@</code> 

now look at my example,,, I generated a Url with QueryString 

<pre><code> var listURL = '@Url.RouteUrl(new { controller = "Sector", action = "List" , name = Request.QueryString["name"]})';
</code></pre>

the listURL value is <code>/Sector/List?name=value'</code>

and when <code>queryString</code> is empty 

listURL value is <code>/Sector/List</code>

blocks|key|1394068|text|实际上，您可以通过两种方式在MVC中捕获查询字符串.....|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1394069|public+ActionResult+CrazyMVC(string+knownQuerystring)
{

++//+This+is+the+known+query+string+captured+by+the+Controller+Action+Method+parameter+above
++string+myKnownQuerystring+=+knownQuerystring;

++//+This+is+what+I+call+the+mysterious+"unknown"+query+string
++//+It+is+not+known+because+the+Controller+isn't+capturing+it
++string+myUnknownQuerystring+=+Request.QueryString["unknownQuerystring"];

++return+Content(myKnownQuerystring+%2B+"+-+"+%2B+myUnknownQuerystring);

}|code-block|syntax|javascript|1394070|这将捕获两个查询strings...for示例：|1394071|/CrazyMVC?knownQuerystring=123&unknownQuerystring=456

Output:+123+-+456|1394072|不要问我为什么他们那样设计它。如果他们抛出单个查询字符串的整个Controller操作系统，而只是通过url-form-encoding返回URL的所有字符串/编码文件对象的捕获动态列表，这样您就可以在一次调用中轻松地访问它们，这会更有意义。如果可能的话，也许这里有人能证明这一点？|1394073|对我来说，控制器如何捕获查询字符串没有任何意义，但这确实意味着您捕获查询字符串的灵活性比它们教给您的更灵活。所以选择你的poison....both工作很好。|1394074|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Actually you can capture Query strings in MVC in two ways.....

<pre><code>public ActionResult CrazyMVC(string knownQuerystring)
{

 // This is the known query string captured by the Controller Action Method parameter above
 string myKnownQuerystring = knownQuerystring;

 // This is what I call the mysterious "unknown" query string
 // It is not known because the Controller isn't capturing it
 string myUnknownQuerystring = Request.QueryString["unknownQuerystring"];

 return Content(myKnownQuerystring + " - " + myUnknownQuerystring);

}
</code></pre>

This would capture both query strings...for example:

<pre><code>/CrazyMVC?knownQuerystring=123&amp;unknownQuerystring=456

Output: 123 - 456
</code></pre>

Don't ask me why they designed it that way. Would make more sense if they threw out the whole Controller action system for individual query strings and just returned a captured dynamic list of all strings/encoded file objects for the URL by url-form-encoding so you can easily access them all in one call. Maybe someone here can demonstrate that if its possible?

Makes no sense to me how Controllers capture query strings, but it does mean you have more flexibility to capture query strings than they teach you out of the box. So pick your poison....both work fine.

blocks|key|1609011|text|@Context.Request.Query"yourId“|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1609012|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

@Context.Request.Query[&quot;yourId&quot;]

blocks|key|1609033|text|这是.NET+6(和其他netcore)中的正确方法|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1609034|var参数=+Request.Query"IndexString"；|1609035|如果需要为字符串|1609036|string参数=+Request.Query"IndexString".ToString()；|1609037|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

This is the correct way in .NET 6 (and other netcore)
var Param = Request.Query[&quot;IndexString&quot;];
If need to be string
string Param = Request.Query[&quot;IndexString&quot;].ToString();

Under ASP.NET MVC are you supposed to pick up QueryString params the same way you do in ASP.NET WebForms? or does the <code>[AcceptVerbs(HttpVerbs.Get)]</code> declaration get used somehow?

ASP.NET MVC - Getting QueryString values

单元测试

路由

在ASP.NET MVC下，您是否应该像在ASP.NET WebForms中一样获取QueryString参数？还是会以某种方式使用[AcceptVerbs(HttpVerbs.Get)]声明？

问ASP.NET MVC -获取QueryString值
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.NET MVC -获取QueryString值EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.NET MVC -获取QueryString值
EN