I cannot say what is the common practice in this situation, because we often use only one assembly. When we use more assemblies, we did not run into "cycle reference" problem. So I suggest separate assembly only to solve problem for this concrete project.
Plamen Ivanov
MCSD .NET Early Achiever and MCAD .NET Charter Member (VB .NET/SQL Server 2000)
MCSD (VB 6.0/SQL Server 2000) br>
VB (.NET) - what other language do you need in the whole Universe?...