Drew's Blog

The Joys of Technology Explored

How To Get Intellisense For WSDL

...

You can use VS.NET as an XML editor, but that is all. Maybe the next major release will have a graphical WSDL (or generally spoken Web Services contract) designer with support to leverage existing XML Schemas.

...

[Christian Weyer: Web Services & .NET ]

What you can do is save the WSDL XML Schema into a file and put it into the <VS.NET Install Dir>\Common7\Packages\schemas\xml directory. Once you do this and you start definining your instance document, as soon as you define a node with the WSDL namespace, you'll get intellisense support for it.

Actually, the title is a little misleading as this feature of VS.NET applies to any XML specification for which there is an XML Schema defined, including your own!

Posted: Apr 14 2003, 02:26 PM by drub0y | with 4 comment(s)
Filed under:

Comments

Christian Weyer said:

Ahh - this is actually cool. But as you can guess this might only be the start of a long story ...
You know what I mean: graphical editor etc. ... just take a look at the tools I listed in my original post.

But your suggestion is definitely something I have to try out!

Cheers,
Christian
# April 14, 2003 1:38 PM

Drew Marsh said:

Yeah, it doesn't cover the graphical side of your argument at all. However, I'm perfectly happy typing my XML today, so the intellisense is a big productivity booster.
# April 14, 2003 3:20 PM

Don Box said:

Here's hoping that Yasser will get a VS.NET-hosted WSDL editor/designer in our lifetimes.

Go Yasser!

DB
# April 14, 2003 8:15 PM

Jim Murphy said:

If VSIP wasn't so damn onerous we'd have a choice between at least 3 graphical WSDL editors today!

Common guys - "Chinese Household" - Quit beating your wives!
# April 29, 2003 12:41 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)