> svcutil.exe *.wsdl *.xsd

"Geir Forsmo" <geir.forsmo@gmail.com> wrote in message
news:7294edb2-a2a5-4432-b4f3-015aa0c2ebb3@i12g2000prf.googlegroups.com...
> Hi!
>
> I am trying to create a web service from a wsdl from a external part.
> The external part is running as a client, but forces us to use their
> wsdl specification because they are communicating against several
> other parts which also must follow their wsdl contract. Now we are the
> only one that is implementing our web service in .net. The other ones
> have implemented their web service on the bea weblogic platform (java)
> and therefore has an easier integration.
>
> Some have told me to use the original wdsl as a static wsdl to my web
> service and in this way could be the client call my web service. If
> some of you have done this or have some experience with static wsdl
> please let me know. I won't really like to see an asp.net web service
> example that uses a static wsdl.
>
> Hope you can help me with this.
>
> regards
>
> Geir F

On 1 Mar, 02:59, "Tiago Halm" <th...@nospam.hotmail.com> wrote:
> Get the wsdl/xsd files, and then generate the client proxy with:
>
> > svcutil.exe *.wsdl *.xsd
>
> Tiago Halm
>
> "Geir Forsmo" <geir.for...@gmail.com> wrote in message
>
> news:7294edb2-a2a5-4432-b4f3-015aa0c2ebb3@i12g2000prf.googlegroups.com...
>
> > Hi!
>
> > I am trying to create a web service from a wsdl from a external part.
> > The external part is running as a client, but forces us to use their
> > wsdl specification because they are communicating against several
> > other parts which also must follow their wsdl contract. Now we are the
> > only one that is implementing our web service in .net. The other ones
> > have implemented their web service on the bea weblogic platform (java)
> > and therefore has an easier integration.
>
> > Some have told me to use the original wdsl as a static wsdl to my web
> > service and in this way could be the client call my web service. If
> > some of you have done this or have some experience with static wsdl
> > please let me know. I won't really like to see an asp.net web service
> > example that uses a static wsdl.
>
> > Hope you can help me with this.
>
> > regards
>
> > Geir F

On Mar 5, 12:29=A0pm, Geir Forsmo <geir.for...@gmail.com> wrote:
> On 1 Mar, 02:59, "Tiago Halm" <th...@nospam.hotmail.com> wrote:
>
>
>
>
>
> > Get the wsdl/xsd files, and then generate the client proxy with:
>
> > > svcutil.exe *.wsdl *.xsd
>
> >Tiago Halm
>
> > "Geir Forsmo" <geir.for...@gmail.com> wrote in message
>
> >news:7294edb2-a2a5-4432-b4f3-015aa0c2ebb3@i12g2000prf.googlegroups.com...=

>
> > > Hi!
>
> > > I am trying to create a web service from a wsdl from a external part.
> > > The external part is running as a client, but forces us to use their
> > > wsdl specification because they are communicating against several
> > > other parts which also must follow their wsdl contract. Now we are the=

> > > only one that is implementing our web service in .net. The other ones
> > > have implemented their web service on the bea weblogic platform (java)=

> > > and therefore has an easier integration.
>
> > > Some have told me to use the original wdsl as a static wsdl to my web
> > > service and in this way could be the client call my web service. If
> > > some of you have done this or have some experience with static wsdl
> > > please let me know. I won't really like to see an asp.net web service
> > > example that uses a static wsdl.
>
> > > Hope you can help me with this.
>
> > > regards
>
> > > Geir F
>
> Hi again. Where do I find svcutil?
>
> regards
>
> Geir F- Hide quoted text -
>
> - Show quoted text -