blocks|key|3269248|text|您需要实现自定义ServiceHostFactory、ServiceHost和IInstanceProvider的组合。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3269249|给定一个具有此构造函数签名的服务：|3269250|public+MyService(IDependency+dep)|code-block|syntax|javascript|3269251|下面是一个可以启动MyService的示例：|3269252|public+class+MyServiceHostFactory+:+ServiceHostFactory
{
++++private+readonly+IDependency+dep;

++++public+MyServiceHostFactory()
++++{
++++++++this.dep+=+new+MyClass();
++++}

++++protected+override+ServiceHost+CreateServiceHost(Type+serviceType,
++++++++Uri[]+baseAddresses)
++++{
++++++++return+new+MyServiceHost(this.dep,+serviceType,+baseAddresses);
++++}
}

public+class+MyServiceHost+:+ServiceHost
{
++++public+MyServiceHost(IDependency+dep,+Type+serviceType,+params+Uri[]+baseAddresses)
++++++++:+base(serviceType,+baseAddresses)
++++{
++++++++if+(dep+==+null)
++++++++{
++++++++++++throw+new+ArgumentNullException("dep");
++++++++}

++++++++foreach+(var+cd+in+this.ImplementedContracts.Values)
++++++++{
++++++++++++cd.Behaviors.Add(new+MyInstanceProvider(dep));
++++++++}
++++}
}

public+class+MyInstanceProvider+:+IInstanceProvider,+IContractBehavior
{
++++private+readonly+IDependency+dep;

++++public+MyInstanceProvider(IDependency+dep)
++++{
++++++++if+(dep+==+null)
++++++++{
++++++++++++throw+new+ArgumentNullException("dep");
++++++++}

++++++++this.dep+=+dep;
++++}

++++#region+IInstanceProvider+Members

++++public+object+GetInstance(InstanceContext+instanceContext,+Message+message)
++++{
++++++++return+this.GetInstance(instanceContext);
++++}

++++public+object+GetInstance(InstanceContext+instanceContext)
++++{
++++++++return+new+MyService(this.dep);
++++}

++++public+void+ReleaseInstance(InstanceContext+instanceContext,+object+instance)
++++{
++++++++var+disposable+=+instance+as+IDisposable;
++++++++if+(disposable+!=+null)
++++++++{
++++++++++++disposable.Dispose();
++++++++}
++++}

++++#endregion

++++#region+IContractBehavior+Members

++++public+void+AddBindingParameters(ContractDescription+contractDescription,+ServiceEndpoint+endpoint,+BindingParameterCollection+bindingParameters)
++++{
++++}

++++public+void+ApplyClientBehavior(ContractDescription+contractDescription,+ServiceEndpoint+endpoint,+ClientRuntime+clientRuntime)
++++{
++++}

++++public+void+ApplyDispatchBehavior(ContractDescription+contractDescription,+ServiceEndpoint+endpoint,+DispatchRuntime+dispatchRuntime)
++++{
++++++++dispatchRuntime.InstanceProvider+=+this;
++++}

++++public+void+Validate(ContractDescription+contractDescription,+ServiceEndpoint+endpoint)
++++{
++++}

++++#endregion
}|3269253|在MyService.svc文件中注册MyServiceHostFactory，或者在代码中直接使用MyServiceHost实现自托管。|3269254|您可以很容易地推广这种方法，实际上一些DI容器已经为您完成了这项工作(提示:Windsor的WCF+Facility)。|3269255|entityMap^0|8|I|R|B|13|H|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|13|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|14|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|15|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|17|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|18|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|V|$]]

You'll need to implement a combination of custom <code>ServiceHostFactory</code>, <code>ServiceHost</code> and <code>IInstanceProvider</code>.

Given a service with this constructor signature:

<pre><code>public MyService(IDependency dep)
</code></pre>

Here's an example that can spin up MyService:

<pre><code>public class MyServiceHostFactory : ServiceHostFactory
{
 private readonly IDependency dep;

 public MyServiceHostFactory()
 {
 this.dep = new MyClass();
 }

 protected override ServiceHost CreateServiceHost(Type serviceType,
 Uri[] baseAddresses)
 {
 return new MyServiceHost(this.dep, serviceType, baseAddresses);
 }
}

public class MyServiceHost : ServiceHost
{
 public MyServiceHost(IDependency dep, Type serviceType, params Uri[] baseAddresses)
 : base(serviceType, baseAddresses)
 {
 if (dep == null)
 {
 throw new ArgumentNullException("dep");
 }

 foreach (var cd in this.ImplementedContracts.Values)
 {
 cd.Behaviors.Add(new MyInstanceProvider(dep));
 }
 }
}

public class MyInstanceProvider : IInstanceProvider, IContractBehavior
{
 private readonly IDependency dep;

 public MyInstanceProvider(IDependency dep)
 {
 if (dep == null)
 {
 throw new ArgumentNullException("dep");
 }

 this.dep = dep;
 }

 #region IInstanceProvider Members

 public object GetInstance(InstanceContext instanceContext, Message message)
 {
 return this.GetInstance(instanceContext);
 }

 public object GetInstance(InstanceContext instanceContext)
 {
 return new MyService(this.dep);
 }

 public void ReleaseInstance(InstanceContext instanceContext, object instance)
 {
 var disposable = instance as IDisposable;
 if (disposable != null)
 {
 disposable.Dispose();
 }
 }

 #endregion

 #region IContractBehavior Members

 public void AddBindingParameters(ContractDescription contractDescription, ServiceEndpoint endpoint, BindingParameterCollection bindingParameters)
 {
 }

 public void ApplyClientBehavior(ContractDescription contractDescription, ServiceEndpoint endpoint, ClientRuntime clientRuntime)
 {
 }

 public void ApplyDispatchBehavior(ContractDescription contractDescription, ServiceEndpoint endpoint, DispatchRuntime dispatchRuntime)
 {
 dispatchRuntime.InstanceProvider = this;
 }

 public void Validate(ContractDescription contractDescription, ServiceEndpoint endpoint)
 {
 }

 #endregion
}
</code></pre>

Register MyServiceHostFactory in your MyService.svc file, or use MyServiceHost directly in code for self-hosting scenarios.

You can easily generalize this approach, and in fact some DI Containers have already done this for you (cue: Windsor's WCF Facility).

blocks|key|316303|text|马克对IInstanceProvider的回答是正确的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|316304|您也可以使用自定义属性(比如MyInstanceProviderBehaviorAttribute)，而不是使用自定义ServiceHostFactory。从Attribute派生它，使其实现IServiceBehavior并实现IServiceBehavior.ApplyDispatchBehavior方法，如下所示|316305|//+YourInstanceProvider+implements+IInstanceProvider
var+instanceProvider+=+new+YourInstanceProvider(<yourargs>);

foreach+(ChannelDispatcher+dispatcher+in+serviceHostBase.ChannelDispatchers)
{
++++foreach+(var+epDispatcher+in+dispatcher.Endpoints)
++++{
++++++++//+this+registers+your+custom+IInstanceProvider
++++++++epDispatcher.DispatchRuntime.InstanceProvider+=+instanceProvider;
++++}
}|code-block|syntax|javascript|316306|然后，将该属性应用于服务实现类|316307|[ServiceBehavior]
[MyInstanceProviderBehavior(<params+as+you+want>)]
public+class+MyService+:+IMyContract|316308|第三个选项:您还可以使用配置文件应用服务行为。|316309|entityMap^0|3|H|0|E|Z|27|9|2O|G|37|12|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]|$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|17|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|18|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|19|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|T|$]]

Mark's answer with the <code>IInstanceProvider</code> is correct.

Instead of using the custom ServiceHostFactory you could also use a custom attribute (say <code>MyInstanceProviderBehaviorAttribute</code>). Derive it from <code>Attribute</code>, make it implement <code>IServiceBehavior</code> and implement the <code>IServiceBehavior.ApplyDispatchBehavior</code> method like 

<pre><code>// YourInstanceProvider implements IInstanceProvider
var instanceProvider = new YourInstanceProvider(&lt;yourargs&gt;);

foreach (ChannelDispatcher dispatcher in serviceHostBase.ChannelDispatchers)
{
 foreach (var epDispatcher in dispatcher.Endpoints)
 {
 // this registers your custom IInstanceProvider
 epDispatcher.DispatchRuntime.InstanceProvider = instanceProvider;
 }
}
</code></pre>

Then, apply the attribute to your service implementation class

<pre><code>[ServiceBehavior]
[MyInstanceProviderBehavior(&lt;params as you want&gt;)]
public class MyService : IMyContract
</code></pre>

The third option: you can also apply a service behavior using the configuration file.

blocks|key|3055673|text|我根据Mark的回答工作，但(至少对于我的场景)，它是不必要的复杂。其中一个ServiceHost构造函数接受服务的一个实例，您可以直接从ServiceHostFactory实现传入该实例。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3055674|为了利用Mark的示例，它将如下所示：|3055675|public+class+MyServiceHostFactory+:+ServiceHostFactory
{
++++private+readonly+IDependency+_dep;

++++public+MyServiceHostFactory()
++++{
++++++++_dep+=+new+MyClass();
++++}

++++protected+override+ServiceHost+CreateServiceHost(Type+serviceType,
++++++++Uri[]+baseAddresses)
++++{
++++++++var+instance+=+new+MyService(_dep);
++++++++return+new+MyServiceHost(instance,+serviceType,+baseAddresses);
++++}
}

public+class+MyServiceHost+:+ServiceHost
{
++++public+MyServiceHost(MyService+instance,+Type+serviceType,+params+Uri[]+baseAddresses)
++++++++:+base(instance,+baseAddresses)
++++{
++++}
}|code-block|syntax|javascript|3055676|entityMap^0|12|B|1X|I|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

I worked from Mark's answer, but (for my scenario at least), it was needlessly complex. One of the <code>ServiceHost</code> constructors accepts an instance of the service, which you can pass in directly from the <code>ServiceHostFactory</code> implementation. 

To piggyback off Mark's example, it would look like this:

<pre><code>public class MyServiceHostFactory : ServiceHostFactory
{
 private readonly IDependency _dep;

 public MyServiceHostFactory()
 {
 _dep = new MyClass();
 }

 protected override ServiceHost CreateServiceHost(Type serviceType,
 Uri[] baseAddresses)
 {
 var instance = new MyService(_dep);
 return new MyServiceHost(instance, serviceType, baseAddresses);
 }
}

public class MyServiceHost : ServiceHost
{
 public MyServiceHost(MyService instance, Type serviceType, params Uri[] baseAddresses)
 : base(instance, baseAddresses)
 {
 }
}
</code></pre>

blocks|key|3055691|text|我们面临着同样的问题，并通过以下方式解决了它。这是一个简单的解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3055692|在Visual+Studio中，只需创建一个普通的WCF服务应用程序并移除其接口即可。保留.cs文件(只需将其重命名)并打开cs文件，并将接口的名称替换为实现服务逻辑的原始类名(这样，服务类使用继承并替换您的实际实现)。添加一个调用基类的构造函数的默认构造函数，如下所示：|3055693|public+class+Service1+:+MyLogicNamespace.MyService
{
++++public+Service1()+:+base(new+MyDependency1(),+new+MyDependency2())+{}
}|code-block|syntax|javascript|3055694|MyService基类是服务的实际实现。此基类不应具有无参数构造函数，而应仅具有接受依赖项的参数的构造函数。|3055695|服务应该使用这个类而不是原始的MyService。|3055696|这是一个简单的解决方案，效果很好:-D|3055697|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|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$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|$]]

We were facing this same problem and have solved it in the following manner. It is a simple solution. 

In Visual Studio just create a normal WCF service application and remove it's interface. Leave the .cs file in place (just rename it) and open that cs file and replace the name of the interface with your original class name which implements the service logic (this way the service class uses inheritance and replaces your actual implementation). Add a default constructor that calls the base class's constructors, like this: 

<pre><code>public class Service1 : MyLogicNamespace.MyService
{
 public Service1() : base(new MyDependency1(), new MyDependency2()) {}
}
</code></pre>

The MyService base class is the actual implementation of the service. This base class should not have a parameterless constructor, but only constructors with parameters that accept the dependencies. 

The service should use this class instead of the original MyService. 

It's a simple solution and works like a charm :-D

blocks|key|311351|text|我使用我的类型的静态变量。我不确定这是不是最好的方法，但它对我很有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|311352|public+class+MyServer
{+++
++++public+static+string+CustomerDisplayName;
++++...
}|code-block|syntax|javascript|311353|当我实例化服务主机时，我执行以下操作：|311354|protected+override+void+OnStart(string[]+args)
{
++++MyServer.CustomerDisplayName+=+"Test+customer";

++++...

++++selfHost+=+new+ServiceHost(typeof(MyServer),+baseAddress);

++++....
}|311355|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I use static variables of my type. Not sure if this is the best way, but it works for me:

<pre><code>public class MyServer
{ 
 public static string CustomerDisplayName;
 ...
}
</code></pre>

When I instantiate service host I do the following:

<pre><code>protected override void OnStart(string[] args)
{
 MyServer.CustomerDisplayName = "Test customer";

 ...

 selfHost = new ServiceHost(typeof(MyServer), baseAddress);

 ....
}
</code></pre>

blocks|key|3269338|text|您可以简单地创建Service的实例并将该实例传递给ServiceHost对象。您唯一需要做的就是为您的服务添加一个[ServiceBehaviour]属性，并用[DataContract]属性标记所有返回的对象。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3269339|这是一个模型：|3269340|namespace+Service
{
++++[ServiceContract]
++++[ServiceBehavior(InstanceContextMode+=+InstanceContextMode.Single)]
++++public+class+MyService
++++{
++++++++private+readonly+IDependency+_dep;

++++++++public+MyService(IDependency+dep)
++++++++{
++++++++++++_dep+=+dep;
++++++++}

++++++++public+MyDataObject+GetData()
++++++++{
++++++++++++return+_dep.GetData();
++++++++}
++++}

++++[DataContract]
++++public+class+MyDataObject
++++{
++++++++public+MyDataObject(string+name)
++++++++{
++++++++++++Name+=+name;
++++++++}

++++++++public+string+Name+{+get;+private+set;+}
++++}

++++public+interface+IDependency
++++{
++++++++MyDataObject+GetData();
++++}
}|code-block|syntax|javascript|3269341|和用法：|3269342|var+dep+=+new+Dependecy();
var+myService+=+new+MyService(dep);
var+host+=+new+ServiceHost(myService);

host.Open();|3269343|我希望这会让一些人的生活变得更轻松。|3269344|entityMap^0|8|7|Q|B|1M|I|29|E|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|13|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|14|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|15|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|17|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|T|$]]

You can simply create and instance of your <code>Service</code> and pass that instance to the <code>ServiceHost</code> object. The only thing you have to do is to add a <code>[ServiceBehaviour]</code> attribute for your service and mark all returned objects with <code>[DataContract]</code> attribute.

Here is a mock up:

<pre><code>namespace Service
{
 [ServiceContract]
 [ServiceBehavior(InstanceContextMode = InstanceContextMode.Single)]
 public class MyService
 {
 private readonly IDependency _dep;

 public MyService(IDependency dep)
 {
 _dep = dep;
 }

 public MyDataObject GetData()
 {
 return _dep.GetData();
 }
 }

 [DataContract]
 public class MyDataObject
 {
 public MyDataObject(string name)
 {
 Name = name;
 }

 public string Name { get; private set; }
 }

 public interface IDependency
 {
 MyDataObject GetData();
 }
}
</code></pre>

and the usage:

<pre><code>var dep = new Dependecy();
var myService = new MyService(dep);
var host = new ServiceHost(myService);

host.Open();
</code></pre>

I hope this will make life easier for someone.

blocks|key|311366|text|这是一个非常有用的解决方案-特别是对于WCF编程新手来说。我确实想为任何可能将其用于IIS托管服务的用户提供一点提示。MyServiceHost需要继承WebServiceHost，，而不仅仅是ServiceHost。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|311367|public+class+MyServiceHost+:+WebServiceHost
{
++++public+MyServiceHost(MyService+instance,+Type+serviceType,+params+Uri[]+baseAddresses)
++++++++:+base(instance,+baseAddresses)
++++{
++++}
}|code-block|syntax|javascript|311368|这将为IIS中的端点创建所有必要的绑定等。|311369|entityMap^0|24|E|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

This was a very helpful solution - especially for someone who is a novice WCF coder. I did want to post a little tip for any users who might be using this for an IIS-hosted service. MyServiceHost needs to inherit WebServiceHost, not just ServiceHost.

<pre><code>public class MyServiceHost : WebServiceHost
{
 public MyServiceHost(MyService instance, Type serviceType, params Uri[] baseAddresses)
 : base(instance, baseAddresses)
 {
 }
}
</code></pre>

This will create all the necessary bindings, etc for your endpoints in IIS.

blocks|key|3055776|text|去他的，…我混合了依赖注入和服务定位器模式(但大多数仍然是依赖注入，它甚至发生在构造函数中，这意味着您可以拥有只读状态)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3055777|public+class+MyService+:+IMyService
{
++++private+readonly+Dependencies+_dependencies;

++++//+set+this+before+creating+service+host.+this+can+use+your+IOC+container+or+whatever.
++++//+if+you+don't+like+the+mutability+shown+here+(IoC+containers+are+usually+immutable+after+being+configured)
++++//+you+can+use+some+sort+of+write-once+object
++++//+or+more+advanced+approach+like+authenticated+access
++++public+static+Func<Dependencies>+GetDependencies+{+get;+set;+}+++++
++++public+class+Dependencies
++++{
++++++++//+whatever+your+service+needs+here.
++++++++public+Thing1+Thing1+{get;}
++++++++public+Thing2+Thing2+{get;}

++++++++public+Dependencies(Thing1+thing1,+Thing2+thing2)
++++++++{
++++++++++++Thing1+=+thing1;
++++++++++++Thing2+=+thing2;
++++++++}
++++}

++++public+MyService+()
++++{
++++++++_dependencies+=+GetDependencies();+//+this+will+blow+up+at+run+time+in+the+exact+same+way+your+IoC+container+will+if+it+hasn't+been+properly+configured+up+front.+NO+DIFFERENCE
++++}
}|code-block|syntax|javascript|3055778|服务的依赖关系在它的嵌套Dependencies类的契约中明确指定。如果您正在使用IoC容器(它还没有为您修复WCF混乱)，您可以将其配置为创建Dependencies实例，而不是服务。这样你就会得到容器给你的温暖模糊的感觉，同时也不需要跳过WCF强加的太多的圈套。|offset|length|style|CODE|3055779|我不会因为这种方法而失眠。其他人也不应该这样做。毕竟，你的IoC容器是一个庞大的、庞大的、静态的委托集合，它为你创建了一些东西。再加一个有什么用呢？|3055780|entityMap^0|0|0|C|C|20|C|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]|$I|V|J|W|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

Screw it… I blended the dependency injection and service locator patterns (but mostly it's still dependency injection and it even takes place in the constructor which means you can have read-only state).

<pre><code>public class MyService : IMyService
{
 private readonly Dependencies _dependencies;

 // set this before creating service host. this can use your IOC container or whatever.
 // if you don't like the mutability shown here (IoC containers are usually immutable after being configured)
 // you can use some sort of write-once object
 // or more advanced approach like authenticated access
 public static Func&lt;Dependencies&gt; GetDependencies { get; set; } 
 public class Dependencies
 {
 // whatever your service needs here.
 public Thing1 Thing1 {get;}
 public Thing2 Thing2 {get;}

 public Dependencies(Thing1 thing1, Thing2 thing2)
 {
 Thing1 = thing1;
 Thing2 = thing2;
 }
 }

 public MyService ()
 {
 _dependencies = GetDependencies(); // this will blow up at run time in the exact same way your IoC container will if it hasn't been properly configured up front. NO DIFFERENCE
 }
}
</code></pre>

The dependencies of the service are clearly specified in the contract of it's nested <code>Dependencies</code> class. If you are using an IoC container (one that doesn't already fix the WCF mess for you), you can configure it to create the <code>Dependencies</code> instance instead of the service. This way you get the warm fuzzy feeling that your container gives you while also not having to jump through too many hoops imposed by WCF.

I'm not going to lose any sleep over this approach. Neither should anyone else. After all, you're IoC container is a big, fat, static collection of delegates that creates stuff for you. What's adding one more?

blocks|key|313356|text|创建带有依赖项的实例服务(让我们称其为myService)，然后像这样打开您的ServiceHost：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|313357|var+myService+=+new+Service(argumentOne,+argumentTwo,+.+.+.+etc.);
var+host+=+new+WebServiceHost(myService,+new+Uri("http://localhost:80"));
var+behavior+=+host.Description.Behaviors.Find<ServiceBehaviorAttribute>();
behavior.InstanceContextMode+=+InstanceContextMode.Single;
host.Open();|code-block|syntax|javascript|313358|entityMap^0|J|9|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

Create your instanced service with its dependencies (let's call it <code>myService</code>), then open up your ServiceHost like so:
<pre><code>var myService = new Service(argumentOne, argumentTwo, . . . etc.);
var host = new WebServiceHost(myService, new Uri(&quot;http://localhost:80&quot;));
var behavior = host.Description.Behaviors.Find&lt;ServiceBehaviorAttribute&gt;();
behavior.InstanceContextMode = InstanceContextMode.Single;
host.Open();
</code></pre>

I would like to pass values into the constructor on the class that implements my service. 

However ServiceHost only lets me pass in the name of the type to create, not what arguments to pass to its contrstructor.

I would like to be able to pass in a factory that creates my service object.

What I have found so far:

<ul>
<li><a href="http://weblogs.asp.net/cibrax/archive/2007/12/13/wcf-dependency-injection-behavior.aspx" rel="noreferrer">WCF Dependency Injection Behavior</a> which is more than what I am looking for and seems to be over-complex for my needs.</li>
</ul>

How do I pass values to the constructor on my wcf service?

Visual Studio

容器

我希望将值传递到实现我的服务的类的构造函数中。然而，ServiceHost只允许我传递要创建的类型的名称，而不是传递给其构造函数的参数。我希望能够传入一个创建我的服务对象的工厂。到目前为止，我发现的是：不仅仅是我想要的，而且似乎过于复杂，不能满足我的需求。

问如何将值传递给wcf服务上的构造函数？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何将值传递给wcf服务上的构造函数？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何将值传递给wcf服务上的构造函数？
EN