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 / March 2005

Tip: Looking for answers? Try searching our database.

WSE SP3 WSDLs and the 2003 IDE

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Mike - 21 Mar 2005 15:51 GMT
1. What exe does the VS IDE use to generate ws proxy classes under WSE SP3? I
just renamed Wsdl.EXE and WseWsdl2.exe and the IDE still generated a proxy. I
sure would've expected WseWsdl2.exe to be the one it used.

2. To make it easier for the client to add web references, I have combined
the over 40 web services in my project into a single WSDL. This also keeps me
from having to deal with converting like objects between services (i.e. A
person class in the web service1 proxy is NOT a person in the web service2
proxy because of namespace differences).

Problem is, in the generated proxy class only the first class inherits from
Microsoft.Web.Services2.WebServicesClientProtocol. The remaining classes
inherit from System.Web.Services.Protocols.SoapHttpClientProtocol. This won't
work, as I'm using WSE for all of my security and I need the -Wse proxy
classes.

Any thoughts? I sure like having all my ws references combined in 1, and I
surely like not having to deal with different 'person' classes, but this is
driving me nuts.

Thanks in advance,
Mike
Yves Reynhout - 22 Mar 2005 22:40 GMT
> 1. What exe does the VS IDE use to generate ws proxy classes under WSE SP3? I
> just renamed Wsdl.EXE and WseWsdl2.exe and the IDE still generated a proxy. I
[quoted text clipped - 18 lines]
> Thanks in advance,
> Mike

1. Have a "reflection" at WseSettings2.dll. It contains a ToolInstaller
class (derived from System.Configuration.Install.Installer) which
modifies the wsdl.exe.config and devenv.exe.config to include a class
WseExtensionImporter (which is responsible for the codegeneration when
you do an "Add Webreference"). Probably this assembly "WseSettings2.dll"
is called during setup of WSE 2.0 SP3, which explains how the "magic" works.
2. This maybe a bug (it's probably related to the implementation of
WseExtensionImporter). Fancy writing your own SoapExtensionImporter?

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.