blocks|key|349222|text|如果我无法找到我知道的方法，我通常做的是使用ILSpy来查看dll。运行它，删除所有“默认”程序集，只拖拽所需的资产(例如nhibernate的资产)，然后查看->搜索，如果您知道在组合框中选择type的类型名称，如果您知道选择成员的方法名称。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|349223|entityMap|0|LINK|mutability|MUTABLE|url|http://ilspy.net/^0|M|5|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If I can't find a method that I know is somewhere, what I normally do is use <a href="http://ilspy.net/" rel="nofollow">ILSpy</a> to take a peek at the dll. You run it, remove all the "default" assemblies, drag-n-drop only the asseblies you need (for example the ones of nhibernate), then View->Search and if you know the type name you select Type in the combo box, if you know the method name you select Member.

blocks|key|349251|text|要为实体(如QueryOver+)创建Employee，我们只需要ISession，并引用实体|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|349252|//+using+for+below+query
using+System;
using+MyProject.Entity;
using+MyProject.Data;+//+to+get+session|code-block|syntax|javascript|349253|有了上面的使用，我们可以有这个查询|349254|...
var+session+=+...+//+get+session
Employee+empl+=+null;

var+employee+=+session
++++.QueryOver<Employee>()
++++.Where(x+=>+x.ID+>+1)
++++.SelectList(list+=>+list
++++++++.Select(x+=>+x.ID)
++++++++.Select(x+=>+x.FirstName)
++++++++.Select(x+=>+x.LastName)
++++)
++++.Skip(10)
++++.Take(10)
++++.List<Employee>();|349255|要使用像限制一样的帮手，我们需要|349256|using+NHibernate.Criterion;|349257|这样我们就可以访问Restrictions，Projections，QueryOver.Of()|349258|var+disjunction+=+Restrictions.Disjunction();
var+projection+=+Projections.Sum("Age");
var+detachedQuery+=+QueryOver.Of<Employee>();|349259|摘要：|349260|要接触帮手，我们需要NHibernate.Criterion。|ordered-list-item|349261|要访问QueryOver+API，我们只需要QueryOver实例。因为这些方法是而不是扩展，所以它们是它的方法.|BOLD|349262|如果我们想通过QueryOver，我们只需参考标准：|349263|using+NHibernate.Criterion;

namespace+MyNamespace
{
++++public+static+class+MyExtension
++++{
++++++++public+static+QueryOver<T,+U>+AddPaging<T,+U>(QueryOver<T,+U>+queryOver)
++++++++{
++++++++++++queryOver
++++++++++++++++.Skip(10)
++++++++++++++++.Take(10);

++++++++++++return+queryOver;
++++++++}
++++}
}|349264|entityMap^0|6|9|J|8|X|8|0|0|0|0|0|0|9|C|M|B|Y|E|0|0|0|0|3|9|M|9|15|3|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1H|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1I|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|1J|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1K|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1L|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|1M|8|@$9|1N|A|1O|B|C]|$9|1P|A|1Q|B|C]|$9|1R|A|1S|B|C]]|D|@]|E|$]]|$1|U|3|V|5|H|7|1T|8|@]|D|@]|E|$I|J]]|$1|W|3|X|5|6|7|1U|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|10|7|1V|8|@]|D|@]|E|$]]|$1|11|3|12|5|10|7|1W|8|@$9|1X|A|1Y|B|C]|$9|1Z|A|20|B|C]|$9|21|A|22|B|13]]|D|@]|E|$]]|$1|14|3|15|5|6|7|23|8|@]|D|@]|E|$]]|$1|16|3|17|5|H|7|24|8|@]|D|@]|E|$I|J]]|$1|18|3|-4|5|6|7|25|8|@]|D|@]|E|$]]]|19|$]]

To create <code>QueryOver</code> for entity like <code>Employee</code>, we would need only <code>ISession</code>, and reference to entity

<pre><code>// using for below query
using System;
using MyProject.Entity;
using MyProject.Data; // to get session
</code></pre>

with above using, we can have this query

<pre><code>...
var session = ... // get session
Employee empl = null;

var employee = session
 .QueryOver&lt;Employee&gt;()
 .Where(x =&gt; x.ID &gt; 1)
 .SelectList(list =&gt; list
 .Select(x =&gt; x.ID)
 .Select(x =&gt; x.FirstName)
 .Select(x =&gt; x.LastName)
 )
 .Skip(10)
 .Take(10)
 .List&lt;Employee&gt;();
</code></pre>

To use helpers like Restrictions, we need

<pre><code>using NHibernate.Criterion;
</code></pre>

which will give us access to <code>Restrictions</code>, <code>Projections</code>, <code>QueryOver.Of()</code>

<pre><code>var disjunction = Restrictions.Disjunction();
var projection = Projections.Sum("Age");
var detachedQuery = QueryOver.Of&lt;Employee&gt;();
</code></pre>

Summary: 

<ol>
<li>to get access to helpers, we need NHibernate.Criterion. </li>
<li>To have access to <code>QueryOver</code> API - we need just <code>QueryOver</code> instance. Because these methods are not extensions, they are methods of it...</li>
</ol>

In case, we want to pass QueryOver, we just have to reference Criterion:

<pre><code>using NHibernate.Criterion;

namespace MyNamespace
{
 public static class MyExtension
 {
 public static QueryOver&lt;T, U&gt; AddPaging&lt;T, U&gt;(QueryOver&lt;T, U&gt; queryOver)
 {
 queryOver
 .Skip(10)
 .Take(10);

 return queryOver;
 }
 }
}
</code></pre>

blocks|key|1394825|text|如果我们希望将QueryOver传递给另一个方法，并对其执行一些筛选，则必须知道传递的类型。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1394826|下面的片段显示，我们有一些已知的接口IBusinessObject，，它具有ID和名称。这可能有助于为我们的通用params+T和U创建where条件，并应用一些与该接口相关的内容：|offset|length|style|BOLD|CODE|1394827|using+NHibernate.Criterion;

namespace+MyNamespace
{
++++public+interface+IBusinessObject
++++{
++++++++int+ID+{+get;+}
++++++++string+Name+{+get;+}
++++}

++++++++public+static+QueryOver<T,+U>+AddSomeFilter<T,+U>(QueryOver<T,+U>+queryOver)
++++++++++++where+T:+IBusinessObject
++++++++++++where+U:+IBusinessObject
++++++++{
++++++++++++//+here+we+can+play+with+ID,+and+Name
++++++++++++//+because+we+know+that+U+is+of+a+type+IBusinessObject
++++++++++++queryOver
++++++++++++++++.Where(x+=>+x.ID+>+1)
++++++++++++++++.Where(x+=>+x.Name+==+"Abc");

++++++++++++return+queryOver;
++++++++}
++++}
}|code-block|syntax|javascript|1394828|这可能是好的，但它可能会导致一些依赖。这就是为什么我喜欢使用标准API的原因。我们可以传递一些元数据，并创建更多的动态处理器：|1394829|public+static+class+MyExtension
{
++++public+static+ICriteria+AddLike(ICriteria+criteria,+string+property,+string+likeValue)
++++{
++++++++if+(property.IsNotEmpty())
++++++++{
++++++++++++criteria.Add(Restrictions.Like(property,+likeValue));
++++++++}
++++++++return+criteria;
++++}|1394830|要处理注释中的方法，我们可以这样做：|1394831|public+class+SearchCriteria
{
++++public+string+PropertyName+{+get;+set;+}
++++public+string+LikeValue+{+get;+set;+}
}

public+static+class+MyExtension
{
+++public+static+IQueryOver<Employee,+Employee>+ConstructQueryConditions(
++++++++this+IQueryOver<Employee,+Employee>+query
++++++++,+SearchCriteria+criteria)
++++{
++++++++if+(criteria.PropertyName.IsNotEmpty())
++++++++{
++++++++++++query.Where(Restrictions.Like(criteria.PropertyName,+criteria.LikeValue));
++++++++}
++++++++return+query;
++++}|1394832|entityMap^0|0|I|F|I|F|1W|5|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@$D|Z|E|10|F|G]|$D|11|E|12|F|H]|$D|13|E|14|F|H]]|9|@]|A|$]]|$1|I|3|J|5|K|7|15|8|@]|9|@]|A|$L|M]]|$1|N|3|O|5|6|7|16|8|@]|9|@]|A|$]]|$1|P|3|Q|5|K|7|17|8|@]|9|@]|A|$L|M]]|$1|R|3|S|5|6|7|18|8|@]|9|@]|A|$]]|$1|T|3|U|5|K|7|19|8|@]|9|@]|A|$L|M]]|$1|V|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|W|$]]

In case, that we want to pass QueryOver into another method, and execute some filtering over it, we MUST know the type, which is passed.

Below snippet shows, that we have some known interface <code>IBusinessObject</code>, which has ID and Name. That could help use to create <code>where</code> conditions for our generic params T and U - and apply some stuff related to that interface:

<pre><code>using NHibernate.Criterion;

namespace MyNamespace
{
 public interface IBusinessObject
 {
 int ID { get; }
 string Name { get; }
 }

 public static QueryOver&lt;T, U&gt; AddSomeFilter&lt;T, U&gt;(QueryOver&lt;T, U&gt; queryOver)
 where T: IBusinessObject
 where U: IBusinessObject
 {
 // here we can play with ID, and Name
 // because we know that U is of a type IBusinessObject
 queryOver
 .Where(x =&gt; x.ID &gt; 1)
 .Where(x =&gt; x.Name == "Abc");

 return queryOver;
 }
 }
}
</code></pre>

This could be fine, but it could lead to some dependency. That's why I honestly do like to use Criteria API. We can pass some Metadata, and create more dynamic processors:

<pre><code>public static class MyExtension
{
 public static ICriteria AddLike(ICriteria criteria, string property, string likeValue)
 {
 if (property.IsNotEmpty())
 {
 criteria.Add(Restrictions.Like(property, likeValue));
 }
 return criteria;
 }
</code></pre>

To process the method in the comment, we can do it like this:

<pre><code>public class SearchCriteria
{
 public string PropertyName { get; set; }
 public string LikeValue { get; set; }
}

public static class MyExtension
{
 public static IQueryOver&lt;Employee, Employee&gt; ConstructQueryConditions(
 this IQueryOver&lt;Employee, Employee&gt; query
 , SearchCriteria criteria)
 {
 if (criteria.PropertyName.IsNotEmpty())
 {
 query.Where(Restrictions.Like(criteria.PropertyName, criteria.LikeValue));
 }
 return query;
 }
</code></pre>

I am not able to find which namespace contains what for methods.

<ul>
<li>e.g. <code>NHibernate.IQueryOver</code> does not contain a definition for 'Add'
and no extension method 'Add' accepting a first argument of type .</li>
</ul>

Visual studio is not helping to get appropriate method on using because of extension method.

How can I know which methods, namespaces should be included?

Nhibernate 4 API documentation

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我无法找到哪个名称空间包含用于方法的内容。例如，NHibernate.IQueryOver不包含“Add”的定义，也不包含接受类型的第一个参数的扩展方法“Add”。由于使用扩展方法，Visual无助于获得适当的使用方法。我如何知道应该包括哪些方法、名称空间？

问Nhibernate 4 API文档
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Nhibernate 4 API文档EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Nhibernate 4 API文档
EN