Re: Updating Web References in .NET 2003
- From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng[MSFT])
- Date: Mon, 10 Oct 2005 09:26:17 GMT
{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\lang2052\f0\fs20 Thanks for your followup el_sid,
\par
\par 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.
\par 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.aspx?scid=sz;en-us;top.
\par
\par Thanks,
\par
\par Steven Cheng
\par Microsoft Online Support
\par
\par Get Secure! www.microsoft.com/security
\par
\par
\par
\par
\par
\par \pard\li720 --------------------
\par Thread-Topic: Updating Web References in .NET 2003
\par thread-index: AcXLJTMNiWmcc78rTvKREwsAYs9bRQ==
\par X-WBNR-Posting-Host: 158.234.250.71
\par From: =?Utf-8?B?ZWxfc2lk?= <el_sid@xxxxxxxxxxxxxxxx>
\par References: <E95B3281-3A32-4639-9A43-D73A270619F9@xxxxxxxxxxxxx> <1124311403.556686.47960@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4D349288-71F8-4903-83CD-6A0B50F964CD@xxxxxxxxxxxxx> <1124393783.118404.197700@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4D230A46-9F96-4577-A748-439D6EA59278@xxxxxxxxxxxxx> <A225FFFE-BE92-4645-A58B-0FB8CB54F3C3@xxxxxxxxxxxxx> <rpH8n$zwFHA.780@xxxxxxxxxxxxxxxxxxxxx> <E548DBCF-02DC-4501-9E66-1C5A165549CE@xxxxxxxxxxxxx> <ZleoqTAxFHA.768@xxxxxxxxxxxxxxxxxxxxx> <1127929868.750491.293480@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <6F9FFE23-925E-4C11-A55A-BAE6B7703D72@xxxxxxxxxxxxx> <xCfWKuZxFHA.768@xxxxxxxxxxxxxxxxxxxxx>
\par Subject: Re: Updating Web References in .NET 2003
\par Date: Fri, 7 Oct 2005 02:55:08 -0700
\par Lines: 305
\par Message-ID: <28C4B62C-92E4-4823-A9DA-8AC99D657E83@xxxxxxxxxxxxx>
\par MIME-Version: 1.0
\par Content-Type: text/plain;
\par \tab charset="Utf-8"
\par Content-Transfer-Encoding: 7bit
\par X-Newsreader: Microsoft CDO for Windows 2000
\par Content-Class: urn:content-classes:message
\par Importance: normal
\par Priority: normal
\par X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
\par Newsgroups: microsoft.public.dotnet.framework.webservices
\par NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
\par Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
\par Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.dotnet.framework.webservices:8147
\par X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
\par
\par This behavour is common on all our development boxes and we have also updated
\par to SP1 and still see this problem.
\par
\par "Steven Cheng[MSFT]" wrote:
\par
\par > Hi el_sid,
\par >
\par > Thanks for your response.
\par > So seems the behavior on your side is different from mine, from my local
\par > test, no matter the webmethod's signature is
\par > void X(int i, out int j)
\par > or void X(int i, out int j, out string k)
\par >
\par > the generated client proxy will always convert the first out paremater as
\par > the return value. Also, as for the random or caching behavior, it may due
\par > to some other thing related to the enviornment or IDE. Does you got this
\par > behavior on all the dev boxes with VS.NET 2003 IDE?
\par >
\par > Steven Cheng
\par > Microsoft Online Support
\par >
\par > Get Secure! www.microsoft.com/security
\par > (This posting is provided "AS IS", with no warranties, and confers no
\par > rights.)
\par >
\par >
\par >
\par >
\par > --------------------
\par > Thread-Topic: Updating Web References in .NET 2003
\par > thread-index: AcXE2VkSWhlmbxRhSzWX1yenlpmepw==
\par > X-WBNR-Posting-Host: 158.234.10.144
\par > From: =?Utf-8?B?ZWxfc2lk?= <el_sid@xxxxxxxxxxxxxxxx>
\par > References: <E95B3281-3A32-4639-9A43-D73A270619F9@xxxxxxxxxxxxx>
\par > <1124311403.556686.47960@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
\par > <4D349288-71F8-4903-83CD-6A0B50F964CD@xxxxxxxxxxxxx>
\par > <1124393783.118404.197700@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
\par > <4D230A46-9F96-4577-A748-439D6EA59278@xxxxxxxxxxxxx>
\par > <A225FFFE-BE92-4645-A58B-0FB8CB54F3C3@xxxxxxxxxxxxx>
\par > <rpH8n$zwFHA.780@xxxxxxxxxxxxxxxxxxxxx>
\par > <E548DBCF-02DC-4501-9E66-1C5A165549CE@xxxxxxxxxxxxx>
\par > <ZleoqTAxFHA.768@xxxxxxxxxxxxxxxxxxxxx>
\par > <1127929868.750491.293480@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
\par > Subject: Re: Updating Web References in .NET 2003
\par > Date: Thu, 29 Sep 2005 02:37:03 -0700
\par > Lines: 227
\par > Message-ID: <6F9FFE23-925E-4C11-A55A-BAE6B7703D72@xxxxxxxxxxxxx>
\par > MIME-Version: 1.0
\par > Content-Type: text/plain;
\par > \tab charset="Utf-8"
\par > Content-Transfer-Encoding: 7bit
\par > X-Newsreader: Microsoft CDO for Windows 2000
\par > Content-Class: urn:content-classes:message
\par > Importance: normal
\par > Priority: normal
\par > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
\par > Newsgroups: microsoft.public.dotnet.framework.webservices
\par > NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
\par > Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
\par > Xref: TK2MSFTNGXA01.phx.gbl
\par > microsoft.public.dotnet.framework.webservices:8056
\par > X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
\par >
\par > From a previous posting I made on this subject we have found the following
\par > holds true:
\par >
\par > Interestingly we have discovered that in this scenario we don't have a
\par > return
\par > type defined but what seems to happen on the client side proxy is the first
\par > output parameter becomes the return type and the new output parameter
\par > becomes
\par > part of the functions parameter list an example is shown below:
\par >
\par > Before adding new output parameter:
\par > server definition: void X(int i, out int j)
\par > client proxy defintion: void X(int i, out int j)
\par >
\par >
\par > After adding new output parameter:
\par > server definition: void X(int i, out int j, out string k)
\par > client proxy defintion: int X(int i, out string k)
\par >
\par >
\par > "David" wrote:
\par >
\par > > I experience this problem very frequently on both 2000 Pro and XP Pro
\par > > machines. My issue is that I update the web service itself and then
\par > > when I go to update the web service it doesn't update it at all. I can
\par > > dramatically change the web service and at random the update web
\par > > service does not regenerate the proxy class with the new settings.
\par > >
\par > > I would really love to know how to fix this issue.
\par > >
\par > > Steven Cheng[MSFT] wrote:
\par > > > Thanks for your response el_sid,
\par > > >
\par > > > So have you tried add webreference/ update webreference from this
\par > services
\par > > > from some other development machines? Based on my local test on some
\par > > > machine, the update webreference operations should not generate randomly
\par > > > result fo the proxy code. I still think it might be a machine specific
\par > > > problem.
\par > > >
\par > > > Thanks,
\par > > >
\par > > > Steven Cheng
\par > > > Microsoft Online Support
\par > > >
\par > > > Get Secure! www.microsoft.com/security
\par > > > (This posting is provided "AS IS", with no warranties, and confers no
\par > > > rights.)
\par > > >
\par > > >
\par > > > --------------------
\par > > > Thread-Topic: Updating Web References in .NET 2003
\par > > > thread-index: AcXDQUtdIap2eeoLQMqr0GSzF0F7+w==
\par > > > X-WBNR-Posting-Host: 158.234.10.144
\par > > > From: =?Utf-8?B?ZWxfc2lk?= <el_sid@xxxxxxxxxxxxxxxx>
\par > > > References: <E95B3281-3A32-4639-9A43-D73A270619F9@xxxxxxxxxxxxx>
\par > > > <1124311403.556686.47960@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
\par > > > <4D349288-71F8-4903-83CD-6A0B50F964CD@xxxxxxxxxxxxx>
\par > > > <1124393783.118404.197700@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
\par > > > <4D230A46-9F96-4577-A748-439D6EA59278@xxxxxxxxxxxxx>
\par > > > <A225FFFE-BE92-4645-A58B-0FB8CB54F3C3@xxxxxxxxxxxxx>
\par > > > <rpH8n$zwFHA.780@xxxxxxxxxxxxxxxxxxxxx>
\par > > > Subject: Re: Updating Web References in .NET 2003
\par > > > Date: Tue, 27 Sep 2005 01:56:05 -0700
\par > > > Lines: 137
\par > > > Message-ID: <E548DBCF-02DC-4501-9E66-1C5A165549CE@xxxxxxxxxxxxx>
\par > > > MIME-Version: 1.0
\par > > > Content-Type: text/plain;
\par > > > \tab charset="Utf-8"
\par > > > Content-Transfer-Encoding: 7bit
\par > > > X-Newsreader: Microsoft CDO for Windows 2000
\par > > > Content-Class: urn:content-classes:message
\par > > > Importance: normal
\par > > > Priority: normal
\par > > > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
\par > > > Newsgroups: microsoft.public.dotnet.framework.webservices
\par > > > NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
\par > > > Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
\par > > > Xref: TK2MSFTNGXA01.phx.gbl
\par > > > microsoft.public.dotnet.framework.webservices:8030
\par > > > X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
\par > > >
\par > > > We see this on all our XP develipment machines running with XP SP 1 and
\par > > > .NET
\par > > > framework 1.1 with SP1.
\par > > >
\par > > > "Steven Cheng[MSFT]" wrote:
\par > > >
\par > > > > Hi el_sid,
\par > > > >
\par > > > > Thanks for posting in MSDN newsgroup.
\par > > > > As for the VS.NET's "add webreference" and "update web reference"
\par > > > command,
\par > > > > they're doing the same operation as the WSDL.exe utility. Based on my
\par > > > > research, there haven't any explicit cache in these proxy generating
\par > > > > operations. As for the caching problem, I'm wondering whether it's a
\par > > > > environment specific issue such as the networking condition. Also,
\par > as for
\par > > > > ===============
\par > > > > the the results seem to be unpredictable and sometimes
\par > > > > ===============
\par > > > > do you mean the updated proxy content will be randomly changed, for
\par > > > > example, when I use the "update web reference" serveral times for the
\par > > > same
\par > > > > service proxy, the generated proxy will be different? If so, that
\par > really
\par > > > > seems strange, I think you can try testing this on different machine
\par > to
\par > > > see
\par > > > > whether you continously get the same behavior.
\par > > > >
\par > > > > Thanks,
\par > > > >
\par > > > > Steven Cheng
\par > > > > Microsoft Online Support
\par > > > >
\par > > > > Get Secure! www.microsoft.com/security
\par > > > > (This posting is provided "AS IS", with no warranties, and confers no
\par > > > > rights.)
\par > > > >
\par > > > >
\par > > > >
\par > > > >
\par > > > >
\par > > > >
\par > > > >
\par > > > >
\par > > > > --------------------
\par > > > > Thread-Topic: Updating Web References in .NET 2003
\par > > > > thread-index: AcWzwx6Z76pl7XL1R1eaNulFQQPNrA==
\par > > > > X-WBNR-Posting-Host: 158.234.10.144
\par > > > > From: =?Utf-8?B?ZWxfc2lk?= <el_sid@xxxxxxxxxxxxxxxx>
\par > > > > References: <E95B3281-3A32-4639-9A43-D73A270619F9@xxxxxxxxxxxxx>
\par > > > > <1124311403.556686.47960@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
\par > > > > <4D349288-71F8-4903-83CD-6A0B50F964CD@xxxxxxxxxxxxx>
\par > > > > <1124393783.118404.197700@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
\par > > > > <4D230A46-9F96-4577-A748-439D6EA59278@xxxxxxxxxxxxx>
\par > > > > Subject: Re: Updating Web References in .NET 2003
\par > > > > Date: Wed, 7 Sep 2005 08:45:06 -0700
\par > > > > Lines: 61
\par > > > > Message-ID: <A225FFFE-BE92-4645-A58B-0FB8CB54F3C3@xxxxxxxxxxxxx>
\par > > > > MIME-Version: 1.0
\par > > > > Content-Type: text/plain;
\par > > > > \tab charset="Utf-8"
\par > > > > Content-Transfer-Encoding: 7bit
\par > > > > X-Newsreader: Microsoft CDO for Windows 2000
\par > > > > Content-Class: urn:content-classes:message
\par > > > > Importance: normal
\par > > > > Priority: normal
\par > > > > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
\par > > > > Newsgroups: microsoft.public.dotnet.framework.webservices
\par > > > > NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
\par > > > > Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
\par > > > > Xref: TK2MSFTNGXA01.phx.gbl
\par > > > > microsoft.public.dotnet.framework.webservices:7813
\par > > > > X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
\par > > > >
\par > > > > Interestingly we have discovered that in this scenario we don't have a
\par > > > > return
\par > > > > type defined but what seems to happen on the client side proxy is the
\par > > > first
\par > > > > output parameter becomes the return type and the new output parameter
\par > > > > becomes
\par > > > > part of the functions parameter list an example is shown below:
\par > > > >
\par > > > > Before adding new output parameter:
\par > > > > server definition: void X(int i, out int j)
\par > > > > client proxy defintion: void X(int i, out int j)
\par > > > >
\par > > > >
\par > > > > After adding new output parameter:
\par > > > > server definition: void X(int i, out int j, out string k)
\par > > > > client proxy defintion: int X(int i, out string k)
\par > > > >
\par > > > >
\par > > > >
\par > > > >
\par > > > > "el_sid" wrote:
\par > > > >
\par > > > > > Thanks for the info, but an interesting thing we have found with our
\par > > > > previous
\par > > > > > project (we went down the route of using complex data types there)
\par > that
\par > > > > we
\par > > > > > found the opposite was true. We had definite perofrmance
\par > degregation
\par > > > > until
\par > > > > > we started using simple data types on the system and then we
\par > noticed a
\par > > > > major
\par > > > > > performance increase. So we will probably keep with the simple data
\par > > > > types on
\par > > > > > this project and hope someone comes up with the reason why the
\par > > > references
\par > > > > > aren't being upated.
\par > > > > >
\par > > > > >
\par > > > > > "Denny Boynton" wrote:
\par > > > > >
\par > > > > > > I'm very familiar with that document. It covers general .NET
\par > > > > > > application development and, as such, I generally agree with the
\par > > > > > > content of that document. However, once you start using web
\par > services
\par > > > > > > and enter the realm of "service-orientation," the rules do change
\par > > > > > > somewhat.
\par > > > > > >
\par > > > > > > It sounds like you're using very RPC style interfaces on your web
\par > > > > > > services. This will promote more "chatty" versus "chunky"
\par > > > communication
\par > > > > > > with the service and I can testify that this will DEFINITELY
\par > degrad
\par > > > > > > your performance. It can also complicate the contract (WSDL) of
\par > the
\par > > > > > > services you're trying to consume.
\par > > > > > >
\par > > > > > > Ron Jacobs is a Product Manager at Microsoft for the Patterns &
\par > > > > > > Practices group and does a great deal of writing and public
\par > speaking
\par > > > on
\par > > > > > > web services and service-oriented architectures. Take a look at
\par > this
\par > > > > > > link:
\par > > > > > >
\par > > > > > > http://www.ronjacobs.com/talks.htm
\par > > > > > >
\par > > > > > > Have a look at the "Patterns for SOA" presentation. While this
\par > talk
\par > > > > > > looks at SOA as a whole, the patterns proposed (including
\par > "Document
\par > > > > > > Processor" which I summarize in my initial post) are excellent
\par > > > > > > guidelines for writing performant and loosely-coupled web services
\par > > > that
\par > > > > > > maintain the integrity of the service contract as well.
\par > > > > > >
\par > > > > > > HTH
\par > > > > > >
\par > > > > > > Thanks,
\par > > > > > > Denny Boynton
\par > > > > > >
\par > > > > > >
\par > > > >
\par > >
\par \pard
\par
\par }
- Follow-Ups:
- Re: Updating Web References in .NET 2003
- From: LNP
- Re: Updating Web References in .NET 2003
- References:
- Re: Updating Web References in .NET 2003
- From: el_sid
- Re: Updating Web References in .NET 2003
- Prev by Date:
WSDL generation of types - Next by Date:
Re: Object to hold settings - Previous by thread:
Re: Updating Web References in .NET 2003 - Next by thread:
Re: Updating Web References in .NET 2003 - Index(es):