Re: Updating Web References in .NET 2003
- From: "David" <thechod@xxxxxxxxx>
- Date: 28 Sep 2005 10:51:08 -0700
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_sid@xxxxxxxxxxxxxxxx>
> 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>
> Subject: Re: Updating Web References in .NET 2003
> Date: Tue, 27 Sep 2005 01:56:05 -0700
> Lines: 137
> Message-ID: <E548DBCF-02DC-4501-9E66-1C5A165549CE@xxxxxxxxxxxxx>
> 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!TK2MSFTNGXA03.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_sid@xxxxxxxxxxxxxxxx>
> > 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>
> > Subject: Re: Updating Web References in .NET 2003
> > Date: Wed, 7 Sep 2005 08:45:06 -0700
> > Lines: 61
> > Message-ID: <A225FFFE-BE92-4645-A58B-0FB8CB54F3C3@xxxxxxxxxxxxx>
> > 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!TK2MSFTNGXA03.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
> > > >
> > > >
> >
.
- Follow-Ups:
- Re: Updating Web References in .NET 2003
- From: el_sid
- 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
- From: Steven Cheng[MSFT]
- Re: Updating Web References in .NET 2003
- From: el_sid
- Re: Updating Web References in .NET 2003
- From: Steven Cheng[MSFT]
- Re: Updating Web References in .NET 2003
- Prev by Date: Re: Form Posting Problem
- Next by Date: RE: Timeout value at the client proxy
- Previous by thread: Re: Updating Web References in .NET 2003
- Next by thread: Re: Updating Web References in .NET 2003
- Index(es):
Relevant Pages
|