Here was the problem as printed in the Communications of the ACM, August 2004:

To Send a Fax

Dial the four-digit access code Y where 60097 equals f(f(f(Y))).
This machine has extension number Z where f(f(Z)) = 1.

(If you forgot your orientation packet, E(x) = number of letters when x is written out in American English f(x) = 3[E(x)]^3 - x.

 read more ...

The UAB leaves log files and old application directories on the client.  This post processor will delete these old files when a new version is deployed.  The most recent log file will be not be deleted.  Also, the most two recent version directories will not be deleted.  This is mainly for 2 reasons:  1)  You cannot delete the executable you are currently running in the "old" version directory while the new directory is being created and 2)  Just in case you need to rollback to the previous version it's still on the client: read more ...

I created a base form class that allows me to easily incorporate the UAB into my Windows Forms applications.  This class is based on the QuickStart examples provided by Microsoft.  Simply inherit your main application window from this class and your application is ready to use the UAB.  The window simply has a status textbox at the bottom that displays information to the user. read more ...

For some reason the InstallServices.bat assumes that you have Visual Studio .NET installed on the machine you are running. It only needs access to the InstallUtil.exe that comes with the .NET framework. I have modified the batch file to run without Visual Studio installed and it seems to work.  Run the batch file from the same directory that the Enterprise Library assemblies are located on the server. read more ...

I created an example that uses two approaches: 1) A Singleton SAO factory that returns an MBR object and 2) A Singleton SAO factory that returns a ObjRef to another Singleton SAO.

In order to implement a true Singleton object you must return a Singleton SAO to the client, method #2. The only way to do so is to create an SAO on the server using the Activator class and to return an ObjRef to the client by Marshaling the SAO reference yourself. (See 2nd entry below for an update)

There are fundamental differences between these two types of remote objects and the context of how you use an object alone does not determine whether it is an SAO or CAO. How you activate an object seem to determine this classification and most importantly any MBR object returned to a client that is created by another remote object (factory pattern) that is created with the New statement will be classified as a CAO. The key fundamental difference between an SAO and CAO is their lifetime management with leases.

 read more ...