web.config中的webservices部分 [英] webservices section in web.config

问题描述

我已经在vis studio 2005中写了一个WSE，并制作了一个dll，我可以在其他项目中使用

，包括以下内容在web.config中。


< webservices>

< soapextensiontypes>

< add type =" traceextension ，simpleModule"优先级= QUOT 1 QUOT; group =" high" />

< / soapExtensionTypes>

< / webservices>


这一切都工作很好但我有很多vis studio 2003项目我需要使用

这个用。当添加以上内容时，它们返回以下内容。


分析器错误消息：无法识别的配置部分''webservices''


我假设这表明在vis studio 2003中不支持WSE，是否可以在vis studio 2003中使用WSE？


谢谢

Hi,

I have written a WSE in vis studio 2005 as and produced a dll that I can use
in other projects by including the following in the web.config.

<webservices>
<soapextensiontypes>
<add type="traceextension, simpleModule" priority="1" group="high"/>
</soapExtensionTypes>
</webservices>

This all work fine but I have many vis studio 2003 projects I need to use
this with. When the above is added they return the following.

Parser Error Message: Unrecognized configuration section ''webservices''

I assume this indicates it WSE isn''t supported in vis studio 2003, is it
possible to use the WSE in vis studio 2003?

Thanks

推荐答案

Hello smarty，


欢迎来到MSDN新闻组。


来自你的描述，我知道你在VS 2003环境中使用WSE装备应用程序（在VS 2005下）尝试

时遇到了一些问题，

是否正确？


根据我的经验，由于WSE

组件的版本控制策略，这是预期的行为。 WSE组件是Microsoft

.NET基于Web服务的附加组件，到目前为止它已发布了三个版本。他们是b $ b 1.0,2.0和3.0。你在VS 2005中使用的那个是versino 3.0，它纯粹基于.net framework 2.0，是b $ b。由于vs 2003只支持.net

框架1.1开发，WSE 3.0无法在VS 2003 / .net 1.1

应用程序中使用。

目前WSE 1.0已被视为已过时。 WSE团队的'b
计划和推荐使用的WSE版如下：


1. WSE 2.0（最新的是SP3）仍然适用于VS 2003 / .net

框架1.1应用程序。它已经实现了大部分WS- *

规格，尽管其中一些规格与最新的

规格不兼容。


2. WSE 3.0是WSE组件的最新版本，适用于.net

框架2.0应用程序，并实现了最新的WS- *

规范。同时，WSE 3.0的编程模型也符合WFC（windows通信基金）中的Vista WINFX编程

模型。这意味着我们使用WSE 3.0开发的应用程序将很方便

将来升级到基于VISTA WCF的程序。


此外，如果您仍有兴趣在你的.net

框架1.1程序的WSE 2.0中，你可以从以下位置获取它。

然而，WSE 2.0有很多不同的编程模型和接口

与WSE 3.0相比，我们不能指望简单地复制代码并构建它们

上班。


#Web服务增强功能（ WSE）2.0 SP3 for Microsoft .NET
http://www.microsoft.com/downloads/d...631-c3e7-420a-

bc1e-ef18bab66122& displaylang = en


希望这会有所帮助。如果您仍然需要任何其他信息或有任何

进一步的问题，请随时告诉我。


此致，


Steven Cheng


Microsoft MSDN在线支持主管


============ ======================================


通过电子邮件收到我的帖子通知？请参阅

http：/ /msdn.microsoft.com/subscripti...ult.aspx#notif

ications。


注意：MSDN托管新闻组支持提供适用于非紧急问题

其中，社区或Microsoft支持工程师在1

工作日内做出初步回复
回复


可以接受。请注意，每个跟进回复可能需要大约

2个工作日


因为与您合作的支持专业人员可能需要进一步调查

来达到最优惠的分辨率。
此产品不适合需要


紧急，实时或基于电话的互动或复杂项目分析的情况

和转储分析


问题。这种性质的问题最好通过专门工作来支付

Microsoft支持


工程师通过联系Microsoft客户支持服务（CSS）

http：//msdn.microsoft.com/subscripti ... t / default.aspx 。


============================ ======================


此帖子按原样提供。没有保证，也没有授予任何权利。

Hello smarty,

Welcome to the MSDN newsgroup.

From your description, I understand you''re getting some problems when try
using the WSE equiped application(under VS 2005) in VS 2003 environment,
correct?

Based on my experience, this is the expected behvior due to the WSE
component''s versioning policy. The WSE component is an add-on of Microsoft
.NET based webservice, and it has published three versions so far. They are
1.0, 2.0 and 3.0. The one you used with VS 2005 is versino 3.0 which is
purely based on .net framework 2.0. Since vs 2003 only support .net
framework 1.1 developing, WSE 3.0 is not able to use in VS 2003/.net 1.1
applications.

Currently the WSE 1.0 is already considered as obsolete. The WSE team''s
plan and recommendation on the version of WSE to use is as below:

1. WSE 2.0(lastest one is SP3) is still workable with VS 2003/.net
framework 1.1 applications. And it has implemented most of the WS-*
specifications though some of them is not compatible to the latest
specification.

2. WSE 3.0 is the latest version of WSE components which works for .net
framework 2.0 application and has implemented the latest WS-*
specifications. Meanwhile, the WSE 3.0''s programming model is also conform
to the WCF(windows communication fundation) in Vista WINFX programming
model. That means our application developed with WSE 3.0 will be convenient
to upgrade to VISTA WCF based programs in the future.

In addition, if you still have interests in the WSE 2.0 for your .net
framework 1.1 programs, you can get it from the following location.
However, WSE 2.0 has much different programming model and interfaces
comparing to WSE 3.0, we can not expect to simply copy code and build them
to work.

#Web Services Enhancements (WSE) 2.0 SP3 for Microsoft .NET
http://www.microsoft.com/downloads/d...631-c3e7-420a-
bc1e-ef18bab66122&displaylang=en

Hope this helps. If you still need any other information or have any
further questions on this, please feel free to let me know.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

==================================================

Get notification to my posts through email? Please refer to

http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial

response from the community or a Microsoft Support Engineer within 1
business day is

acceptable. Please note that each follow up response may take approximately
2 business days

as the support professional working with you may need further investigation
to reach the

most efficient resolution. The offering is not appropriate for situations
that require

urgent, real-time or phone-based interactions or complex project analysis
and dump analysis

issues. Issues of this nature are best handled working with a dedicated
Microsoft Support

Engineer by contacting Microsoft Customer Support Services (CSS) at

http://msdn.microsoft.com/subscripti...t/default.aspx.

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

感谢您的帖子，我在2003年重写了WSE，它与

其他一起使用2003年申请。


我正在使用WSE来为web服务中的时间戳和各个阶段执行

执行，然后比较时间以计算需要多长时间

序列化，反序列化等。我正在使用.millisecond但是没有看到

在exectution时间的任何差异。知道为什么不呢？执行

的时间可能不到一毫秒吗？是一种在b $ b $毫秒下测量的方式吗？


不确定这是否是一个正确的发布位置，非常乐意移动它/>
如果有与之相关的论坛。


谢谢


" Steven Cheng [MSFT]"写道：

Thanks for the post, I have rewritten the WSE in 2003 and it works with the
other 2003 application now.

I am using the WSE to timestamp and various stages in the webservice
execution and then compare the times to work out how long it takes to
serialize, deserialise etc.. I am using the .millisecond but am not seeing
any difference in the exectution time. Any idea why not? Is the execution
time likely to be less than a millisecond? is the a way of measuring under a
millisecond?

Not sure if this is the correct place to post by the way so happy to move it
if there is a forum this relates to.

Thanks

"Steven Cheng[MSFT]" wrote:

Hello smarty，


欢迎来到MSDN新闻组。


从您的描述中，我了解到在VS 2003环境中使用WSE装备应用程序（在VS 2005下）尝试

时会遇到一些问题，

是否正确？


根据我的经验，由于WSE

组件的版本控制策略，这是预期的行为。 WSE组件是Microsoft

.NET基于Web服务的附加组件，到目前为止它已发布了三个版本。他们是b $ b 1.0,2.0和3.0。你在VS 2005中使用的那个是versino 3.0，它纯粹基于.net framework 2.0，是b $ b。由于vs 2003只支持.net

框架1.1开发，WSE 3.0无法在VS 2003 / .net 1.1

应用程序中使用。

目前WSE 1.0已被视为已过时。 WSE团队的'b
计划和推荐使用的WSE版如下：


1. WSE 2.0（最新的是SP3）仍然适用于VS 2003 / .net

框架1.1应用程序。它已经实现了大部分WS- *

规格，尽管其中一些规格与最新的

规格不兼容。


2. WSE 3.0是WSE组件的最新版本，适用于.net

框架2.0应用程序，并实现了最新的WS- *

规范。同时，WSE 3.0的编程模型也符合WFC（windows通信基金）中的Vista WINFX编程

模型。这意味着我们使用WSE 3.0开发的应用程序将很方便

将来升级到基于VISTA WCF的程序。


此外，如果您仍有兴趣在你的.net

框架1.1程序的WSE 2.0中，你可以从以下位置获取它。

然而，WSE 2.0有很多不同的编程模型和接口

与WSE 3.0相比，我们不能指望简单地复制代码并构建它们

上班。


#Web服务增强功能（ WSE）2.0 SP3 for Microsoft .NET
http://www.microsoft.com/downloads/d...631-c3e7-420a-

bc1e-ef18bab66122& displaylang = en


希望这会有所帮助。如果您仍然需要任何其他信息或有任何

进一步的问题，请随时告诉我。


此致，


Steven Cheng


Microsoft MSDN在线支持主管


============ ======================================


通过电子邮件收到我的帖子通知？请参阅

http：/ /msdn.microsoft.com/subscripti...ult.aspx#notif

ications。


注意：MSDN托管新闻组支持提供适用于非紧急问题

其中，社区或Microsoft支持工程师在1

工作日内做出初步回复
回复


可以接受。请注意，每个跟进回复可能需要大约

2个工作日


因为与您合作的支持专业人员可能需要进一步调查

来达到最优惠的分辨率。
此产品不适合需要


紧急，实时或基于电话的互动或复杂项目分析的情况

和转储分析


问题。这种性质的问题最好通过专门工作来支付

Microsoft支持


工程师通过联系Microsoft客户支持服务（CSS）

http：//msdn.microsoft.com/subscripti ... t / default.aspx 。


============================ ======================


此帖子按原样提供。没有保证，也没有授予任何权利

Hello smarty,

Welcome to the MSDN newsgroup.

From your description, I understand you''re getting some problems when try
using the WSE equiped application(under VS 2005) in VS 2003 environment,
correct?

Based on my experience, this is the expected behvior due to the WSE
component''s versioning policy. The WSE component is an add-on of Microsoft
.NET based webservice, and it has published three versions so far. They are
1.0, 2.0 and 3.0. The one you used with VS 2005 is versino 3.0 which is
purely based on .net framework 2.0. Since vs 2003 only support .net
framework 1.1 developing, WSE 3.0 is not able to use in VS 2003/.net 1.1
applications.

Currently the WSE 1.0 is already considered as obsolete. The WSE team''s
plan and recommendation on the version of WSE to use is as below:

1. WSE 2.0(lastest one is SP3) is still workable with VS 2003/.net
framework 1.1 applications. And it has implemented most of the WS-*
specifications though some of them is not compatible to the latest
specification.

2. WSE 3.0 is the latest version of WSE components which works for .net
framework 2.0 application and has implemented the latest WS-*
specifications. Meanwhile, the WSE 3.0''s programming model is also conform
to the WCF(windows communication fundation) in Vista WINFX programming
model. That means our application developed with WSE 3.0 will be convenient
to upgrade to VISTA WCF based programs in the future.

In addition, if you still have interests in the WSE 2.0 for your .net
framework 1.1 programs, you can get it from the following location.
However, WSE 2.0 has much different programming model and interfaces
comparing to WSE 3.0, we can not expect to simply copy code and build them
to work.

#Web Services Enhancements (WSE) 2.0 SP3 for Microsoft .NET
http://www.microsoft.com/downloads/d...631-c3e7-420a-
bc1e-ef18bab66122&displaylang=en

Hope this helps. If you still need any other information or have any
further questions on this, please feel free to let me know.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

==================================================

Get notification to my posts through email? Please refer to

http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial

response from the community or a Microsoft Support Engineer within 1
business day is

acceptable. Please note that each follow up response may take approximately
2 business days

as the support professional working with you may need further investigation
to reach the

most efficient resolution. The offering is not appropriate for situations
that require

urgent, real-time or phone-based interactions or complex project analysis
and dump analysis

issues. Issues of this nature are best handled working with a dedicated
Microsoft Support

Engineer by contacting Microsoft Customer Support Services (CSS) at

http://msdn.microsoft.com/subscripti...t/default.aspx.

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights

感谢您的回复Smarty，


当然，我认为它适合继续在这里讨论，因为这是一个

webservice speccific问题。此外，当您有任何.NET Web服务或WSE问题时，欢迎您在MSDN新闻组之后发布

：

microsoft.public.dotnet.framework.aspnet .webservic es


microsoft.public.dotnet.framework.webservices

microsoft.public.dotnet.framework.webservices.enha ncements


至于你的进一步描述（下）：


=================== =====

我正在使用WSE来设置时间戳和webservice中的各个阶段

执行，然后比较时间以计算出需要多长时间/>
序列化，反序列化等。

========================


我不确定各个阶段是什么？你在这里提到过，你的意思是

请求到达服务器端的进程然后代码执行

和响应发送到cilent ....？你会在这方面提供一些额外的

描述吗？根据我的理解，ASP.NET webservice是由webserviceHandler处理的，它提供了一个管道，我们可以在其中插入
多个soapExtensions以自定义传入或传出的SOAP消息： br />

＃在ASP.NET中使用SOAP扩展
http://msdn.microsoft.com/msdnmag/is.../03/ASPColumn/


#Altering the使用SOAP扩展的SOAP消息
http://msdn.microsoft.com/library/de...us/cpguide/htm

l / cpconalteringsoapmessageusingsoapextensions.asp


Thereforce，soapextensions只是ASP.NET webservice的一部分

服务器端或客户端代理的处理管道，不包括

webservice代码执行。


此外，至于WSE c omponent（2.0或3.0），它是基于soapExtension实现的完全

。这意味着所有WSE

功能（过滤器...处理）生命周期都是那个

SOAPExtension的子集。因此，我认为不可能计算所有

执行状态或ASP.NET webservice中每个阶段的信息

服务器端处理。


只是我的一些理解。如果您有任何其他想法或

考虑，请随时在此处发布。


此致，


Steven Cheng


Microsoft MSDN在线支持主管

该帖子按原样提供。没有保证，也没有授予任何权利。

Thanks for your response Smarty,

Sure, I think it appropriate to continue discuss here since this is a
webservice speccific question. Also, you''re welcome to post in the
following MSDN newsgroups when you have any .NET webservice or WSE issues:
microsoft.public.dotnet.framework.aspnet.webservic es

microsoft.public.dotnet.framework.webservices

microsoft.public.dotnet.framework.webservices.enha ncements

As for your further description (below):

========================
I am using the WSE to timestamp and various stages in the webservice
execution and then compare the times to work out how long it takes to
serialize, deserialise etc..
========================

I''m not sure what''s the "various stages" you mentioned here, do you mean
the process from the request arrive server-side and then the code execution
and response dispatched to cilent .... ? Would you provide some further
description on this? Based on my understanding, ASP.NET webservice is
handled by webserviceHandler and it provide a pipeline where we can insert
muliple soapExtensions to customize the SOAP message incoming or outgoing:

#Using SOAP Extensions in ASP.NET
http://msdn.microsoft.com/msdnmag/is.../03/ASPColumn/

#Altering the SOAP Message Using SOAP Extensions
http://msdn.microsoft.com/library/de...us/cpguide/htm
l/cpconalteringsoapmessageusingsoapextensions.asp

Thereforce, soapextensions are only part of the ASP.NET webservice
server-side or client proxy''s processing pipeline, not include the
webservice code execution.

Further more, as for the WSE component(2.0 or 3.0), it is a completely
implemented based on a soapExtension. That means all the WSE
features(filters .. processing) lifetime is a subset of that
SOAPExtension. Therefore, I don''t think it''ll be possible to calculate all
the execution states or info about every stages in ASP.NET webservice
server-side processing.

Just some of my understanding. If you have any other ideas or
consideration, please feel free to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

这篇关于web.config中的webservices部分的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！