>>How do you handle "cycling reference" issue in this cause? For example, Business.Personal might need to access functionality in Business.Banking and vice versa.



Hi John,

To avoid a "cyclic reference" in situations such as this, you would need to have a third project for the common stuff that need to be referenced by both of the other projects. I'm not sure of your exact needs, so perhaps my answer is a bit vague, but does it help?

~~Bonnie