Odd problem with WSE
- From: "B.E.S." <bryanslatner@xxxxxxxxxxxxxxxx>
- Date: Thu, 4 Jan 2007 19:07:30 -0500
I have a WSDL provided to me by one of our partners.
I have Visual Studio 2003, WSE 1.0 (latest SP), and WSE 2.0 (SP3) installed
on this development machine.
I created a C# console application for testing. I enabled the project for
WSE 2.0 support and added a web reference using the WSDL my partner
provided. The proxy client class with the "Wse" extension was NOT created. I
went into Reference.cs for and verified that it was missing. I saw one class
called CommonOrdering (the name of the service). I expected to see another
called CommonOrderingWse, but I did not.
I then disabled WSE 2.0 support on the project and removed the web
reference. Then I enabled WSE 1.0 support and added the web reference back.
This time, the CommonOrderingWse proxy client class was created.
I moved to a 2nd development machine with VS 2005 and WSE 3.0 on it, created
a test application, and added a reference and the CommonOrderingWse proxy
client class was created.
So I'm flummoxed: what am I doing wrong with WSE 2.0?
If anyone needs it, the WSDL can be downloaded from
http://www.slatner.com/quick/test.wsdl
Thanks,
Bryan
.
- Follow-Ups:
- RE: Odd problem with WSE
- From: Steven Cheng[MSFT]
- RE: Odd problem with WSE
- Prev by Date: WSE 3.0 - WSE2013 Error VS2005
- Next by Date: Re: wse custom headers
- Previous by thread: WSE 3.0 - WSE2013 Error VS2005
- Next by thread: RE: Odd problem with WSE
- Index(es):
Relevant Pages
|