@ -183,6 +183,65 @@
<param name= "message" > </param>
<param name= "innerException" > </param>
</member>
<member name= "T:LINGYUN.Abp.EventBus.CAP.AbpCAPMessageExtensions" >
<summary >
CAP消息扩展
</summary>
</member>
<member name= "M:LINGYUN.Abp.EventBus.CAP.AbpCAPMessageExtensions.TryGetTenantId(DotNetCore.CAP.Messages.Message,System.Guid@)" >
<summary >
尝试获取消息标头中的租户标识
</summary>
<param name= "message" > </param>
<param name= "tenantId" > </param>
<returns > </returns>
</member>
<member name= "M:LINGYUN.Abp.EventBus.CAP.AbpCAPMessageExtensions.GetTenantIdOrNull(DotNetCore.CAP.Messages.Message)" >
<summary >
获取消息标头中的租户标识
</summary>
<param name= "message" > </param>
<returns > </returns>
</member>
<member name= "T:LINGYUN.Abp.EventBus.CAP.AbpCAPSubscribeInvoker" >
<summary >
重写 ISubscribeInvoker 实现 Abp 租户集成
</summary>
</member>
<member name= "M:LINGYUN.Abp.EventBus.CAP.AbpCAPSubscribeInvoker.#ctor(Microsoft.Extensions.Logging.ILoggerFactory,System.IServiceProvider,DotNetCore.CAP.Serialization.ISerializer,Volo.Abp.MultiTenancy.ICurrentTenant)" >
<summary >
AbpCAPSubscribeInvoker
</summary>
<param name= "loggerFactory" > </param>
<param name= "serviceProvider" > </param>
<param name= "serializer" > </param>
<param name= "currentTenant" > </param>
</member>
<member name= "M:LINGYUN.Abp.EventBus.CAP.AbpCAPSubscribeInvoker.InvokeAsync(DotNetCore.CAP.Internal.ConsumerContext,System.Threading.CancellationToken)" >
<summary >
调用订阅者方法
</summary>
<param name= "context" > </param>
<param name= "cancellationToken" > </param>
<returns > </returns>
</member>
<member name= "M:LINGYUN.Abp.EventBus.CAP.AbpCAPSubscribeInvoker.GetInstance(System.IServiceProvider,DotNetCore.CAP.Internal.ConsumerContext)" >
<summary >
获取事件处理类实例
</summary>
<param name= "provider" > </param>
<param name= "context" > </param>
<returns > </returns>
</member>
<member name= "M:LINGYUN.Abp.EventBus.CAP.AbpCAPSubscribeInvoker.ExecuteWithParameterAsync(LINGYUN.Abp.EventBus.CAP.Internal.ObjectMethodExecutor,System.Object,System.Object[])" >
<summary >
通过给定的类型实例与参数调用订阅者方法
</summary>
<param name= "executor" > </param>
<param name= "class" > </param>
<param name= "parameter" > </param>
<returns > </returns>
</member>
<member name= "T:LINGYUN.Abp.EventBus.CAP.CAPDistributedEventBus" >
<summary >
CAP分布式事件总线
@ -213,14 +272,32 @@
本地事件集合
</summary>
</member>
<member name= "M:LINGYUN.Abp.EventBus.CAP.CAPDistributedEventBus.#ctor(Microsoft.Extensions.DependencyInjection.IServiceScopeFactory,Microsoft.Extensions.Options.IOptions{Volo.Abp.EventBus.Distributed.AbpDistributedEventBusOptions},DotNetCore.CAP.ICapPublisher,Volo.Abp.MultiTenancy.ICurrentTenant,LINGYUN.Abp.EventBus.CAP.ICustomDistributedEventSubscriber)" >
<member name= "P:LINGYUN.Abp.EventBus.CAP.CAPDistributedEventBus.CurrentUser" >
<summary >
当前用户
</summary>
</member>
<member name= "P:LINGYUN.Abp.EventBus.CAP.CAPDistributedEventBus.CurrentClient" >
<summary >
当前客户端
</summary>
</member>
<member name= "P:LINGYUN.Abp.EventBus.CAP.CAPDistributedEventBus.CancellationTokenProvider" >
<summary >
取消令牌
</summary>
</member>
<member name= "M:LINGYUN.Abp.EventBus.CAP.CAPDistributedEventBus.#ctor(Microsoft.Extensions.DependencyInjection.IServiceScopeFactory,Microsoft.Extensions.Options.IOptions{Volo.Abp.EventBus.Distributed.AbpDistributedEventBusOptions},DotNetCore.CAP.ICapPublisher,Volo.Abp.Users.ICurrentUser,Volo.Abp.Clients.ICurrentClient,Volo.Abp.MultiTenancy.ICurrentTenant,Volo.Abp.Threading.ICancellationTokenProvider,LINGYUN.Abp.EventBus.CAP.ICustomDistributedEventSubscriber)" >
<summary >
constructor
</summary>
<param name= "serviceScopeFactory" > </param>
<param name= "distributedEventBusOptions" > </param>
<param name= "capPublisher" > </param>
<param name= "currentUser" > </param>
<param name= "currentTenant" > </param>
<param name= "currentClient" > </param>
<param name= "cancellationTokenProvider" > </param>
<param name= "customDistributedEventSubscriber" > </param>
</member>
<member name= "M:LINGYUN.Abp.EventBus.CAP.CAPDistributedEventBus.Subscribe(System.Type,Volo.Abp.EventBus.IEventHandlerFactory)" >
@ -300,6 +377,62 @@
<param name= "eventType" > </param>
<param name= "factory" > </param>
</member>
<member name= "M:LINGYUN.Abp.EventBus.CAP.Internal.ObjectMethodExecutor.Execute(System.Object,System.Object[])" >
<summary >
Executes the configured method on <paramref name= "target" /> . This can be used whether or not
the configured method is asynchronous.
</summary>
<remarks >
Even if the target method is asynchronous, it's desirable to invoke it using Execute rather than
ExecuteAsync if you know at compile time what the return type is, because then you can directly
"await" that value (via a cast), and then the generated code will be able to reference the
resulting awaitable as a value-typed variable. If you use ExecuteAsync instead, the generated
code will have to treat the resulting awaitable as a boxed object, because it doesn't know at
compile time what type it would be.
</remarks>
<param name= "target" > The object whose method is to be executed.</param>
<param name= "parameters" > Parameters to pass to the method.</param>
<returns > The method return value.</returns>
</member>
<member name= "M:LINGYUN.Abp.EventBus.CAP.Internal.ObjectMethodExecutor.ExecuteAsync(System.Object,System.Object[])" >
<summary >
Executes the configured method on <paramref name= "target" /> . This can only be used if the configured
method is asynchronous.
</summary>
<remarks >
If you don't know at compile time the type of the method's returned awaitable, you can use ExecuteAsync,
which supplies an awaitable-of-object. This always works, but can incur several extra heap allocations
as compared with using Execute and then using "await" on the result value typecasted to the known
awaitable type. The possible extra heap allocations are for:
1. The custom awaitable (though usually there's a heap allocation for this anyway, since normally
it's a reference type, and you normally create a new instance per call).
2. The custom awaiter (whether or not it's a value type, since if it's not, you need a new instance
of it, and if it is, it will have to be boxed so the calling code can reference it as an object).
3. The async result value, if it's a value type (it has to be boxed as an object, since the calling
code doesn't know what type it's going to be).
</remarks>
<param name= "target" > The object whose method is to be executed.</param>
<param name= "parameters" > Parameters to pass to the method.</param>
<returns > An object that you can "await" to get the method return value.</returns>
</member>
<member name= "T:LINGYUN.Abp.EventBus.CAP.Internal.ObjectMethodExecutorAwaitable" >
<summary >
Provides a common awaitable structure that <see cref= "M:LINGYUN.Abp.EventBus.CAP.Internal.ObjectMethodExecutor.ExecuteAsync(System.Object,System.Object[])" /> can
return, regardless of whether the underlying value is a System.Task, an FSharpAsync, or an
application-defined custom awaitable.
</summary>
</member>
<member name= "T:LINGYUN.Abp.EventBus.CAP.Internal.ObjectMethodExecutorFSharpSupport" >
<summary >
Helper for detecting whether a given type is FSharpAsync`1, and if so, supplying
an <see cref= "T:System.Linq.Expressions.Expression" /> for mapping instances of that type to a C# awaitable.
</summary>
<remarks >
The main design goal here is to avoid taking a compile-time dependency on
FSharp.Core.dll, because non-F# applications wouldn't use it. So all the references
to FSharp types have to be constructed dynamically at runtime.
</remarks>
</member>
<member name= "T:Microsoft.Extensions.DependencyInjection.ServiceCollectionExtensions" >
<summary >
CAP ServiceCollectionExtensions
cKey
5 years ago
GitHub