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 / January 2006

Tip: Looking for answers? Try searching our database.

Manipulating/Changing the way proxies are generated

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ido Flatow - 28 Jan 2006 10:20 GMT
Hi all,

I've been exploring the way I can manipulate WSDL.exe using
SchemaImporterExtension in order to create a proxy to my liking.

My situation is as follows - I have a web site that has multiple asmx files,
some of them share the same data types (the famous "Order" example).

What I want is this final result:
- A class file that holds all the proxy classes, but no data types
- A class file that holds all the data type, but no proxy classes

So far, I achieved the first by deriving from SchemaImporterExtension and
change that every time a data type is used, it is referenced by another
namespace, therefore the data types are not generated in the first file.

The second file is the problematic one - How can I use the
SchemaImporterExtension class (or any other class) to manipulate the way the
proxies are created ? or to be more specific - How can I instruct the
wsdl.exe not to generate proxy code ?

Thanks in advance,
Ido.
Dale - 29 Jan 2006 02:13 GMT
Well, lacking any better suggestions coming in, let me take a crack at this.  
I was waiting to see if someone was going to pipe in with a suggestion of
some wiz-bang tool that would export a proxy out of a class library.  That
would be perfect for your needs.  I did a cursory search and didn't find one.

One thing I am certain of, is that you can't do what you ask by manipulating
WSDL.exe.

I think you'll have to create the proxy with WSDL.exe as a starting point,
make two copies, and edit them both to provide what you want.  Or hand code
both proxies from scratch.

HTH
Signature

Dale Preston
MCAD C#
MCSE, MCDBA

> Hi all,
>
[quoted text clipped - 19 lines]
> Thanks in advance,
> Ido.
Ido Flatow - 29 Jan 2006 08:39 GMT
Hi Dale,
I too gave up on WSDL, so i've looked around a bit, and found a simple app
named "SED" (originated in unix) that manipulates text files.
I wrote a small script for it that finds every proxy declaration in the
generated code and deletes it - so very simple and so very stupid !

Sometimes a simple tool can be the answer ...

Thanks anyway,
Ido.

> Well, lacking any better suggestions coming in, let me take a crack at this.  
> I was waiting to see if someone was going to pipe in with a suggestion of
[quoted text clipped - 33 lines]
> > Thanks in advance,
> > Ido.

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.