needed to view most of the images on this Web site - just a couple of clicks and you're "good to go."
Welcome
Photos of Larryblakeley
http://www.royblakeley.name/larry_blakeley/larryblakeley_photos_jpeg.htm
(Contact Info: larry at larryblakeley dot com)
Important Note: You will need to click this icon to download the free needed to view most of the images on this Web site - just a couple of clicks and you're "good to go."
I manage this Web site and the following Web sites: Leslie (Blakeley) Adkins - my oldest daughter
Lori Ann Blakeley (June 20, 1985 - May 4, 2005) - my middle daughter
Evan Blakeley- my youngest child
Microsoft has pulled back its aggressive marketing of the term ".NET" over the past several years, removing the term from the names of its new versions of Windows and various applications.
In 2003, .NET primarily refers to the development framework upon which Microsoft has based the company's approach to building Web services and other applications. .NET is the object-oriented development platform at the heart of Windows Server 2003, though other Windows environments can be made ".NET-enabled" through downloadable components.
NET competes directly with the Java application platform, which most of Microsoft's rivals implement in their products. In spite of many differences, the .NET and Java platforms share a common architectural approach, involving object-oriented development, distributed execution, and loosely coupled interoperability environments.
Microsoft provides many developer-productivity and code-security benefits in its .NET application platform. However, to fully realize these benefits, organizations will need to migrate toward a new server operating system (Windows Server 2003) and a new integrated development environment (Visual Studio .NET 2003). Enterprise-wide migrations of this sort are seldom inexpensive and straightforward, inasmuch as organizations must continue to maintain, leverage, and extend existing code that was developed in Microsoft's legacy Component Object Model (COM) and other application platforms.
Fortunately, customers who switch or migrate to .NET from COM and other development platforms have various mechanisms for interoperating with legacy COM applications. Bear in mind, though, that Microsoft has implemented some proprietary features in .NET, such as .NET Framework Classes and .NET Remoting. To the extent that developers leverage these features in their application code, they risk locking themselves into the Windows environment.
Many IT professionals don't have the luxury of an "either/or" choice between the platforms. Many companies have deployed Windows and non-Windows operating environments at various tiers in their networking and application environments. It's even possible to run the .NET, COM, and Java runtime environments and applications side by side on the same operating platforms.
Organizations are running mission-critical applications on these diverse platforms, and are looking for approaches, such as Web services, to enable greater interoperability among them. SOAP-based middleware is a loose tether—not yet a robust integration approach—that will enable some degree of interoperability between these heretofore incompatible application platforms.
- "Microsoft’s .NET Platform: Bringing Web Services into the Core of Windows," Platforms and Integration, James Kobielus, Burton Group http://www.burtongroup.com, May 15, 2003
Directory: http://www.larryblakeley.com/Articles/application_services/
File Name: apsresearch.pdf
Post Date: March 9, 2005 at 7:15 AM CST; 1315 GMT