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 / August 2004

Tip: Looking for answers? Try searching our database.

Splitting Up WSDL issue

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Mauricio Arroyo - 07 Aug 2004 00:00 GMT
Hi,

I used the excellent article
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/html/
service08202002.asp

from Scott Seely to have a webservice interface defined in a separated wsdl
file. It works just fine, but when I try to navigate to the wsdl from Visual
Studio I get a message "No Ports or Methods were found on this page.". I'm
still able to add the web reference and every thing works fine. (if I point
to the asmx it works but one of the methods is not showed)

The problem is that using another tool, one of the clients is not able to
add the reference to the wsdl, and it may be related to this "No ports..."
message. Is it some way to avoid this message and have the Visual Studio to
look for ports and Methods in the Binding file?

Thanks in advance.

Mauricio
Eric Cherng - 08 Aug 2004 22:50 GMT
Which version of Visual Studio are you running? Visual Studio .NET 2002 had
a limitation where it cannot reference other files your WSDL depends on
(<import> references in the <types> element in your WSDL file). This
limitation has been removed from VS.NET 2003.

The other thing you can do is use the command line tool wsdl.exe.

Eric

Signature

Eric Cherng
MCP, MCDBA, MCSD
http://echerng.com

> Hi,
>
> I used the excellent article

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/html/
service08202002.asp

> from Scott Seely to have a webservice interface defined in a separated wsdl
> file. It works just fine, but when I try to navigate to the wsdl from Visual
[quoted text clipped - 10 lines]
>
> Mauricio
Mauricio Arroyo - 09 Aug 2004 18:36 GMT
Eric, thank you for your answer. I'm using VS.NET 2003 Framework 1.1, the
tool my client is using is GeneXus (I don't know it). Maybe the reason VS is
not seeing the Ports (showing the No Ports message) is related to why
GeneXus is not able to get a reference to my webService. Any help would be
really appreciated.

Thanks again.

> Which version of Visual Studio are you running? Visual Studio .NET 2002 had
> a limitation where it cannot reference other files your WSDL depends on
[quoted text clipped - 8 lines]
> >
> > I used the excellent article

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/html/
service08202002.asp

> > from Scott Seely to have a webservice interface defined in a separated
> wsdl
[quoted text clipped - 14 lines]
> >
> > Mauricio

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.