We have a service that runs methods used for data import/export at specified intervals. To test these methods we have a little application with a single button that, when clicked, instantiates the import/export class and invokes the desired method. Nothing fancy. I would like create a more robust test application that can receive debug information from the method in more of a real-time fashion than the return value from the service method. These methods can take anywhere from a few minutes to 30 to run a full import/export load, and I would like some indication of the amount of data that’s already been processed.
My initial idea was to wrap the classes in some type of message queuing class which the test application could then read from and display the messages. However I’m still kind of a n00b at this, so I don’t know if there’s a better way to do what I want to do.
We develop in VB on .NET 2.0
You could modify your service methods to raise events that report on status during the processing then simply handle the events in your code to update the status, that would be the fastest method.
Your production code could simply not do anything with the events