blocks|key|3131978|text|我在工作中有一个应用程序，它的工作原理类似于您在这里讨论的内容。我们在多个项目中有多个WCF服务，它们的所有配置信息都驻留在一个配置文件中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3131979|我的公司选择的解决方案是从配置文件中读取服务配置，然后基于读取的值以编程方式设置绑定、行为等。配置文件中的值不符合您通常在WCF服务中看到的配置内容-它被设计为便于助手类在运行时执行所有配置。|3131980|话虽如此，我一点也不喜欢这样做--有太多的耦合，而且相当混乱。|3131981|然而，它确实表明了这是可能的--这是在你的设计中要考虑的一件事。|3131982|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I have an application at work that works kind of like what you're talking about here. We have multiple WCF services across multiple projects and all of their configuration information resides in a single config file.

The solution my company chose was to read the service configuration out of the config file and then programmatically set up the bindings, behavior, etc based on the values read. The values in the config file don't conform to the config stuff you usually see in WCF services - it was designed to be easily used by a helper class to do all the configuration at run time.

All that said, I'm not a big fan of doing that at all - too much coupling going on and it's pretty messy.

It does, though, show that it's possible - it's one thing to think about in your design.

blocks|key|352144|text|我一直渴望做同样的事情--基本上甚至更进一步:将我的WCF配置放在一个数据库表中(因为我可以更改它--不能访问我的托管提供商上的文件系统来更改配置文件:-()。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|352145|不幸的是，这似乎不是那么简单……|352146|基本上，它归结为必须编写您自己的自定义"ServiceHost“后代，它可以根据需要处理配置。|352147|这里有一个loading+WCF+configuration+from+a+custom+config+location的例子。|offset|length|352148|这可能会让你振作起来？我仍然希望有一天我能弄清楚“从数据库表加载我的配置”.我想我只需要安静地工作一周:-)|352149|entityMap|0|LINK|mutability|MUTABLE|url|http://www.paraesthesia.com/archive/2008/11/26/reading-wcf-configuration-from-a-custom-location.aspx^0|0|0|0|5|1J|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$H|X|I|Y|1|Z]]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

I've been longing to do the same - basically even one step further: put my WCF config in a database table (since I can change that - can't access the file system on my hosted provider to change config files :-().

Unfortunately, this seems less than simple.....

Basically, it boils down to having to write your own custom "ServiceHost" descendant which can handle the configuration as needed.

Here's an example of <a href="http://www.paraesthesia.com/archive/2008/11/26/reading-wcf-configuration-from-a-custom-location.aspx" rel="nofollow noreferrer">loading WCF configuration from a custom config location</a>.

This might get you going? I'm still hoping I'll be able to figure out the "loading my config from a database table" some day..... just need to quiet week at work, I guess :-)

blocks|key|3132015|text|我倾向于以编程方式配置所有的服务设置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3132016|我的客户实际上不是那种理解XML的人，他们要求我制作更像旧的INI风格的配置文件。|3132017|这很容易做到(不包括读取INI文件代码)：|3132018|++++++++//+create+the+URI+which+is+used+as+the+service+endpoint
++++++++Uri+tcpBaseAddress+=+new+Uri(
++++++++++++++++string.Format("net.tcp://{0}:{1}",
++++++++++++++++++++LocalIPAddress.ToString(),+GeneralPortNumber));

++++++++//+create+the+net.tcp+binding+for+the+service+endpoint
++++++++NetTcpBinding+ntcBinding+=+new+NetTcpBinding();
++++++++ntcBinding.Security.Mode+=+SecurityMode.None;
++++++++System.ServiceModel.Channels.Binding+tcpBinding+=+ntcBinding;

++++++++//+create+the+service+host+and+add+the+endpoint
++++++++Host+=+new+ServiceHost(typeof(WordWarService),+tcpBaseAddress);|code-block|syntax|javascript|3132019|由于我们可以通过编程方式配置主机(以及客户端)，因此没有什么可以阻止您以您选择的任何方式(数据库、xml、疯狂文本文件等)提供设置。|3132020|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|R|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I have a tendency to programatically configure all my service settings. 

My clients aren't really the type to understand XML and have asked me make configuration files more like the old INI style.

This is easy to do (reading INI file code not included):

<pre><code> // create the URI which is used as the service endpoint
 Uri tcpBaseAddress = new Uri(
 string.Format("net.tcp://{0}:{1}",
 LocalIPAddress.ToString(), GeneralPortNumber));

 // create the net.tcp binding for the service endpoint
 NetTcpBinding ntcBinding = new NetTcpBinding();
 ntcBinding.Security.Mode = SecurityMode.None;
 System.ServiceModel.Channels.Binding tcpBinding = ntcBinding;

 // create the service host and add the endpoint
 Host = new ServiceHost(typeof(WordWarService), tcpBaseAddress);
</code></pre>

Since we can configure the host (and client, for that matter) programatically there is nothing keeping you from supplying the settings in any manner you choose (database, xml, crazy text file, etc).

blocks|key|3344871|text|你可以这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3344872|<system.serviceModel+configSource="wcf.config"/>|code-block|syntax|javascript|3344873|只需将您的服务模型部分剪切出来，并将其放入一个单独的文件中。您必须将整个节放入单独的配置文件中；使用这种方法，您不能让节跨越多个文件AFAIK。|3344874|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

You can do like this:

<pre><code>&lt;system.serviceModel configSource="wcf.config"/&gt;
</code></pre>

Just cut your service model section out and put it in a separate file. You will have to put the whole section into the separate config file; using this method you cannot have a section span multiple files AFAIK.

blocks|key|3132047|text|您可以使用configSource分离您的WCF配置。这里有说明：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3132048|http://weblogs.asp.net/cibrax/archive/2007/07/24/configsource-attribute-on-system-servicemodel-section.aspx|offset|length|3132049|另一种选择是以编程方式配置WCF服务。|3132050|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2Z|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

You can separate out your WCF configuration using configSource. Instructions here:

<a href="http://weblogs.asp.net/cibrax/archive/2007/07/24/configsource-attribute-on-system-servicemodel-section.aspx" rel="noreferrer">http://weblogs.asp.net/cibrax/archive/2007/07/24/configsource-attribute-on-system-servicemodel-section.aspx</a>

Another option is to configure your WCF services programatically.

blocks|key|351048|text|我找到了这篇文章，可能会对你有所帮助。我还没有尝试过，但它看起来相当简单。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|351049|http://weblogs.asp.net/cibrax/archive/2007/07/24/configsource-attribute-on-system-servicemodel-section.aspx|offset|length|351050|“configSource属性最初是在.NET+Framework2.0中引入的，用于支持外部配置文件。该属性可以添加到任何配置节，以指定该节的外部文件。|351051|遗憾的是，system.serviceModel节组不支持此属性。如果您尝试添加它，您将收到以下异常：|351052|无法指定属性'configSource‘，因为其名称以保留的前缀'config’或'lock‘开头|351053|我发现，您可以在system.serviceModel下的不同部分使用此属性，例如服务、行为或绑定。“|351054|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2Z|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|12|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|C]]]]

I found this article that may help you out. I have not tried it, but it seems fairly straightforward.

<a href="http://weblogs.asp.net/cibrax/archive/2007/07/24/configsource-attribute-on-system-servicemodel-section.aspx" rel="nofollow noreferrer">http://weblogs.asp.net/cibrax/archive/2007/07/24/configsource-attribute-on-system-servicemodel-section.aspx</a>

"
The configSource attribute was firstly introduced in .NET framework 2.0 to support external configuration files. This attribute can be added to any configuration section to specify an external file for that section. 

Unfortunately, the system.serviceModel section group does not support this attribute. If you try to add it, you will receive the following exception:

The attribute 'configSource' cannot be specified because its name starts with the reserved prefix 'config' or 'lock'

What I found out is that you can use this attribute on the different sections under system.serviceModel such as services, behaviors or bindings.
"

blocks|key|3344949|text|System.ServiceModel.Configuration.ConfigurationChannelFactory等人支持从System.Configuration.Configuration实例读取配置。这意味着您可以将<system.servicemodel+...内容放在一个专用文件中，而无需从web/app.config中引用它。您可以有多个配置文件，每个客户端一个。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3344950|SharePoint+2010在其服务应用程序模型中过度使用了这一点，其中每个服务代理从一个专用的.config读取其设置，该and不一定是web.config或app.config，甚至不会从那里引用。|3344951|entityMap^0|0|1P|1U|Y|37|O|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

<code>System.ServiceModel.Configuration.ConfigurationChannelFactory</code> et al support reading the configuration from a <code>System.Configuration.Configuration</code> instance. Which means you can put the <code>&lt;system.servicemodel ...</code> stuff in a dedicated file without referencing it from web/app.config. You could have multiple config files, one for each client.

SharePoint 2010 uses that excessively in its service application model, where each service proxy reads its settings from a dedicated .config which is not necessarily web.config or app.config and isn't even referenced from there.

blocks|key|3344973|text|using+System;
using+System.Configuration;
using+System.IO;
using+System.ServiceModel;
using+System.ServiceModel.Configuration;

namespace+ConsoleHost
{
++++public+class+CustomServiceHost+:+ServiceHost
++++{
++++++++public+CustomServiceHost(string+customConfigPath,+Type+serviceType,+
++++++++++++params+Uri[]+baseAddresses)
++++++++{
++++++++++++CustomConfigPath+=+customConfigPath;
++++++++++++var+collection+=+new+UriSchemeKeyedCollection(baseAddresses);
++++++++++++InitializeDescription(serviceType,+collection);
++++++++}

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

++++++++protected+override+void+ApplyConfiguration()
++++++++{
++++++++++++if+(string.IsNullOrEmpty(CustomConfigPath)+%7C%7C
++++++++++++++++!File.Exists(CustomConfigPath))
++++++++++++{
++++++++++++++++base.ApplyConfiguration();
++++++++++++}
++++++++++++else
++++++++++++{
++++++++++++++++LoadConfigFromCustomLocation(CustomConfigPath);
++++++++++++}
++++++++}

++++++++void+LoadConfigFromCustomLocation(string+configFilename)
++++++++{
++++++++++++var+filemap+=+new+ExeConfigurationFileMap
++++++++++++{
++++++++++++++++ExeConfigFilename+=+configFilename
++++++++++++};
++++++++++++Configuration+config+=+ConfigurationManager.
++++++++++++++++OpenMappedExeConfiguration(filemap,+ConfigurationUserLevel.None);

++++++++++++var+serviceModel+=+ServiceModelSectionGroup.GetSectionGroup(config);

++++++++++++bool+loaded+=+false;
++++++++++++foreach+(ServiceElement+se+in+serviceModel.Services.Services)
++++++++++++{
++++++++++++++++if+(se.Name+==+Description.ConfigurationName)
++++++++++++++++{
++++++++++++++++++++LoadConfigurationSection(se);
++++++++++++++++++++loaded+=+true;
++++++++++++++++++++break;
++++++++++++++++}
++++++++++++}

++++++++++++if+(!loaded)
++++++++++++++++throw+new+ArgumentException("ServiceElement+doesn't+exist");
++++++++}
++++}
}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|3344974|在这个类之后，只需像通常使用它来初始化服务主机一样使用它|unstyled|offset|length|style|BOLD|3344975|myServiceHost+=新类型(ConfigFileName，CustomServiceHost+new+(QueryTree))；|3344976|myServiceHost.Open()；|3344977|entityMap^0|0|0|N|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|R|8|@$G|S|H|T|I|J]]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|F|7|W|8|@]|9|@]|A|$]]]|P|$]]

<pre><code>using System;
using System.Configuration;
using System.IO;
using System.ServiceModel;
using System.ServiceModel.Configuration;

namespace ConsoleHost
{
 public class CustomServiceHost : ServiceHost
 {
 public CustomServiceHost(string customConfigPath, Type serviceType, 
 params Uri[] baseAddresses)
 {
 CustomConfigPath = customConfigPath;
 var collection = new UriSchemeKeyedCollection(baseAddresses);
 InitializeDescription(serviceType, collection);
 }

 public string CustomConfigPath { get; private set; }

 protected override void ApplyConfiguration()
 {
 if (string.IsNullOrEmpty(CustomConfigPath) ||
 !File.Exists(CustomConfigPath))
 {
 base.ApplyConfiguration();
 }
 else
 {
 LoadConfigFromCustomLocation(CustomConfigPath);
 }
 }

 void LoadConfigFromCustomLocation(string configFilename)
 {
 var filemap = new ExeConfigurationFileMap
 {
 ExeConfigFilename = configFilename
 };
 Configuration config = ConfigurationManager.
 OpenMappedExeConfiguration(filemap, ConfigurationUserLevel.None);

 var serviceModel = ServiceModelSectionGroup.GetSectionGroup(config);

 bool loaded = false;
 foreach (ServiceElement se in serviceModel.Services.Services)
 {
 if (se.Name == Description.ConfigurationName)
 {
 LoadConfigurationSection(se);
 loaded = true;
 break;
 }
 }

 if (!loaded)
 throw new ArgumentException("ServiceElement doesn't exist");
 }
 }
}
</code></pre>

After this class just use it as you would normally use it to initialize the service host

myServiceHost = new CustomServiceHost(ConfigFileName, typeof(QueryTree));

myServiceHost.Open();

I have a specific requirement to remove all client WCF configuration (&lt;system.serviceModel&gt;) out of the main app.config file, and into a separate XML file. The behaviour I would like to see is similar to that available in the appSettings section using the File="" directive. In fact, I'd ideally like to be able to specify a separate file for each consumed service...

I know I can build a custom ChannelBuilder factory that reads config data from an XML file (or a series of them), but I would prefer to still have the config data "auto-discovered" by the client. 

Some basic Google searches seem to suggest this is not possible, but I wanted to get the view from SO - does anyone here know something I haven't been able to find? :)

<blockquote>
 Edit ::
 
 Tim Scott and davogones both came up with a possible suggestion, but one which relies on splitting the component sections of the system.serviceModel section out to separate files. Although this isn't quite what I'm looking for (I'd like to define each service and its associated elements discretely, one file per service), it is an option. I'll investigate and let you know what I thought.
</blockquote>

WCF Configuration - Split it out of app.config

文件系统

数据库

我有一个特定的需求，需要将所有client WCF configuration (<system.serviceModel>)从主app.config文件中删除，并放入一个单独的XML文件中。我希望看到的行为类似于使用File="“指令的appSettings部分中提供的行为。实际上，理想情况下，我希望能够为每个使用的...

问WCF配置-将其从app.config中分离出来
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WCF配置-将其从app.config中分离出来EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WCF配置-将其从app.config中分离出来
EN