Developer .NET UPDATE—brought to you by Windows & .NET Magazine Network.
THIS ISSUE SPONSORED BY
Windows & .NET Magazine LIVE!
(below DEVELOPER .NET PERSPECTIVES)
SPONSOR: MICROSOFT ASP.NET CONNECTIONS
Attend Microsoft ASP.NET Connections, VS.NET Connections, or SQL Server Magazine LIVE! and you could win a brand new Harley Davidson 100th Anniversary Sportster 883 XLH motorcycle. One attendee will leave owning this Harley, which will be on display in the Exhibit Hall throughout the conference.
Register today for any one of the three conferences and you'll get access to the other two events for FREE. Over 160 sessions to choose from, and you'll save $2,790. Last Chance to register, as these events begin October 27.
This deal gets even better: Stay for the week and save a total of $4,785 when you also register for either XML Web Services Connections or Windows & .NET Magazine LIVE!. Register for the entire week and you'll get access to five conferences and 240 sessions. Last Chance to register, go to:
October 22, 2002—In this issue:
1. DEVELOPER .NET PERSPECTIVES
- Exploring UDDI
- Subscribe to Windows & .NET Magazine and Receive an eBook Gift!
- Get Connected with Connected Home
3. NEW AND IMPROVED
- Leverage .NET Development with the Eiffel Language Plug-In
4. CONTACT US
- See this section for a list of ways to contact us.
1. DEVELOPER .NET PERSPECTIVES
(contributed by Bill Sheldon, email@example.com)
If you've been working with XML Web services in Visual Studio .NET, you might be familiar with Universal Description, Discovery, and Integration. UDDI is the term used to describe how Web services are "advertised." Most developers are familiar with how to use UDDI at design time to retrieve the Web Services Description Language (WSDL) file associated with a Web service, but few are familiar with how to use UDDI at runtime.
If you go to http://uddi.microsoft.com/developer/default.aspx, you'll find Microsoft's UDDI portal for developers. The UDDI portal is the yellow pages for Web services—it provides a way for developers to find out about published Web services. If you have a Web service that's publicly available, posting a reference to it (i.e., advertising it) on this site lets other developers and businesses find your service at design time. Using a public forum to advertise a Web service, however, has two limitations:
- If you want to publish your Web service to only developers within your organization (and not developers worldwide), the public UDDI site isn't an appropriate forum. This site is for Web services meant for public consumption.
- When you create a Web service-based implementation in the current version of Visual Studio .NET, you create a link to a Web service on a server. Thus, after you've referenced UDDI at design time, you've locked your implementation to a specific Web service. If you change the Web service's location, you can't notify those people who previously used the portal to locate your service about the new URL.
When Microsoft releases Windows .NET Server (Win.NET Server) 2003, you'll be able to overcome these limitations. Win.NET Server provides an optional feature called Enterprise UDDI Services, which lets you create a private UDDI publishing server. Thus, you can set up a server within your organization to test the Web services you're planning to publish or publish Web services that are for internal consumption only.
Win.NET Server's Enterprise UDDI Services supports UDDI 2.0 Programmer's API and UDDI 1.0 Programmer's API. You can also use a programmatic API to interact with Enterprise UDDI Services. Thus, you can automatically add and remove Web services as you define them, which is great as you begin to create dozens of Web services within your organization. You can get more information about Enterprise UDDI Services at:
In addition to letting you advertise Web services internally, Enterprise UDDI Services provides a way for you to change the implementation if that necessity arises in the future. To understand how Enterprise UDDI Services eliminates the second limitation, you need to examine what Visual Studio .NET does. When you use Visual Studio .NET to create a Web service, you get a WSDL file that includes a reference to the server that's hosting the Web service. In many ways, this reference is the root of the problem because if you rely on the WSDL file, you're reliant on the URL.
Enterprise UDDI Services changes this situation by making the environment more like that of a COM-based development. A COM object's definition in the system registry contains information about a physical path on the hard disk. Because of that path information, developers can reference that object without needing to know its physical location on the system. The layer of abstraction that COM provides about the physical location of objects on the local system is similar to the level of abstraction that UDDI provides regarding the physical location of the Web services.
The long-term power of using UDDI and WSDL to create a Web service-based implementation is that you have a truly distributed computing environment. The ability to decouple the implementation from the interface, which was previously available only in desktop development, becomes available across a heterogeneous WAN. The central system registry on the desktop is replaced by a distributed UDDI server. And the Interface Definition Language (IDL), which defines the interfaces that a COM object exposes, is replaced by the WSDL, which describes the Simple Object Access Protocol (SOAP) interfaces associated with the distributed objects.
Currently, Enterprise UDDI Services might not be quite up to release standards. When Win.NET Server gets released, you can expect to see updates to the available tools. To start exploring how to take advantage of UDDI not just as a design-time protocol to find and reuse Web services but also as a tool to provide runtime abstraction, check out UDDI .NET software development kit (SDK) 2.0 Beta 1. You can find UDDI .NET SDK 2.0 Beta 1 and lots of other reference information at:
Finally, a quick note to those of you who requested copies of my project source files to use as examples: I'm still adding some comments and installation instructions. I'll send those files to you as soon as possible.
SPONSOR: WINDOWS & .NET MAGAZINE LIVE!
Real-World Tips and Solutions Here for You
Register now for Windows & .NET Magazine LIVE! and attend concurrently run XML Web Services Connections sessions for FREE. These conferences are chock full of "been there, done that" information from people who use these technologies in the real world.
Last week to register:
Extend your stay to include preceding conferences Microsoft ASP.NET Connections, VS.NET Connections, or SQL Server Magazine LIVE! and you may leave with a brand new Harley Davidson motorcycle. Registration ends this week, so click now for more details:
(brought to you by Windows & .NET Magazine and its partners)
Windows & .NET Magazine is a problem-solving manual designed to help systems administrators better manage their Windows 2000 and Windows NT enterprise. Subscribe today and, with your paid subscription, you can choose from one of three eBooks about Active Directory, public key infrastructure, or automating tasks with VBScript. Subscribe now!
If you haven't seen Connected Home Online lately, you're missing the definitive resource to help you tackle home automation, install a home network, set up a home theater, and much more. Visit today, and while you're there, check out this article about installing a 100Mbps home network at http://www.connectedhomemag.com/networking/articles/index.cfm?articleid=24765. Check it out!
3. NEW AND IMPROVED
(contributed by Sue Cooper, firstname.lastname@example.org)
Eiffel Software released Eiffel ENViSioN!, a plug-in for Visual Studio .NET that lets you use the Eiffel language at the same level as the other Microsoft .NET languages. The plug-in's "code once, run on many platforms" feature lets you migrate applications to and from different platforms, and use component libraries across platforms. The Eiffel language's objects offer greater reusability than objects created with other languages. Eiffel is the only .NET language to offer multiple inheritance and "genericity" (i.e., support for type-parameterized class modules). Eiffel also supports contract mechanisms natively, as an actual language construct. Eiffel ENViSioN! runs on Windows XP, Windows 2000, and Windows NT. The cost is $999 per license. A free, non-expiring version is available, but this version doesn’t include all features or allow commercial development. Contact Eiffel Software at 805-685-1006 or email@example.com.
4. CONTACT US
Here's how to reach us with your comments and questions:
- ABOUT DEVELOPER .NET PERSPECTIVES — firstname.lastname@example.org
- ABOUT THE NEWSLETTER IN GENERAL — email@example.com
(please mention the newsletter name in the subject line)
- TECHNICAL QUESTIONS — http://www.winnetmag.net/forums
- PRODUCT NEWS — firstname.lastname@example.org
- QUESTIONS ABOUT YOUR DEVELOPER .NET UPDATE SUBSCRIPTION?
Customer Support — Developer_dot_NET_update@winnetmag.com
- WANT TO SPONSOR DEVELOPER .NET UPDATE?
This weekly email newsletter is brought to you by Windows & .NET Magazine, the leading publication for Windows professionals who want to learn more and perform better. Subscribe today.
Receive the latest information about the Windows and .NET topics of your choice. Subscribe to our other FREE email newsletters.