What is considered 'too much' logic in a class constructor?

What you are saying is:

You want to set some properties of YOUR class based on what consumer passes as arguments. But, why do you need to get that done in Constructor itself?

Is "SomeService" Windows Service / Web Service? In which case, it is an "interaction" component as depicted in my original post.

Viral.

---

MCTS - WPF, WinForms, Sql Server 2008