>Drop the word "call" completely. It doesn't tell you WHAT calls it. Is it a telephone call? Is it a web services call? You should KNOW what calls it OR what is being called from the name.
>
>>BTW, looks like all other developers here like the 'CurrentCall' as a class name. Should I just go with it then?


Here is what is happening. The C++ application passes a string to .NET application. In our terminology it is an "invoke call". .NET application which is replacing our current VFP class library application does its work for the passed method call and returns result back as a string to C++ application.

The class I want to develop will serve as a holder for several important properties associated with each "invoke call". It may also have some extra functionality built in.

For now we're mostly concerned about status codes, error codes, error messages to be passed.