Manipulating/Changing the way proxies are generated

[Ido Flatow]

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]

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
--
Dale Preston
MCAD C#
MCSE, MCDBA
"Ido Flatow" wrote:

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.

[Ido Flatow]

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.

"Dale" wrote:

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
--
Dale Preston
MCAD C#
MCSE, MCDBA
"Ido Flatow" wrote:

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.