svcutil document literal wrapped

I'm trying to develop a wcf web service using a wsdl supplied by a vendor. Comments in the wsdl indicate that it is "designed using the Document Literal Wrapped pattern". The results of svcutil says that it is generating a message contract since the operation is neither RPC nor document wrapped. Is there something I can do to the wsdl before I run svcutil to get it to work?
LVL 1
trgbAsked:
Who is Participating?
 
Anil GolamariCommented:
Take a look at below url and it should ans your question with some code samples.

http://msdn.microsoft.com/en-us/library/aa347733.aspx
0
 
Grant SpiteriSenior consultantCommented:
Not to sure but why dont you create your own proxy?
0
 
Anil GolamariCommented:
Using svcutil, you can create interfaces and classes (data contracts) from the WSDL.

svcutil your.wsdl (or svcutil your.wsdl /l:vb if you want Visual Basic)

This will create a file called "your.cs" in C# (or "your.vb" in VB.NET) which contains all the necessary items.

Now, you need to create a class "MyService" which will implement the service interface (IServiceInterface) - or the several service interfaces - and this is your server instance.

Now a class by itself doesn't really help yet - you'll need to host the service somewhere. You need to either create your own ServiceHost instance which hosts the service, configure endpoints and so forth - or you can host your service inside IIS.
0
 
trgbAuthor Commented:
I'm new to this, obviously, and have another question. In the tutorials I've done I had to define ServiceContracts OperationContracts and DataContracts. Why doesn't svcutil include those definitions?
0
 
trgbAuthor Commented:
Thanks. I think I get it now.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.