../code/ADAM-Wrapper-Prototype All message handlers, e.g., virtually all parts, inherit from AWrapper, except for UIs that already inherit implementation from Form. UIs need to create a message handler that does inherit from AWrapper.

../code/DynamicLinkLibraries How the Executives attach to the parts they manage.

../../CoreTechnologies/SocketsAndRemoting/code/MessageFraming Communication component receivers need to do this.

../code/Base64Encoding Any component that wants to send, possibly binary, files needs to do this.

../../CoreTechnologies/ThreadsAndSynchronization/code/ProcessDemoDotNet Shows how to wrap a legacy EXE.

msdn.microsoft.com/msdnmag/issues/03/01/NET/ ../presentations/QueueAnalysis.doc ../presentations/OrganizingPrinciplesForProject5.doc - a "chalk talk". ../presentations/SizeTimeEstimatesPr5F05.doc - some more "chalk talk". Some timed executions: ../code/fileXferWebService ../code/TestHarnessPrototype ../code/RunCompiler ../presentations/LoadAnalysisForQueuedSubsystems.doc ../code/RandomEvents ../presentations/ArchitectureTaxonomy.ppt ../presentations/messagepassingsystems.ppt ../code/PeerToPeerPrototype Illustrates use of bilateral remoting with SingleCall activation to establish Peer-To-Peer communication. ../code/MessageServiceClientServer ../presentations/ConfigureWebService.doc ../presentations/Interception.ppt ../Lecture11 contains a page of links to presentations and code discussed in this class. The Lecture folders will occasionally hold physical files of interest as well. Usually, however, all the materials of interest to the class are in the ../presentations and ../code folders. The contents of these folders will grow as you progress through the course.