Issue: 2001 - Issue 2

  • Issue 2 2001 David Stevenson Editorial Article
  • Inheritance is the single most important new object-oriented feature in Visual Studio.NET. Surprisingly, not much has been written about the subject, and most of the information available is either very basic and an "overview" at best, or just plain misleading. In this article, I give you a real-world overview of what inheritance - especially visual inheritance, can do for you.
  • Systems built with XML and XSLT can often provide much more flexibility and cross-platform functionality than other approaches.Michiel shows us how to build a shopping cart application that's simple, yet highly extensible, and in the process teaches us a few practical uses for these exciting technologies.
  • Today's world is about information. People want it wherever they are, in front of a television, at a PC, in a board meeting, or waiting for a bus.The Internet is great on your PC, but when you want your data on the go, lugging a Pentium PC around in your coat pocket just isn't going to cut it. Enter the Wireless Application Protocol (WAP), a way to get data to mobile wireless devices.
  • XSL patterns are the SQL Select of the XML world.To retrieve the data you want from an XML file, you need to understand how to construct the necessary pattern.
  • Studies indicate that between 40% and 60% of all defects found in software projects can be traced back to errors made while gathering requirements.This is huge! Finding problems while they are just in the planning stages is MUCH easier to deal with than finding them after the code has been written. So, how can developers avoid these errors and create a solid design for their software? This article will describe various methods for gathering software requirements and w...See More
  • In previous issues of Component Developer Magazine, we have introduced technologies such as Queued Components, COM+ Security, Loosely Coupled Events, SQL Server 2000 and BizTalk Server.Each of these represents a fascinating myriad of possibilities. But, how do you put all of them together to build a real-life, highly reliable, 100% available distributed application?
  • Web applications are essentially made up of functions that map inputs (requests) to outputs (responses).This article looks at a way to store the relationship between request and response and pre-generate responses, thus reducing the resources needed fulfill requests.
  • Web Applications tend to be stateless, and running long requests can be problematic for Web backends. Long-running requests can tie up valuable Web server connections and resources. In this article, Rick describes one approach that can be used to handle lengthy requests. A polling mechanism and an Event manager class can be used to pass messages between a Web application and a processing server running the actual long task.
  • Everything you wanted to know about customers but were too busy coding to ask.
  • This page is dedicated to strictly non-technical aspects of our lives as a developers.After all, most developers are real people, too (except for automated code-generating programs, of course). Look here in each issue for commentary and insight into the struggles (and joys) of balancing life and logic, people and programming, fun and flowcharts, and (you fill in the blanks).You will be invited each time to think on a topic, then express yourself via email for possible in...See More