2  

Create a .Bat file which uses svcutil, for proxygeneration, that has the settings that is right for your project. It's fairly easy. Clicking on the batfile, to generate new proxyfiles whenever the interface have been changed is easy.

创建一个.bat文件,该文件使用svcutil进行代理生成,该文件具有适合您项目的设置。这很容易。单击bat文件,只要界面被更改就生成新的代理文件很容易。

The batch can then later be used in automated builds. Then you only need to set up the app.config (or web.config) once. We generally separate the different configs for different environments, such as dev, test prod.

然后可以将批处理用于自动构建中。然后你只需要设置一次app.config(或web.config)。我们通常会针对不同的环境分离不同的配置,例如dev,test prod。

Example (watch out for linebreaks):

示例(注意换行):

REM generate meta data
call "SVCUTIL.EXE" /t:metadata "MyProject.dll" /reference:"MyReference.dll"

REM making sure the file is writable
attrib -r "MyServiceProxy.cs"

REM create new proxy file
call "SVCUTIL.EXE" /t:code *.wsdl *.xsd /serializable /serializer:Auto /collectionType:System.Collections.Generic.List`1  /out:"MyServiceProxy.cs" /namespace:*,MY.Name.Space /reference:"MyReference.dll" 

:)

//W

2  

Rather than changing the generated endpoint, uou could add a second endpoint and binding definition with the configuration you need, then in your code just put the name of the new endpoint in your service client constructor.

您可以使用所需的配置添加第二个端点和绑定定义,而不是更改生成的端点,然后在代码中将新端点的名称添加到服务客户端构造函数中。

0  

Somehow I prefer using svcutil.exe directly than to use the "Add Service Reference" feature of Visual Studio :P This is what we're doing on our WCF projects.

不知何故,我更喜欢直接使用svcutil.exe而不是使用Visual Studio的“添加服务引用”功能:P这就是我们在WCF项目中所做的事情。

0  

I take your point, svcutil is definetly the more advanced way of adding and updating service references. Its just a fair bit more manual work when "right click, update reference" is so close to just working in a single step.

我认为,svcutil绝对是添加和更新服务引用的更高级方法。当“右键单击,更新参考”非常接近于只需一步操作时,它只需要更多的手动工作。

I guess we could create some batch files or something to just output the reference code. Even then, manually checking out and updating the service code with svcutil will probably be more work than just undoing the check out on the config.

我想我们可以创建一些批处理文件或只是输出参考代码。即使这样,使用svcutil手动检出和更新服务代码也可能比撤消配置中的检出更多。

Thanks for the advice in any case.

在任何情况下都要感谢您的建议。

0  

What we do is we check out (from source control) the app.config and *.cs files that are autogenerated by the svcutil.exe utility, then we run a batch file that runs svcutil.exe to retrieve the service metadata. When it's done, we recompile the code, make sure it works, then check the updated app.config and *.cs files back in. It's a whole lot more reliable than using the oft-buggy "Add Service Reference" with Visual Studio.

我们做的是检查(从源代码控制)svcutil.exe实用程序自动生成的app.config和* .cs文件,然后我们运行一个运行svcutil.exe的批处理文件来检索服务元数据。完成后,我们重新编译代码,确保它有效,然后再检查更新的app.config和* .cs文件。它比使用Visual Studio的oft-buggy“添加服务引用”要可靠得多。