Gos,
..NET fully supports circular references between objects!
Are you referring to circular references between projects?
What I would suggest is a Separated Interface Pattern.
http://www.martinfowler.com/eaaCatal...Interface.html
When you implement this pattern you can dynamically load one of the classes
if you want giving you the a benefit of late-binding. However! because of
the Separated Interface you will have the benefit of early binding also.
If you search the microsoft.public.dotnet.* newsgroups at groups.google.com
for Separated Interface Pattern you should find a number of references and
other tidbits on the above pattern.
Hope this helps
Jay
"Gos" <er***********@yahoo.com> wrote in message
news:a3**************************@posting.google.c om...
Hi,
It is known that .NET does not allow us to add circular references. Is
there a way to workaround this problem by late-binding the objects at
run time? Will this create any other problems?
One solution to the problem is to re-architect the solution. But, I
dont want to do this as there are many modules in the project which
are already developed and nearing the release.
Any help would be appreciated.
Thanks
Gos