Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / September 2004

Tip: Looking for answers? Try searching our database.

Using dynamic url changes generated proxy

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Dominick Baier - 14 Sep 2004 06:02 GMT
a general advice:

leave the generated classes untouched. if you want to customize the proxy in any way, inherit from the proxy and to your customisation there.

use the inherited class in your app to call the webservice.

in this way you can modify the proxy behaviour (e.g. reading some values from config files,add properties...) and can always regenerate the web proxy without loosing your changes...



---
Dominick Baier - DevelopMentor
http://www.leastprivilege.com

  nntp://news.microsoft.com/microsoft.public.dotnet.framework.webservices.enhancements/<58965B43-293D-4119-B948-1EA0D13FBEAA@microsoft.com>

I am using WSE 2.0 sp1 and have several web-references to webservices in my
project. Using the web-reference property pages I changed the URL behaviour
from static to dynamic and now the classes that end with wse are no longer
generated.

I am using Visual Studio .NET 2003 and running XP Pro SP1.

Has anyone run across this problem? Better yet does anyone have a solution?

Larry
larry dot guger at online dash can dot com.

[microsoft.public.dotnet.framework.webservices.enhancements]
lguger - 14 Sep 2004 14:17 GMT
To clarify:

I am changing the URL behaviour on the web reference properties from within
Visual Studio's Solution Explorer and not actually touching the code.  After
the property is changed in solution explorer Studio regenerates the code and
the newly generated code no longer contains the wse specific class.

Larry

> a general advice:
>
[quoted text clipped - 25 lines]
>  
>  [microsoft.public.dotnet.framework.webservices.enhancements]
Lguger - 20 Sep 2004 22:31 GMT
The solution, as it turns out, was to simply update the web reference in the
project after cahnging the url to dynamic and the WSE classes were back.  So
simple... <sigh>

> To clarify:
>
[quoted text clipped - 34 lines]
> >  
> >  [microsoft.public.dotnet.framework.webservices.enhancements]

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.