By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,689 Members | 1,731 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,689 IT Pros & Developers. It's quick & easy.

Updating Web References in .NET 2003

P: n/a
Our developers have experienced a problem with updating Web References in
Visual Studio.NET 2003.

Normally, when a web service class (.asmx) is created, updating the Web
Reference will utilise the disco file to update the

Corresponding proxy file and reflect the changes made to the web service.
However, the results of doing this with out params is that the results seem
to be unpredictable and sometimes - possibly due to caching - the proxy file
is not updated, hence causing problems compiling the code.

We also noticed that when for example two out parameters are specified - in
the proxy class, the method contains one output parameter and the second one
is changed into a return value.

We have worked around this by manually changing the reference.cs file for
the web service.

We would like to know if there is any options for turning off caching of Web
Service proxy files and indeed where they are cached.

What is the recommendation for passing parameters out of Web Services and
could we have a detailed resolution to this problem?

Nov 23 '05 #1
Share this Question
Share on Google+
14 Replies


P: n/a
I'll be interested to see if anyone else who reads this thread has ever
tried to us out parameters in a web method before. In general, using an
RPC style method signature for a web method is discouraged -- a more
message-oriented approach can help solve a lot of these headaches.

The patterns & practices group at Microsoft has been talking about the
"Document Processor" pattern for designing web service interfaces. I
had been working with something similar, but decided to implement this
pattern and I've had great success with it. Essentially, you create a
custom type within your service that acts as a request parameter and
another custom type as the return type. So your web method would look
something like this:

[WebMethod]
public ProcessOrderResponse ProcessOrder(ProcessOrderRequest request)
{
...
}

Both ProcessOrderRequest and ProcessOrderResponse are "carrier" classes
inside your service that are used specifically to pass data into the
web method and send the results back to the consumer. Managing these as
classes in the service allows you to dynamically insert them into the
service's WSDL, enforcing a strong contract with the consumer, while
simultaneously allow loose coupling with service consumers.

I'm working on getting a working example of this pattern posted on my
web site, but I sort of need to finish the site first. If you like, I
can repost when I have this done.

HTH

Thanks,
Denny Boynton

Nov 23 '05 #2

P: n/a
Thanks for the information but this solution goes against the Microsoft
recommened approach specified in the document 'Improving .NET Application
Performance and Scalability' which says you shouldn't do it this way but
instead use many simple data types as input and output parameters.

"Denny Boynton" wrote:
I'll be interested to see if anyone else who reads this thread has ever
tried to us out parameters in a web method before. In general, using an
RPC style method signature for a web method is discouraged -- a more
message-oriented approach can help solve a lot of these headaches.

The patterns & practices group at Microsoft has been talking about the
"Document Processor" pattern for designing web service interfaces. I
had been working with something similar, but decided to implement this
pattern and I've had great success with it. Essentially, you create a
custom type within your service that acts as a request parameter and
another custom type as the return type. So your web method would look
something like this:

[WebMethod]
public ProcessOrderResponse ProcessOrder(ProcessOrderRequest request)
{
...
}

Both ProcessOrderRequest and ProcessOrderResponse are "carrier" classes
inside your service that are used specifically to pass data into the
web method and send the results back to the consumer. Managing these as
classes in the service allows you to dynamically insert them into the
service's WSDL, enforcing a strong contract with the consumer, while
simultaneously allow loose coupling with service consumers.

I'm working on getting a working example of this pattern posted on my
web site, but I sort of need to finish the site first. If you like, I
can repost when I have this done.

HTH

Thanks,
Denny Boynton

Nov 23 '05 #3

P: n/a
I'm very familiar with that document. It covers general .NET
application development and, as such, I generally agree with the
content of that document. However, once you start using web services
and enter the realm of "service-orientation," the rules do change
somewhat.

It sounds like you're using very RPC style interfaces on your web
services. This will promote more "chatty" versus "chunky" communication
with the service and I can testify that this will DEFINITELY degrad
your performance. It can also complicate the contract (WSDL) of the
services you're trying to consume.

Ron Jacobs is a Product Manager at Microsoft for the Patterns &
Practices group and does a great deal of writing and public speaking on
web services and service-oriented architectures. Take a look at this
link:

http://www.ronjacobs.com/talks.htm

Have a look at the "Patterns for SOA" presentation. While this talk
looks at SOA as a whole, the patterns proposed (including "Document
Processor" which I summarize in my initial post) are excellent
guidelines for writing performant and loosely-coupled web services that
maintain the integrity of the service contract as well.

HTH

Thanks,
Denny Boynton

Nov 23 '05 #4

P: n/a
Thanks for the info, but an interesting thing we have found with our previous
project (we went down the route of using complex data types there) that we
found the opposite was true. We had definite perofrmance degregation until
we started using simple data types on the system and then we noticed a major
performance increase. So we will probably keep with the simple data types on
this project and hope someone comes up with the reason why the references
aren't being upated.
"Denny Boynton" wrote:
I'm very familiar with that document. It covers general .NET
application development and, as such, I generally agree with the
content of that document. However, once you start using web services
and enter the realm of "service-orientation," the rules do change
somewhat.

It sounds like you're using very RPC style interfaces on your web
services. This will promote more "chatty" versus "chunky" communication
with the service and I can testify that this will DEFINITELY degrad
your performance. It can also complicate the contract (WSDL) of the
services you're trying to consume.

Ron Jacobs is a Product Manager at Microsoft for the Patterns &
Practices group and does a great deal of writing and public speaking on
web services and service-oriented architectures. Take a look at this
link:

http://www.ronjacobs.com/talks.htm

Have a look at the "Patterns for SOA" presentation. While this talk
looks at SOA as a whole, the patterns proposed (including "Document
Processor" which I summarize in my initial post) are excellent
guidelines for writing performant and loosely-coupled web services that
maintain the integrity of the service contract as well.

HTH

Thanks,
Denny Boynton

Nov 23 '05 #5

P: n/a
Interestingly we have discovered that in this scenario we don't have a return
type defined but what seems to happen on the client side proxy is the first
output parameter becomes the return type and the new output parameter becomes
part of the functions parameter list an example is shown below:

Before adding new output parameter:
server definition: void X(int i, out int j)
client proxy defintion: void X(int i, out int j)
After adding new output parameter:
server definition: void X(int i, out int j, out string k)
client proxy defintion: int X(int i, out string k)


"el_sid" wrote:
Thanks for the info, but an interesting thing we have found with our previous
project (we went down the route of using complex data types there) that we
found the opposite was true. We had definite perofrmance degregation until
we started using simple data types on the system and then we noticed a major
performance increase. So we will probably keep with the simple data types on
this project and hope someone comes up with the reason why the references
aren't being upated.
"Denny Boynton" wrote:
I'm very familiar with that document. It covers general .NET
application development and, as such, I generally agree with the
content of that document. However, once you start using web services
and enter the realm of "service-orientation," the rules do change
somewhat.

It sounds like you're using very RPC style interfaces on your web
services. This will promote more "chatty" versus "chunky" communication
with the service and I can testify that this will DEFINITELY degrad
your performance. It can also complicate the contract (WSDL) of the
services you're trying to consume.

Ron Jacobs is a Product Manager at Microsoft for the Patterns &
Practices group and does a great deal of writing and public speaking on
web services and service-oriented architectures. Take a look at this
link:

http://www.ronjacobs.com/talks.htm

Have a look at the "Patterns for SOA" presentation. While this talk
looks at SOA as a whole, the patterns proposed (including "Document
Processor" which I summarize in my initial post) are excellent
guidelines for writing performant and loosely-coupled web services that
maintain the integrity of the service contract as well.

HTH

Thanks,
Denny Boynton

Nov 23 '05 #6

P: n/a
Hi el_sid,

Thanks for posting in MSDN newsgroup.
As for the VS.NET's "add webreference" and "update web reference" command,
they're doing the same operation as the WSDL.exe utility. Based on my
research, there haven't any explicit cache in these proxy generating
operations. As for the caching problem, I'm wondering whether it's a
environment specific issue such as the networking condition. Also, as for
===============
the the results seem to be unpredictable and sometimes
===============
do you mean the updated proxy content will be randomly changed, for
example, when I use the "update web reference" serveral times for the same
service proxy, the generated proxy will be different? If so, that really
seems strange, I think you can try testing this on different machine to see
whether you continously get the same behavior.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)


--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcWzwx6Z76pl7XL1R1eaNulFQQPNrA==
X-WBNR-Posting-Host: 158.234.10.144
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
Subject: Re: Updating Web References in .NET 2003
Date: Wed, 7 Sep 2005 08:45:06 -0700
Lines: 61
Message-ID: <A2**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
microsoft.public.dotnet.framework.webservices:7813
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

Interestingly we have discovered that in this scenario we don't have a
return
type defined but what seems to happen on the client side proxy is the first
output parameter becomes the return type and the new output parameter
becomes
part of the functions parameter list an example is shown below:

Before adding new output parameter:
server definition: void X(int i, out int j)
client proxy defintion: void X(int i, out int j)
After adding new output parameter:
server definition: void X(int i, out int j, out string k)
client proxy defintion: int X(int i, out string k)


"el_sid" wrote:
Thanks for the info, but an interesting thing we have found with our previous project (we went down the route of using complex data types there) that we found the opposite was true. We had definite perofrmance degregation until we started using simple data types on the system and then we noticed a major performance increase. So we will probably keep with the simple data types on this project and hope someone comes up with the reason why the references
aren't being upated.
"Denny Boynton" wrote:
I'm very familiar with that document. It covers general .NET
application development and, as such, I generally agree with the
content of that document. However, once you start using web services
and enter the realm of "service-orientation," the rules do change
somewhat.

It sounds like you're using very RPC style interfaces on your web
services. This will promote more "chatty" versus "chunky" communication
with the service and I can testify that this will DEFINITELY degrad
your performance. It can also complicate the contract (WSDL) of the
services you're trying to consume.

Ron Jacobs is a Product Manager at Microsoft for the Patterns &
Practices group and does a great deal of writing and public speaking on
web services and service-oriented architectures. Take a look at this
link:

http://www.ronjacobs.com/talks.htm

Have a look at the "Patterns for SOA" presentation. While this talk
looks at SOA as a whole, the patterns proposed (including "Document
Processor" which I summarize in my initial post) are excellent
guidelines for writing performant and loosely-coupled web services that
maintain the integrity of the service contract as well.

HTH

Thanks,
Denny Boynton


Nov 23 '05 #7

P: n/a
We see this on all our XP develipment machines running with XP SP 1 and .NET
framework 1.1 with SP1.

"Steven Cheng[MSFT]" wrote:
Hi el_sid,

Thanks for posting in MSDN newsgroup.
As for the VS.NET's "add webreference" and "update web reference" command,
they're doing the same operation as the WSDL.exe utility. Based on my
research, there haven't any explicit cache in these proxy generating
operations. As for the caching problem, I'm wondering whether it's a
environment specific issue such as the networking condition. Also, as for
===============
the the results seem to be unpredictable and sometimes
===============
do you mean the updated proxy content will be randomly changed, for
example, when I use the "update web reference" serveral times for the same
service proxy, the generated proxy will be different? If so, that really
seems strange, I think you can try testing this on different machine to see
whether you continously get the same behavior.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)


--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcWzwx6Z76pl7XL1R1eaNulFQQPNrA==
X-WBNR-Posting-Host: 158.234.10.144
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
Subject: Re: Updating Web References in .NET 2003
Date: Wed, 7 Sep 2005 08:45:06 -0700
Lines: 61
Message-ID: <A2**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices:7813
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

Interestingly we have discovered that in this scenario we don't have a
return
type defined but what seems to happen on the client side proxy is the first
output parameter becomes the return type and the new output parameter
becomes
part of the functions parameter list an example is shown below:

Before adding new output parameter:
server definition: void X(int i, out int j)
client proxy defintion: void X(int i, out int j)
After adding new output parameter:
server definition: void X(int i, out int j, out string k)
client proxy defintion: int X(int i, out string k)


"el_sid" wrote:
Thanks for the info, but an interesting thing we have found with our

previous
project (we went down the route of using complex data types there) that

we
found the opposite was true. We had definite perofrmance degregation

until
we started using simple data types on the system and then we noticed a

major
performance increase. So we will probably keep with the simple data

types on
this project and hope someone comes up with the reason why the references
aren't being upated.
"Denny Boynton" wrote:
I'm very familiar with that document. It covers general .NET
application development and, as such, I generally agree with the
content of that document. However, once you start using web services
and enter the realm of "service-orientation," the rules do change
somewhat.

It sounds like you're using very RPC style interfaces on your web
services. This will promote more "chatty" versus "chunky" communication
with the service and I can testify that this will DEFINITELY degrad
your performance. It can also complicate the contract (WSDL) of the
services you're trying to consume.

Ron Jacobs is a Product Manager at Microsoft for the Patterns &
Practices group and does a great deal of writing and public speaking on
web services and service-oriented architectures. Take a look at this
link:

http://www.ronjacobs.com/talks.htm

Have a look at the "Patterns for SOA" presentation. While this talk
looks at SOA as a whole, the patterns proposed (including "Document
Processor" which I summarize in my initial post) are excellent
guidelines for writing performant and loosely-coupled web services that
maintain the integrity of the service contract as well.

HTH

Thanks,
Denny Boynton

Nov 23 '05 #8

P: n/a
Thanks for your response el_sid,

So have you tried add webreference/ update webreference from this services
from some other development machines? Based on my local test on some
machine, the update webreference operations should not generate randomly
result fo the proxy code. I still think it might be a machine specific
problem.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcXDQUtdIap2eeoLQMqr0GSzF0F7+w==
X-WBNR-Posting-Host: 158.234.10.144
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
<A2**********************************@microsoft.co m>
<rp*************@TK2MSFTNGXA01.phx.gbl>
Subject: Re: Updating Web References in .NET 2003
Date: Tue, 27 Sep 2005 01:56:05 -0700
Lines: 137
Message-ID: <E5**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl
microsoft.public.dotnet.framework.webservices:8030
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

We see this on all our XP develipment machines running with XP SP 1 and
..NET
framework 1.1 with SP1.

"Steven Cheng[MSFT]" wrote:
Hi el_sid,

Thanks for posting in MSDN newsgroup.
As for the VS.NET's "add webreference" and "update web reference" command, they're doing the same operation as the WSDL.exe utility. Based on my
research, there haven't any explicit cache in these proxy generating
operations. As for the caching problem, I'm wondering whether it's a
environment specific issue such as the networking condition. Also, as for
===============
the the results seem to be unpredictable and sometimes
===============
do you mean the updated proxy content will be randomly changed, for
example, when I use the "update web reference" serveral times for the same service proxy, the generated proxy will be different? If so, that really
seems strange, I think you can try testing this on different machine to see whether you continously get the same behavior.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)


--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcWzwx6Z76pl7XL1R1eaNulFQQPNrA==
X-WBNR-Posting-Host: 158.234.10.144
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
Subject: Re: Updating Web References in .NET 2003
Date: Wed, 7 Sep 2005 08:45:06 -0700
Lines: 61
Message-ID: <A2**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices:7813
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

Interestingly we have discovered that in this scenario we don't have a
return
type defined but what seems to happen on the client side proxy is the first output parameter becomes the return type and the new output parameter
becomes
part of the functions parameter list an example is shown below:

Before adding new output parameter:
server definition: void X(int i, out int j)
client proxy defintion: void X(int i, out int j)
After adding new output parameter:
server definition: void X(int i, out int j, out string k)
client proxy defintion: int X(int i, out string k)


"el_sid" wrote:
Thanks for the info, but an interesting thing we have found with our

previous
project (we went down the route of using complex data types there) that

we
found the opposite was true. We had definite perofrmance degregation

until
we started using simple data types on the system and then we noticed a

major
performance increase. So we will probably keep with the simple data

types on
this project and hope someone comes up with the reason why the references aren't being upated.
"Denny Boynton" wrote:
I'm very familiar with that document. It covers general .NET
application development and, as such, I generally agree with the
content of that document. However, once you start using web services
and enter the realm of "service-orientation," the rules do change
somewhat.

It sounds like you're using very RPC style interfaces on your web
services. This will promote more "chatty" versus "chunky" communication with the service and I can testify that this will DEFINITELY degrad
your performance. It can also complicate the contract (WSDL) of the
services you're trying to consume.

Ron Jacobs is a Product Manager at Microsoft for the Patterns &
Practices group and does a great deal of writing and public speaking on web services and service-oriented architectures. Take a look at this
link:

http://www.ronjacobs.com/talks.htm

Have a look at the "Patterns for SOA" presentation. While this talk
looks at SOA as a whole, the patterns proposed (including "Document
Processor" which I summarize in my initial post) are excellent
guidelines for writing performant and loosely-coupled web services that maintain the integrity of the service contract as well.

HTH

Thanks,
Denny Boynton


Nov 23 '05 #9

P: n/a
I experience this problem very frequently on both 2000 Pro and XP Pro
machines. My issue is that I update the web service itself and then
when I go to update the web service it doesn't update it at all. I can
dramatically change the web service and at random the update web
service does not regenerate the proxy class with the new settings.

I would really love to know how to fix this issue.

Steven Cheng[MSFT] wrote:
Thanks for your response el_sid,

So have you tried add webreference/ update webreference from this services
from some other development machines? Based on my local test on some
machine, the update webreference operations should not generate randomly
result fo the proxy code. I still think it might be a machine specific
problem.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcXDQUtdIap2eeoLQMqr0GSzF0F7+w==
X-WBNR-Posting-Host: 158.234.10.144
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
<A2**********************************@microsoft.co m>
<rp*************@TK2MSFTNGXA01.phx.gbl>
Subject: Re: Updating Web References in .NET 2003
Date: Tue, 27 Sep 2005 01:56:05 -0700
Lines: 137
Message-ID: <E5**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices:8030
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

We see this on all our XP develipment machines running with XP SP 1 and
.NET
framework 1.1 with SP1.

"Steven Cheng[MSFT]" wrote:
Hi el_sid,

Thanks for posting in MSDN newsgroup.
As for the VS.NET's "add webreference" and "update web reference"

command,
they're doing the same operation as the WSDL.exe utility. Based on my
research, there haven't any explicit cache in these proxy generating
operations. As for the caching problem, I'm wondering whether it's a
environment specific issue such as the networking condition. Also, as for
===============
the the results seem to be unpredictable and sometimes
===============
do you mean the updated proxy content will be randomly changed, for
example, when I use the "update web reference" serveral times for the

same
service proxy, the generated proxy will be different? If so, that really
seems strange, I think you can try testing this on different machine to

see
whether you continously get the same behavior.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)


--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcWzwx6Z76pl7XL1R1eaNulFQQPNrA==
X-WBNR-Posting-Host: 158.234.10.144
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
Subject: Re: Updating Web References in .NET 2003
Date: Wed, 7 Sep 2005 08:45:06 -0700
Lines: 61
Message-ID: <A2**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices:7813
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

Interestingly we have discovered that in this scenario we don't have a
return
type defined but what seems to happen on the client side proxy is the

first
output parameter becomes the return type and the new output parameter
becomes
part of the functions parameter list an example is shown below:

Before adding new output parameter:
server definition: void X(int i, out int j)
client proxy defintion: void X(int i, out int j)
After adding new output parameter:
server definition: void X(int i, out int j, out string k)
client proxy defintion: int X(int i, out string k)


"el_sid" wrote:
Thanks for the info, but an interesting thing we have found with our

previous
project (we went down the route of using complex data types there) that

we
found the opposite was true. We had definite perofrmance degregation

until
we started using simple data types on the system and then we noticed a

major
performance increase. So we will probably keep with the simple data

types on
this project and hope someone comes up with the reason why the references aren't being upated.
"Denny Boynton" wrote:

> I'm very familiar with that document. It covers general .NET
> application development and, as such, I generally agree with the
> content of that document. However, once you start using web services
> and enter the realm of "service-orientation," the rules do change
> somewhat.
>
> It sounds like you're using very RPC style interfaces on your web
> services. This will promote more "chatty" versus "chunky" communication > with the service and I can testify that this will DEFINITELY degrad
> your performance. It can also complicate the contract (WSDL) of the
> services you're trying to consume.
>
> Ron Jacobs is a Product Manager at Microsoft for the Patterns &
> Practices group and does a great deal of writing and public speaking on > web services and service-oriented architectures. Take a look at this
> link:
>
> http://www.ronjacobs.com/talks.htm
>
> Have a look at the "Patterns for SOA" presentation. While this talk
> looks at SOA as a whole, the patterns proposed (including "Document
> Processor" which I summarize in my initial post) are excellent
> guidelines for writing performant and loosely-coupled web services that > maintain the integrity of the service contract as well.
>
> HTH
>
> Thanks,
> Denny Boynton
>
>


Nov 23 '05 #10

P: n/a
From a previous posting I made on this subject we have found the following
holds true:

Interestingly we have discovered that in this scenario we don't have a return
type defined but what seems to happen on the client side proxy is the first
output parameter becomes the return type and the new output parameter becomes
part of the functions parameter list an example is shown below:

Before adding new output parameter:
server definition: void X(int i, out int j)
client proxy defintion: void X(int i, out int j)
After adding new output parameter:
server definition: void X(int i, out int j, out string k)
client proxy defintion: int X(int i, out string k)
"David" wrote:
I experience this problem very frequently on both 2000 Pro and XP Pro
machines. My issue is that I update the web service itself and then
when I go to update the web service it doesn't update it at all. I can
dramatically change the web service and at random the update web
service does not regenerate the proxy class with the new settings.

I would really love to know how to fix this issue.

Steven Cheng[MSFT] wrote:
Thanks for your response el_sid,

So have you tried add webreference/ update webreference from this services
from some other development machines? Based on my local test on some
machine, the update webreference operations should not generate randomly
result fo the proxy code. I still think it might be a machine specific
problem.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcXDQUtdIap2eeoLQMqr0GSzF0F7+w==
X-WBNR-Posting-Host: 158.234.10.144
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
<A2**********************************@microsoft.co m>
<rp*************@TK2MSFTNGXA01.phx.gbl>
Subject: Re: Updating Web References in .NET 2003
Date: Tue, 27 Sep 2005 01:56:05 -0700
Lines: 137
Message-ID: <E5**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices:8030
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

We see this on all our XP develipment machines running with XP SP 1 and
.NET
framework 1.1 with SP1.

"Steven Cheng[MSFT]" wrote:
Hi el_sid,

Thanks for posting in MSDN newsgroup.
As for the VS.NET's "add webreference" and "update web reference"

command,
they're doing the same operation as the WSDL.exe utility. Based on my
research, there haven't any explicit cache in these proxy generating
operations. As for the caching problem, I'm wondering whether it's a
environment specific issue such as the networking condition. Also, as for
===============
the the results seem to be unpredictable and sometimes
===============
do you mean the updated proxy content will be randomly changed, for
example, when I use the "update web reference" serveral times for the

same
service proxy, the generated proxy will be different? If so, that really
seems strange, I think you can try testing this on different machine to

see
whether you continously get the same behavior.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)


--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcWzwx6Z76pl7XL1R1eaNulFQQPNrA==
X-WBNR-Posting-Host: 158.234.10.144
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
Subject: Re: Updating Web References in .NET 2003
Date: Wed, 7 Sep 2005 08:45:06 -0700
Lines: 61
Message-ID: <A2**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices:7813
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

Interestingly we have discovered that in this scenario we don't have a
return
type defined but what seems to happen on the client side proxy is the

first
output parameter becomes the return type and the new output parameter
becomes
part of the functions parameter list an example is shown below:

Before adding new output parameter:
server definition: void X(int i, out int j)
client proxy defintion: void X(int i, out int j)
After adding new output parameter:
server definition: void X(int i, out int j, out string k)
client proxy defintion: int X(int i, out string k)


"el_sid" wrote:

> Thanks for the info, but an interesting thing we have found with our
previous
> project (we went down the route of using complex data types there) that
we
> found the opposite was true. We had definite perofrmance degregation
until
> we started using simple data types on the system and then we noticed a
major
> performance increase. So we will probably keep with the simple data
types on
> this project and hope someone comes up with the reason why the

references
> aren't being upated.
>
>
> "Denny Boynton" wrote:
>
> > I'm very familiar with that document. It covers general .NET
> > application development and, as such, I generally agree with the
> > content of that document. However, once you start using web services
> > and enter the realm of "service-orientation," the rules do change
> > somewhat.
> >
> > It sounds like you're using very RPC style interfaces on your web
> > services. This will promote more "chatty" versus "chunky"

communication
> > with the service and I can testify that this will DEFINITELY degrad
> > your performance. It can also complicate the contract (WSDL) of the
> > services you're trying to consume.
> >
> > Ron Jacobs is a Product Manager at Microsoft for the Patterns &
> > Practices group and does a great deal of writing and public speaking

on
> > web services and service-oriented architectures. Take a look at this
> > link:
> >
> > http://www.ronjacobs.com/talks.htm
> >
> > Have a look at the "Patterns for SOA" presentation. While this talk
> > looks at SOA as a whole, the patterns proposed (including "Document
> > Processor" which I summarize in my initial post) are excellent
> > guidelines for writing performant and loosely-coupled web services

that
> > maintain the integrity of the service contract as well.
> >
> > HTH
> >
> > Thanks,
> > Denny Boynton
> >
> >


Nov 23 '05 #11

P: n/a
Hi el_sid,

Thanks for your response.
So seems the behavior on your side is different from mine, from my local
test, no matter the webmethod's signature is
void X(int i, out int j)
or void X(int i, out int j, out string k)

the generated client proxy will always convert the first out paremater as
the return value. Also, as for the random or caching behavior, it may due
to some other thing related to the enviornment or IDE. Does you got this
behavior on all the dev boxes with VS.NET 2003 IDE?

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)


--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcXE2VkSWhlmbxRhSzWX1yenlpmepw==
X-WBNR-Posting-Host: 158.234.10.144
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
<A2**********************************@microsoft.co m>
<rp*************@TK2MSFTNGXA01.phx.gbl>
<E5**********************************@microsoft.co m>
<Zl*************@TK2MSFTNGXA01.phx.gbl>
<11**********************@g49g2000cwa.googlegroups .com>
Subject: Re: Updating Web References in .NET 2003
Date: Thu, 29 Sep 2005 02:37:03 -0700
Lines: 227
Message-ID: <6F**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices:8056
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

From a previous posting I made on this subject we have found the following
holds true:

Interestingly we have discovered that in this scenario we don't have a
return
type defined but what seems to happen on the client side proxy is the first
output parameter becomes the return type and the new output parameter
becomes
part of the functions parameter list an example is shown below:

Before adding new output parameter:
server definition: void X(int i, out int j)
client proxy defintion: void X(int i, out int j)
After adding new output parameter:
server definition: void X(int i, out int j, out string k)
client proxy defintion: int X(int i, out string k)
"David" wrote:
I experience this problem very frequently on both 2000 Pro and XP Pro
machines. My issue is that I update the web service itself and then
when I go to update the web service it doesn't update it at all. I can
dramatically change the web service and at random the update web
service does not regenerate the proxy class with the new settings.

I would really love to know how to fix this issue.

Steven Cheng[MSFT] wrote:
Thanks for your response el_sid,

So have you tried add webreference/ update webreference from this services from some other development machines? Based on my local test on some
machine, the update webreference operations should not generate randomly
result fo the proxy code. I still think it might be a machine specific
problem.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcXDQUtdIap2eeoLQMqr0GSzF0F7+w==
X-WBNR-Posting-Host: 158.234.10.144
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
<A2**********************************@microsoft.co m>
<rp*************@TK2MSFTNGXA01.phx.gbl>
Subject: Re: Updating Web References in .NET 2003
Date: Tue, 27 Sep 2005 01:56:05 -0700
Lines: 137
Message-ID: <E5**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices:8030
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

We see this on all our XP develipment machines running with XP SP 1 and
.NET
framework 1.1 with SP1.

"Steven Cheng[MSFT]" wrote:
Hi el_sid,

Thanks for posting in MSDN newsgroup.
As for the VS.NET's "add webreference" and "update web reference"

command,
they're doing the same operation as the WSDL.exe utility. Based on my
research, there haven't any explicit cache in these proxy generating
operations. As for the caching problem, I'm wondering whether it's a
environment specific issue such as the networking condition. Also, as for ===============
the the results seem to be unpredictable and sometimes
===============
do you mean the updated proxy content will be randomly changed, for
example, when I use the "update web reference" serveral times for the

same
service proxy, the generated proxy will be different? If so, that really seems strange, I think you can try testing this on different machine to
see
whether you continously get the same behavior.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)


--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcWzwx6Z76pl7XL1R1eaNulFQQPNrA==
X-WBNR-Posting-Host: 158.234.10.144
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
Subject: Re: Updating Web References in .NET 2003
Date: Wed, 7 Sep 2005 08:45:06 -0700
Lines: 61
Message-ID: <A2**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices:7813
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

Interestingly we have discovered that in this scenario we don't have a
return
type defined but what seems to happen on the client side proxy is the

first
output parameter becomes the return type and the new output parameter
becomes
part of the functions parameter list an example is shown below:

Before adding new output parameter:
server definition: void X(int i, out int j)
client proxy defintion: void X(int i, out int j)
After adding new output parameter:
server definition: void X(int i, out int j, out string k)
client proxy defintion: int X(int i, out string k)


"el_sid" wrote:

> Thanks for the info, but an interesting thing we have found with our
previous
> project (we went down the route of using complex data types there)
that we
> found the opposite was true. We had definite perofrmance degregation until
> we started using simple data types on the system and then we noticed a major
> performance increase. So we will probably keep with the simple data
types on
> this project and hope someone comes up with the reason why the

references
> aren't being upated.
>
>
> "Denny Boynton" wrote:
>
> > I'm very familiar with that document. It covers general .NET
> > application development and, as such, I generally agree with the
> > content of that document. However, once you start using web services > > and enter the realm of "service-orientation," the rules do change
> > somewhat.
> >
> > It sounds like you're using very RPC style interfaces on your web
> > services. This will promote more "chatty" versus "chunky"

communication
> > with the service and I can testify that this will DEFINITELY degrad > > your performance. It can also complicate the contract (WSDL) of the > > services you're trying to consume.
> >
> > Ron Jacobs is a Product Manager at Microsoft for the Patterns &
> > Practices group and does a great deal of writing and public speaking on
> > web services and service-oriented architectures. Take a look at

this > > link:
> >
> > http://www.ronjacobs.com/talks.htm
> >
> > Have a look at the "Patterns for SOA" presentation. While this talk > > looks at SOA as a whole, the patterns proposed (including "Document > > Processor" which I summarize in my initial post) are excellent
> > guidelines for writing performant and loosely-coupled web services

that
> > maintain the integrity of the service contract as well.
> >
> > HTH
> >
> > Thanks,
> > Denny Boynton
> >
> >



Nov 23 '05 #12

P: n/a
This behavour is common on all our development boxes and we have also updated
to SP1 and still see this problem.

"Steven Cheng[MSFT]" wrote:
Hi el_sid,

Thanks for your response.
So seems the behavior on your side is different from mine, from my local
test, no matter the webmethod's signature is
void X(int i, out int j)
or void X(int i, out int j, out string k)

the generated client proxy will always convert the first out paremater as
the return value. Also, as for the random or caching behavior, it may due
to some other thing related to the enviornment or IDE. Does you got this
behavior on all the dev boxes with VS.NET 2003 IDE?

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)


--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcXE2VkSWhlmbxRhSzWX1yenlpmepw==
X-WBNR-Posting-Host: 158.234.10.144
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
<A2**********************************@microsoft.co m>
<rp*************@TK2MSFTNGXA01.phx.gbl>
<E5**********************************@microsoft.co m>
<Zl*************@TK2MSFTNGXA01.phx.gbl>
<11**********************@g49g2000cwa.googlegroups .com>
Subject: Re: Updating Web References in .NET 2003
Date: Thu, 29 Sep 2005 02:37:03 -0700
Lines: 227
Message-ID: <6F**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices:8056
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

From a previous posting I made on this subject we have found the following
holds true:

Interestingly we have discovered that in this scenario we don't have a
return
type defined but what seems to happen on the client side proxy is the first
output parameter becomes the return type and the new output parameter
becomes
part of the functions parameter list an example is shown below:

Before adding new output parameter:
server definition: void X(int i, out int j)
client proxy defintion: void X(int i, out int j)
After adding new output parameter:
server definition: void X(int i, out int j, out string k)
client proxy defintion: int X(int i, out string k)
"David" wrote:
I experience this problem very frequently on both 2000 Pro and XP Pro
machines. My issue is that I update the web service itself and then
when I go to update the web service it doesn't update it at all. I can
dramatically change the web service and at random the update web
service does not regenerate the proxy class with the new settings.

I would really love to know how to fix this issue.

Steven Cheng[MSFT] wrote:
Thanks for your response el_sid,

So have you tried add webreference/ update webreference from this services from some other development machines? Based on my local test on some
machine, the update webreference operations should not generate randomly
result fo the proxy code. I still think it might be a machine specific
problem.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcXDQUtdIap2eeoLQMqr0GSzF0F7+w==
X-WBNR-Posting-Host: 158.234.10.144
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
<A2**********************************@microsoft.co m>
<rp*************@TK2MSFTNGXA01.phx.gbl>
Subject: Re: Updating Web References in .NET 2003
Date: Tue, 27 Sep 2005 01:56:05 -0700
Lines: 137
Message-ID: <E5**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices:8030
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

We see this on all our XP develipment machines running with XP SP 1 and
.NET
framework 1.1 with SP1.

"Steven Cheng[MSFT]" wrote:

> Hi el_sid,
>
> Thanks for posting in MSDN newsgroup.
> As for the VS.NET's "add webreference" and "update web reference"
command,
> they're doing the same operation as the WSDL.exe utility. Based on my
> research, there haven't any explicit cache in these proxy generating
> operations. As for the caching problem, I'm wondering whether it's a
> environment specific issue such as the networking condition. Also, as for > ===============
> the the results seem to be unpredictable and sometimes
> ===============
> do you mean the updated proxy content will be randomly changed, for
> example, when I use the "update web reference" serveral times for the
same
> service proxy, the generated proxy will be different? If so, that really > seems strange, I think you can try testing this on different machine to see
> whether you continously get the same behavior.
>
> Thanks,
>
> Steven Cheng
> Microsoft Online Support
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
>
>
>
>
>
>
> --------------------
> Thread-Topic: Updating Web References in .NET 2003
> thread-index: AcWzwx6Z76pl7XL1R1eaNulFQQPNrA==
> X-WBNR-Posting-Host: 158.234.10.144
> From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
> References: <E9**********************************@microsoft.co m>
> <11*********************@g44g2000cwa.googlegroups. com>
> <4D**********************************@microsoft.co m>
> <11**********************@f14g2000cwb.googlegroups .com>
> <4D**********************************@microsoft.co m>
> Subject: Re: Updating Web References in .NET 2003
> Date: Wed, 7 Sep 2005 08:45:06 -0700
> Lines: 61
> Message-ID: <A2**********************************@microsoft.co m>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="Utf-8"
> Content-Transfer-Encoding: 7bit
> X-Newsreader: Microsoft CDO for Windows 2000
> Content-Class: urn:content-classes:message
> Importance: normal
> Priority: normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> Newsgroups: microsoft.public.dotnet.framework.webservices
> NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
> Xref: TK2MSFTNGXA01.phx.gbl
> microsoft.public.dotnet.framework.webservices:7813
> X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
>
> Interestingly we have discovered that in this scenario we don't have a
> return
> type defined but what seems to happen on the client side proxy is the
first
> output parameter becomes the return type and the new output parameter
> becomes
> part of the functions parameter list an example is shown below:
>
> Before adding new output parameter:
> server definition: void X(int i, out int j)
> client proxy defintion: void X(int i, out int j)
>
>
> After adding new output parameter:
> server definition: void X(int i, out int j, out string k)
> client proxy defintion: int X(int i, out string k)
>
>
>
>
> "el_sid" wrote:
>
> > Thanks for the info, but an interesting thing we have found with our
> previous
> > project (we went down the route of using complex data types there) that > we
> > found the opposite was true. We had definite perofrmance degregation > until
> > we started using simple data types on the system and then we noticed a > major
> > performance increase. So we will probably keep with the simple data
> types on
> > this project and hope someone comes up with the reason why the
references
> > aren't being upated.
> >
> >
> > "Denny Boynton" wrote:
> >
> > > I'm very familiar with that document. It covers general .NET
> > > application development and, as such, I generally agree with the
> > > content of that document. However, once you start using web services > > > and enter the realm of "service-orientation," the rules do change
> > > somewhat.
> > >
> > > It sounds like you're using very RPC style interfaces on your web
> > > services. This will promote more "chatty" versus "chunky"
communication
> > > with the service and I can testify that this will DEFINITELY degrad > > > your performance. It can also complicate the contract (WSDL) of the > > > services you're trying to consume.
> > >
> > > Ron Jacobs is a Product Manager at Microsoft for the Patterns &
> > > Practices group and does a great deal of writing and public speaking on
> > > web services and service-oriented architectures. Take a look at this > > > link:
> > >
> > > http://www.ronjacobs.com/talks.htm
> > >
> > > Have a look at the "Patterns for SOA" presentation. While this talk > > > looks at SOA as a whole, the patterns proposed (including "Document > > > Processor" which I summarize in my initial post) are excellent
> > > guidelines for writing performant and loosely-coupled web services
that
> > > maintain the integrity of the service contract as well.
> > >
> > > HTH
> > >
> > > Thanks,
> > > Denny Boynton
> > >
> > >
>

Nov 23 '05 #13

P: n/a
Thanks for your followup el_sid,

If the problem occurs on multiple machines in your environment, due to the
complexity of the problem and the limited support through newsgroup , I'd
suggest that you try contacting PSS for thorough troubleshooting on this.
You can contact Microsoft Product Support directly to discuss additional
support options you may have available, by contacting us at 1-(800)936-5800
or by choosing one of the options listed at
http://support.microsoft.com/default...d=sz;en-us;top.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security

--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcXLJTMNiWmcc78rTvKREwsAYs9bRQ==
X-WBNR-Posting-Host: 158.234.250.71
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
<A2**********************************@microsoft.co m>
<rp*************@TK2MSFTNGXA01.phx.gbl>
<E5**********************************@microsoft.co m>
<Zl*************@TK2MSFTNGXA01.phx.gbl>
<11**********************@g49g2000cwa.googlegroups .com>
<6F**********************************@microsoft.co m>
<xC*************@TK2MSFTNGXA01.phx.gbl>
Subject: Re: Updating Web References in .NET 2003
Date: Fri, 7 Oct 2005 02:55:08 -0700
Lines: 305
Message-ID: <28**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices:8147
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

This behavour is common on all our development boxes and we have also
updated
to SP1 and still see this problem.

"Steven Cheng[MSFT]" wrote:
Hi el_sid,

Thanks for your response.
So seems the behavior on your side is different from mine, from my local
test, no matter the webmethod's signature is
void X(int i, out int j)
or void X(int i, out int j, out string k)

the generated client proxy will always convert the first out paremater as
the return value. Also, as for the random or caching behavior, it may due
to some other thing related to the enviornment or IDE. Does you got this
behavior on all the dev boxes with VS.NET 2003 IDE?

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)


--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcXE2VkSWhlmbxRhSzWX1yenlpmepw==
X-WBNR-Posting-Host: 158.234.10.144
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
<A2**********************************@microsoft.co m>
<rp*************@TK2MSFTNGXA01.phx.gbl>
<E5**********************************@microsoft.co m>
<Zl*************@TK2MSFTNGXA01.phx.gbl>
<11**********************@g49g2000cwa.googlegroups .com>
Subject: Re: Updating Web References in .NET 2003
Date: Thu, 29 Sep 2005 02:37:03 -0700
Lines: 227
Message-ID: <6F**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices:8056
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

From a previous posting I made on this subject we have found the following holds true:

Interestingly we have discovered that in this scenario we don't have a
return
type defined but what seems to happen on the client side proxy is the first output parameter becomes the return type and the new output parameter
becomes
part of the functions parameter list an example is shown below:

Before adding new output parameter:
server definition: void X(int i, out int j)
client proxy defintion: void X(int i, out int j)
After adding new output parameter:
server definition: void X(int i, out int j, out string k)
client proxy defintion: int X(int i, out string k)
"David" wrote:
I experience this problem very frequently on both 2000 Pro and XP Pro
machines. My issue is that I update the web service itself and then
when I go to update the web service it doesn't update it at all. I can
dramatically change the web service and at random the update web
service does not regenerate the proxy class with the new settings.

I would really love to know how to fix this issue.

Steven Cheng[MSFT] wrote:
Thanks for your response el_sid,

So have you tried add webreference/ update webreference from this services from some other development machines? Based on my local test on some
machine, the update webreference operations should not generate randomly result fo the proxy code. I still think it might be a machine specific
problem.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcXDQUtdIap2eeoLQMqr0GSzF0F7+w==
X-WBNR-Posting-Host: 158.234.10.144
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
<A2**********************************@microsoft.co m>
<rp*************@TK2MSFTNGXA01.phx.gbl>
Subject: Re: Updating Web References in .NET 2003
Date: Tue, 27 Sep 2005 01:56:05 -0700
Lines: 137
Message-ID: <E5**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices:8030
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

We see this on all our XP develipment machines running with XP SP 1 and .NET
framework 1.1 with SP1.

"Steven Cheng[MSFT]" wrote:

> Hi el_sid,
>
> Thanks for posting in MSDN newsgroup.
> As for the VS.NET's "add webreference" and "update web reference"
command,
> they're doing the same operation as the WSDL.exe utility. Based on my > research, there haven't any explicit cache in these proxy generating
> operations. As for the caching problem, I'm wondering whether it's a
> environment specific issue such as the networking condition. Also, as for > ===============
> the the results seem to be unpredictable and sometimes
> ===============
> do you mean the updated proxy content will be randomly changed, for
> example, when I use the "update web reference" serveral times for the same
> service proxy, the generated proxy will be different? If so, that really > seems strange, I think you can try testing this on different machine
to
see
> whether you continously get the same behavior.
>
> Thanks,
>
> Steven Cheng
> Microsoft Online Support
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers
no > rights.)
>
>
>
>
>
>
>
>
> --------------------
> Thread-Topic: Updating Web References in .NET 2003
> thread-index: AcWzwx6Z76pl7XL1R1eaNulFQQPNrA==
> X-WBNR-Posting-Host: 158.234.10.144
> From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
> References: <E9**********************************@microsoft.co m>
> <11*********************@g44g2000cwa.googlegroups. com>
> <4D**********************************@microsoft.co m>
> <11**********************@f14g2000cwb.googlegroups .com>
> <4D**********************************@microsoft.co m>
> Subject: Re: Updating Web References in .NET 2003
> Date: Wed, 7 Sep 2005 08:45:06 -0700
> Lines: 61
> Message-ID: <A2**********************************@microsoft.co m>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="Utf-8"
> Content-Transfer-Encoding: 7bit
> X-Newsreader: Microsoft CDO for Windows 2000
> Content-Class: urn:content-classes:message
> Importance: normal
> Priority: normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> Newsgroups: microsoft.public.dotnet.framework.webservices
> NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl > Xref: TK2MSFTNGXA01.phx.gbl
> microsoft.public.dotnet.framework.webservices:7813
> X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
>
> Interestingly we have discovered that in this scenario we don't have a > return
> type defined but what seems to happen on the client side proxy is the first
> output parameter becomes the return type and the new output parameter > becomes
> part of the functions parameter list an example is shown below:
>
> Before adding new output parameter:
> server definition: void X(int i, out int j)
> client proxy defintion: void X(int i, out int j)
>
>
> After adding new output parameter:
> server definition: void X(int i, out int j, out string k)
> client proxy defintion: int X(int i, out string k)
>
>
>
>
> "el_sid" wrote:
>
> > Thanks for the info, but an interesting thing we have found with our > previous
> > project (we went down the route of using complex data types there)
that > we
> > found the opposite was true. We had definite perofrmance degregation > until
> > we started using simple data types on the system and then we noticed a > major
> > performance increase. So we will probably keep with the simple
data > types on
> > this project and hope someone comes up with the reason why the
references
> > aren't being upated.
> >
> >
> > "Denny Boynton" wrote:
> >
> > > I'm very familiar with that document. It covers general .NET
> > > application development and, as such, I generally agree with the
> > > content of that document. However, once you start using web

services > > > and enter the realm of "service-orientation," the rules do change > > > somewhat.
> > >
> > > It sounds like you're using very RPC style interfaces on your web > > > services. This will promote more "chatty" versus "chunky"
communication
> > > with the service and I can testify that this will DEFINITELY degrad > > > your performance. It can also complicate the contract (WSDL) of the > > > services you're trying to consume.
> > >
> > > Ron Jacobs is a Product Manager at Microsoft for the Patterns &
> > > Practices group and does a great deal of writing and public speaking on
> > > web services and service-oriented architectures. Take a look at this > > > link:
> > >
> > > http://www.ronjacobs.com/talks.htm
> > >
> > > Have a look at the "Patterns for SOA" presentation. While this talk > > > looks at SOA as a whole, the patterns proposed (including "Document > > > Processor" which I summarize in my initial post) are excellent
> > > guidelines for writing performant and loosely-coupled web services that
> > > maintain the integrity of the service contract as well.
> > >
> > > HTH
> > >
> > > Thanks,
> > > Denny Boynton
> > >
> > >
>


Nov 23 '05 #14

P: n/a
LNP
I experience the same problem on my XP Pro machine. When I update the
webservice and update the web reference it still shows the old stuff. Even I
delete the webreference then create it again, the problem's still there.
Seems like it's MS bug. Any suggestion or work around will be much
appreciated.

"Steven Cheng[MSFT]" wrote:
Thanks for your followup el_sid,

If the problem occurs on multiple machines in your environment, due to the
complexity of the problem and the limited support through newsgroup , I'd
suggest that you try contacting PSS for thorough troubleshooting on this.
You can contact Microsoft Product Support directly to discuss additional
support options you may have available, by contacting us at 1-(800)936-5800
or by choosing one of the options listed at
http://support.microsoft.com/default...d=sz;en-us;top.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security

--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcXLJTMNiWmcc78rTvKREwsAYs9bRQ==
X-WBNR-Posting-Host: 158.234.250.71
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
<A2**********************************@microsoft.co m>
<rp*************@TK2MSFTNGXA01.phx.gbl>
<E5**********************************@microsoft.co m>
<Zl*************@TK2MSFTNGXA01.phx.gbl>
<11**********************@g49g2000cwa.googlegroups .com>
<6F**********************************@microsoft.co m>
<xC*************@TK2MSFTNGXA01.phx.gbl>
Subject: Re: Updating Web References in .NET 2003
Date: Fri, 7 Oct 2005 02:55:08 -0700
Lines: 305
Message-ID: <28**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices:8147
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

This behavour is common on all our development boxes and we have also
updated
to SP1 and still see this problem.

"Steven Cheng[MSFT]" wrote:
Hi el_sid,

Thanks for your response.
So seems the behavior on your side is different from mine, from my local
test, no matter the webmethod's signature is
void X(int i, out int j)
or void X(int i, out int j, out string k)

the generated client proxy will always convert the first out paremater as
the return value. Also, as for the random or caching behavior, it may due
to some other thing related to the enviornment or IDE. Does you got this
behavior on all the dev boxes with VS.NET 2003 IDE?

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)


--------------------
Thread-Topic: Updating Web References in .NET 2003
thread-index: AcXE2VkSWhlmbxRhSzWX1yenlpmepw==
X-WBNR-Posting-Host: 158.234.10.144
From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
References: <E9**********************************@microsoft.co m>
<11*********************@g44g2000cwa.googlegroups. com>
<4D**********************************@microsoft.co m>
<11**********************@f14g2000cwb.googlegroups .com>
<4D**********************************@microsoft.co m>
<A2**********************************@microsoft.co m>
<rp*************@TK2MSFTNGXA01.phx.gbl>
<E5**********************************@microsoft.co m>
<Zl*************@TK2MSFTNGXA01.phx.gbl>
<11**********************@g49g2000cwa.googlegroups .com>
Subject: Re: Updating Web References in .NET 2003
Date: Thu, 29 Sep 2005 02:37:03 -0700
Lines: 227
Message-ID: <6F**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.webservices:8056
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

From a previous posting I made on this subject we have found the

following
holds true:

Interestingly we have discovered that in this scenario we don't have a
return
type defined but what seems to happen on the client side proxy is the

first
output parameter becomes the return type and the new output parameter
becomes
part of the functions parameter list an example is shown below:

Before adding new output parameter:
server definition: void X(int i, out int j)
client proxy defintion: void X(int i, out int j)
After adding new output parameter:
server definition: void X(int i, out int j, out string k)
client proxy defintion: int X(int i, out string k)
"David" wrote:
I experience this problem very frequently on both 2000 Pro and XP Pro
machines. My issue is that I update the web service itself and then
when I go to update the web service it doesn't update it at all. I can
dramatically change the web service and at random the update web
service does not regenerate the proxy class with the new settings.

I would really love to know how to fix this issue.

Steven Cheng[MSFT] wrote:
> Thanks for your response el_sid,
>
> So have you tried add webreference/ update webreference from this

services
> from some other development machines? Based on my local test on some
> machine, the update webreference operations should not generate randomly > result fo the proxy code. I still think it might be a machine specific
> problem.
>
> Thanks,
>
> Steven Cheng
> Microsoft Online Support
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
> --------------------
> Thread-Topic: Updating Web References in .NET 2003
> thread-index: AcXDQUtdIap2eeoLQMqr0GSzF0F7+w==
> X-WBNR-Posting-Host: 158.234.10.144
> From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
> References: <E9**********************************@microsoft.co m>
> <11*********************@g44g2000cwa.googlegroups. com>
> <4D**********************************@microsoft.co m>
> <11**********************@f14g2000cwb.googlegroups .com>
> <4D**********************************@microsoft.co m>
> <A2**********************************@microsoft.co m>
> <rp*************@TK2MSFTNGXA01.phx.gbl>
> Subject: Re: Updating Web References in .NET 2003
> Date: Tue, 27 Sep 2005 01:56:05 -0700
> Lines: 137
> Message-ID: <E5**********************************@microsoft.co m>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="Utf-8"
> Content-Transfer-Encoding: 7bit
> X-Newsreader: Microsoft CDO for Windows 2000
> Content-Class: urn:content-classes:message
> Importance: normal
> Priority: normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> Newsgroups: microsoft.public.dotnet.framework.webservices
> NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSF TNGXA03.phx.gbl > Xref: TK2MSFTNGXA01.phx.gbl
> microsoft.public.dotnet.framework.webservices:8030
> X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
>
> We see this on all our XP develipment machines running with XP SP 1 and > .NET
> framework 1.1 with SP1.
>
> "Steven Cheng[MSFT]" wrote:
>
> > Hi el_sid,
> >
> > Thanks for posting in MSDN newsgroup.
> > As for the VS.NET's "add webreference" and "update web reference"
> command,
> > they're doing the same operation as the WSDL.exe utility. Based on my > > research, there haven't any explicit cache in these proxy generating
> > operations. As for the caching problem, I'm wondering whether it's a
> > environment specific issue such as the networking condition. Also,

as for
> > ===============
> > the the results seem to be unpredictable and sometimes
> > ===============
> > do you mean the updated proxy content will be randomly changed, for
> > example, when I use the "update web reference" serveral times for the > same
> > service proxy, the generated proxy will be different? If so, that

really
> > seems strange, I think you can try testing this on different machine
to
> see
> > whether you continously get the same behavior.
> >
> > Thanks,
> >
> > Steven Cheng
> > Microsoft Online Support
> >
> > Get Secure! www.microsoft.com/security
> > (This posting is provided "AS IS", with no warranties, and confers

no > > rights.)
> >
> >
> >
> >
> >
> >
> >
> >
> > --------------------
> > Thread-Topic: Updating Web References in .NET 2003
> > thread-index: AcWzwx6Z76pl7XL1R1eaNulFQQPNrA==
> > X-WBNR-Posting-Host: 158.234.10.144
> > From: =?Utf-8?B?ZWxfc2lk?= <el****@newsgroup.nospam>
> > References: <E9**********************************@microsoft.co m>
> > <11*********************@g44g2000cwa.googlegroups. com>
> > <4D**********************************@microsoft.co m>
> > <11**********************@f14g2000cwb.googlegroups .com>
> > <4D**********************************@microsoft.co m>
> > Subject: Re: Updating Web References in .NET 2003
> > Date: Wed, 7 Sep 2005 08:45:06 -0700
> > Lines: 61
> > Message-ID: <A2**********************************@microsoft.co m>
> > MIME-Version: 1.0
> > Content-Type: text/plain;
> > charset="Utf-8"
> > Content-Transfer-Encoding: 7bit
> > X-Newsreader: Microsoft CDO for Windows 2000
> > Content-Class: urn:content-classes:message
> > Importance: normal
> > Priority: normal
> > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> > Newsgroups: microsoft.public.dotnet.framework.webservices
> > NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> > Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl > > Xref: TK2MSFTNGXA01.phx.gbl
> > microsoft.public.dotnet.framework.webservices:7813
> > X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
> >
> > Interestingly we have discovered that in this scenario we don't have a > > return
> > type defined but what seems to happen on the client side proxy is the > first
> > output parameter becomes the return type and the new output parameter > > becomes
> > part of the functions parameter list an example is shown below:
> >

Nov 23 '05 #15

This discussion thread is closed

Replies have been disabled for this discussion.