3

The LA Fox Developer Newsletter
November 2000
Boot Camp (Con’t from page 1)

If time permits, wrap up with how to build a complete Visual FoxPro application.

Full speaker notes and several very useful Visual FoxPro base classes will be distributed to all attendees.


Accelerated Internet session from the basics of Visual FoxPro to the advanced topics of ASP and COM objects

This session is geared toward programmers with a working knowledge of FoxPro 2.6 and/or Visual FoxPro. It will cover basics, object oriented programming, using Visual FoxPro as the database part of a web server, Active Server Pages (ASP) and COM objects.

The following topics will be discussed:

Using Web forms and techniques in Visual FoxPro Windows applications
Using Visual FoxPro on your web server: Tips, tricks, techniques, ASP, and COM

Visually defined objects

Objects defined in code

Generating an HTML Page from Visual FoxPro

HTML transfers from FrontPage to Visual FoxPro

Assign/Access methods

Creating COM objects

Using COM objects in ASP pages

Questions will be entertained throughout the day. Handouts will include how to setup Visual FoxPro on your web server, working code examples, and more.


Touch of Humor...
+ If Fed Ex and UPS were to merge, would they call it Fed UP?
+ Do Lipton employees take coffee breaks?
+ What hair color do they put on the driver’s licenses of bald
men?

Lots O’Stuff...
For Sale
Liquidation Sale. Now’s your chance to get that piece of office furniture you’ve always wanted. Desks, chairs, whiteboards, cabinets, tables.. .the complete list is too large to include here. For a complete listing and to find out more, call 714.968.4225 (between 9-5) or e-mail brlee@earthlink.net.
Getting Ready for “.NET”...
The Programmable Web: Web
Services Provides Building
Blocks for the
Microsoft .NET Framework
By Mary Kirtland
fSUMMARY: Web Services are building blocks for constructing distributed Web-based applications in a platform, object model, and multilanguage manner. Web Services are based on open Internet standards, such as HTTP and XML, and form the basis of Microsoft’s vision of the programmable Web. This article defines Web Services and the key enabling technologies that ensure services can be aggregated into applications. It then describes Microsoft’s new Micmsoft .NET Framework and its support for creating and consuming Web Services. ]

One of today’s most pressing challenges is application integration: taking different applications running on different operating systems built with different object models using different programming languages and turning them into easy-to-use Web applications. The Microsoft vision of Web Services, based on open Web standards such as HTTP and XML, addresses this challenge.

But supporting standard protocols isn’t enough. There must be some way to create, deploy, scale, and maintain these Web Services. This is where the Microsoft® .NET Framework comes
in.

This article describes Web Services and the components of the Microsoft .NET Framework, including the common language runtime, the services framework, and the programming models for building and integrating Web Services.

A Look at Web Services
Broadly speaking, a Web Service is simply an application delivered as a service that can be integrated with other Web Services using Internet standards. In other words, it’s a URLaddressable resource that programmatically returns information to clients who want to use it. One important feature of Web Services is that clients don’t need to know how a service is implemented. In this section, I’ll explain how Web Services combine the best aspects of component-based technologies and the Web, and introduce the infrastructure needed to communicate with Web Services.

Like components, Web Services represent black-box functionality that can be reused without worrying about how the service is implemented. Web Services provide well-defined interfaces, called contracts, that describe the services provided. Developers can assemble applications using a combination of remote services, local services, and custom code. For example, a
(Con’t, page 4)
Page 3

3