>>>What you showed isn't a cyclic reference? Application has database and Database has application?
>>
>>I assume you are worrying about 'cyclic reference' from a VFP POV - it's not issue in .NET
>
>Right, unless the two classes are in different projects, because then each project will have to reference the other and .NET *will* have a problem with "cyclic reference".

In that scenario then, strictly speaking, it's just a VS problem (build order which occurs when both projects are in the same solution) rather than a .NET restriction.

If the references are to the DLL rather than the project then there's no problem.