我有一组在Application实例中使用的通用电子邮件类。 它们都共享相同的接口，但我需要能够(可选地(将另一个"通用"类型的实例"填充"为属性。
从这里开始：鉴于这个起点...
请注意，MyApplication 从所有 3 个属性开始。 而且，由于 DistributionListProvider 是唯一配置的 IInstanceProvider...不会出现任何问题。
public class MyApplication : IMyApplication
{
#region notifications
[SetterProperty]
public IEmailNotification RequestToFlowEmailNotification { get; set; }
[SetterProperty]
public IEmailNotification ApprovalToFlowEmailNotification{ get; set; }
#endregion
#region instance providers
[SetterProperty]
public IInstanceProvider DistributionListProvider { get; set; }
#endregion
}
public class RequestToFlowEmailNotification : IEmailNotification
{
#region <Properties>
[SetterProperty]
public IInstanceProvider DistributionListProvider { get; set; }
#endregion
}
public class ApprovalToFlowEmailNotification : IEmailNotification
{
}
public class DistributionListProvider : ComponentProviderBase, IInstanceProvider
{
}
让我们添加：现在让我们创建另一个IInstanceProvider并将其添加到应用程序中...
但首先，请注意IEmailNotification和IInstanceProvider是通用类型，而不是"泛型类型"。这意味着它们不是EmailNotificationFor<T>类型。 这会在注册表中配置它们的方式有所不同。
// NOW...LETS ADD THIS !!
public class AuthorizationToFlowMeterDocumentRecallProvider : ComponentProviderBase, IInstanceProvider
{
}
public class MyApplication : IMyApplication
{
#region notifications
[SetterProperty]
public IEmailNotification RequestToFlowEmailNotification { get; set; }
[SetterProperty]
public IEmailNotification ApprovalToFlowEmailNotification{ get; set; }
#endregion
#region instance providers
[SetterProperty]
public IInstanceProvider DistributionListProvider { get; set; }
[SetterProperty]
public IInstanceProvider AuthorizationToFlowMeterDocumentRecallProvider{ get; set; }
#endregion
}
此时结构图不再知道如何填充...
- RequestToFlowEmailNotification.DistributionListProvider
问：如何更新注册表以强制结构图正确填写？
下面是我的整个注册表...
注意：
我不想设置默认值...有没有办法在不设置默认值的情况下做到这一点？
public ContainerRegistry()
{
Scan(
scan =>
{
scan.TheCallingAssembly();
scan.WithDefaultConventions();
scan.LookForRegistries();
scan.SingleImplementationsOfInterface();
});
// ------------
// UNIT OF WORK
// ------------
// DbContext
For<DbContext>().Use<MeasurementContractsDbContext>();
// UnitOfWork
For<IMeasurementContractsUnitOfWork>().Use<MeasurementContractsUnitOfWork>();
// GenericRepository
For(typeof(ICompositeRepository<>)).Use(typeof(GenericRepository<>));
// --------
// HELPERS
// --------
For<IWindowsIdentityHelper>().Use<WindowsIdentityHelper>();
For<ISmtpClientHelper>().Use<SmtpClientHelper>()
.Ctor<ISmtpClient>().Is(new SmtpClient());
For<IPdfConverterHelper>().Use<PdfConverterHelper>()
.Ctor<IPdfConverterClient>().Is(new SelectPdfUrlConverterClient());
// WARNING: Do not remove without replacing it with "some kind of" IConstructorSelector, so that, Unit Testing can be done
For<IDataServiceFor<EmployeeData>>()
.Use(x => new EmployeeDataService(new ODataProxyV4())); //<-- uses this constructor
// --------
// WORKFLOW
// ---------
For<IWorkflowProvider>().Use<WorkflowProvider>()
.Ctor<Assembly>().Is(Assembly.GetExecutingAssembly());
// --------
// MANAGERS
// --------
For<IManager<Device>>().Use<DeviceManager>();
For<IManager<Favorite>>().Use<FavoritesManager>();
For<IManager<User>>().Use<UserManager>();
// --------
// DEPENDENCY MANAGERS
// --------
For<IDocumentDependency>().Use<DeviceAffinityProvider>();
// --------
// TRANSFORMERS
// --------
For<IXmlTransformerFor<AuthorizationToFlowMeterDocumentXmlDataSet>>().Use<AuthorizationToFlowMeterDocumentXmlTransformer>();
For<IXmlTransformerFor<FirstDeliveryNoticeDocumentXmlDataSet>>().Use<FirstDeliveryNoticeDocumentXmlTransformer>();
For<IXmlTransformerFor<RequestToFlowMeterDocumentXmlDataSet>>().Use<RequestToFlowMeterDocumentXmlTransformer>();
// --------
// PROVIDERS: DataItem Providers
// --------
For<IDataItemProviderFor<EmployeeData>>().Use<EmployeeDataProvider>();
// --------
// PROVIDERS: Document Providers
// --------
For<IDataItemProviderFor<RequestToFlowMeterDocument>>().Use<RequestToFlowMeterDocumentProvider>();
For<IDataItemProviderFor<AuthorizationToFlowMeterDocument>>().Use<AuthorizationToFlowMeterDocumentProvider>();
For<IDataItemProviderFor<FirstDeliveryNoticeDocument>>().Use<FirstDeliveryNoticeDocumentProvider>();
// --------
// COMMANDS
// --------
For<IAdminUpdateCommandFor<AuthorizationToFlowMeterDocument>>().Use<AuthorizationToFlowMeterDocumentAdminUpdateCommand>();
// -----------
// APPLICATION
// -----------
For<IMyApplication>().Use<MyApplication>()
// Instance Provider
.Setter(x => x.DistributionListProvider).Is<DistributionListProvider>()
.Setter(x => x.AuthorizationToFlowMeterDocumentRecallProvider).Is<AuthorizationToFlowMeterDocumentRecallProvider>()
// Email Notifications
.Setter(x => x.ApprovalToFlowEmailNotification).Is<ApprovalToFlowEmailNotification>()
.Setter(x => x.DenialToFlowEmailNotification).Is<DenialToFlowEmailNotification>()
.Setter(x => x.ApprovalToFlowRecalledEmailNotification).Is<ApprovalToFlowRecalledEmailNotification>()
.Setter(x => x.RequestToFlowEmailNotification).Is<RequestToFlowEmailNotification>()
.Setter(x => x.FirstDeliveryNoticeEmailNotification).Is<FirstDeliveryNoticeEmailNotification>();
}
使用[SetterProperty]属性，StructureMap 将尝试为属性构建并附加值，作为对象构造的一部分。
但是，setter 属性需要默认实现，因为它无法确定在有多个实现时打算使用哪个实现，尤其是在未添加默认实现的情况下。
有了RequestToFlowEmailNotification.DistributionListProvider容器不知道要使用哪种实现。
若要覆盖此行为，请对RequestToFlowEmailNotification.DistributionListProvider使用内联资源库配置
//...
.Setter(x => x.RequestToFlowEmailNotification)
.Is<RequestToFlowEmailNotification>(_ =>
_.Setter(d => d.DistributionListProvider)
.Is<DistributionListProvider>()); //<<-- change to which ever one is needed
请注意Setter配置的链接，以便设置RequestToFlowEmailNotification，然后设置内部DistributionListProvider