>Returning true or false is generally frowned on in a .Net application. In the case we're talking about in this thread, Naomi is dealing with an external C++ application. Unless she can change that program, she has to return a string.
>
No, the C++ application will stay. It is active and does what it needs to do and being constantly developed.

Right now this application communicates with VFP application and passing and returning XML like string. We're migrating VFP application into .NET, that's why my prior threads, etc.

I think I am getting a bit better, I am trying to write simple methods to do just one thing, one complex method may call many small ones. But right now I keep passing these two variables.

Anyway, turned out my latest re-factoring (the one I talked just recently about) broke other tests. I am guilty of not re-running all unit tests and running only my tests.

So, for now I will concentrate on fixing that problem, so I can still have time before naming that new class.