如何设置 StructureMap 来解决 Windows 服务中的依赖关系？
我有一个使用 ASP.NET MVC 1.0 构建的网站。它使用 Structuremap 作为 IOC 容器。 如果我像这样在 Application_Start 上注册 IOC 部分，效果会很好：
ObjectFactory.Initialize(service =>
{
service.ForRequestedType<IOrderRepository>()
.TheDefaultIsConcreteType<OrderRepository>()
.CacheBy(InstanceScope.PerRequest);
});
我必须在 Windows 服务中使用相同的后端。
该服务中有一些同时访问 OrderRepository 的计时器，因此线程是这里的一个问题。
我的第一个想法是在服务的构造函数中注册它，如下所示：
public Service1()
{
ObjectFactory.Initialize(service =>
{
service.ForRequestedType<IOrderRepository>()
.TheDefaultIsConcreteType<OrderRepository>()
.CacheBy(InstanceScope.PerRequest);
});
}
这是缓存的正确位置和正确参数吗？
阅读Structuremap的文档，我认为最安全的方法是使用缓存的默认设置：
PerRequest - 默认操作。将为每个请求创建一个新实例。
我的印象是 PerRequest 意味着 HttpContext，但那是另一个条目：
HttpContext - 将为每个 HttpContext 创建一个实例。缓存
HttpContext.Items集合中的实例。
I have a web that was build using ASP.NET MVC 1.0. It uses Structuremap as an IOC container.
The IOC part works nice if I register it on Application_Start like this:
ObjectFactory.Initialize(service =>
{
service.ForRequestedType<IOrderRepository>()
.TheDefaultIsConcreteType<OrderRepository>()
.CacheBy(InstanceScope.PerRequest);
});
I have to use the same backend in a Windows Service.
The service has some timers in it that access OrderRepository simultaneously, so threading is an issue here.
My first idea is to register it in the constructor of the service like this:
public Service1()
{
ObjectFactory.Initialize(service =>
{
service.ForRequestedType<IOrderRepository>()
.TheDefaultIsConcreteType<OrderRepository>()
.CacheBy(InstanceScope.PerRequest);
});
}
Is this the right place and the right parameter for caching?
Reading the documentation of Structuremap, I think the safest way is to use the default setting for Caching:
PerRequest - The default operation. A new instance will be created for each request.
I had the impression that PerRequest meant HttpContext, but thats another entry:
HttpContext - A single instance will be created for each HttpContext. Caches the instances in the
HttpContext.Itemscollection.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
根据本文：http://msdn.microsoft.com/en -us/library/system.serviceprocess.servicebase.aspx
听起来构造函数是第一次设置结构图的方法。
Per this article: http://msdn.microsoft.com/en-us/library/system.serviceprocess.servicebase.aspx
It sounds like constructor is the way to go for the first time setup of structure map.
老实说，这更像是“我的两分钱”贡献，实际上是试图给出明确的答案，因为我开发 Windows 服务已经有一段时间了，但现在就这样了。
与 ASP .Net MVC 应用程序进行类比，其中容器的配置将在 Global.asax 类的 Application_Start 方法中进行，然后将配置的容器注入自定义控制器工厂；我相信您可以尝试在可执行文件的 Main 函数中配置所有内容，而不是在服务的构造函数中配置所有内容，因为它只会运行一次，然后将配置的容器注入到服务的构造函数中。
我认为通过这样做，您可以引导所有 Composition Root 的内容服务中的应用程序和代码将专注于做它应该做的事情。
就像我说的，已经有一段时间了，我从来没有使用 IoC 容器或 DI 来做这件事。祝你好运！
To be honest this is more of a "my two cents" contribution that actually trying to give a definitive answer since it's been a while since I developed a Windows Service but here it goes.
Making an analogy from an ASP .Net MVC app in which the configuration of the container would take place in the Global.asax class' Application_Start method and then inject the configured container into a custom Controller Factory; I believe you could, instead of configuring everything in the service's constructor, try to do it in the Main function of the executable, since it will only run once, and then inject the configured container in the constructor of the service.
I think that by doing it that way you are bootstrapping everything Composition Root of the application and the code within the service will focus on doing what it is supposed to do.
Like I said it's been a while and I never did it with an IoC container or DI for that matter. Best of lucks!