what is the definition of a "circular reference"???

Hi,

We are in the process of transferring our legacy system to asp.net. We have multiple solutions all containing one project each. We have a lot of situations whereby a class in "Solution A" will call a class in "Solution B" and vice versa. Does this constitute a circular reference or does this term only refer to projects which call other projects within the same solution??? We know that visual studio will now build projects which call other projects inside the same solution due to circular references, however we have not run into this error with the multiple solution/one project setup...We are wondering if this setup will cause us any problems down the road? or Should we combine solutions to eliminate these types of calls and be forced to have longer build times???
pathixAsked:
Who is Participating?
 
devsolnsConnect With a Mentor Commented:
Yeah that is pretty much on as far as a circular reference.  Think about this, should a circular reference really exist for code that is in two difference assemblies?  Probably not.  There are things that you can do to avoid circular references such as using interfaces.


-As you can see from the following a circular reference is set between class A1 & B1.  

    class A1
    {
        public void Foo(){}

    }

    class B1
    {
        public void Foo(A1 a)
        {
            a.Foo();
        }
    }

-The following code removes the circular reference while maintaining/improving functionality.

    interface IFoo
    {
        void Foo();
    }

    class A2 : IFoo
    {
        public void Foo() { }
    }

    class B2
    {
        public void Foo(IFoo a)
        {
            a.Foo();
        }
    }



-gp
0
 
RainMan82Commented:
A circular reference is caused when the calculation that you are doing uses itself to calculate.
This results in an endless calculation, and gives you an error.

It can happen if you have a query which is dependant on the result of another and then use both of these queries as sources for another query.

Alternatively, it can be caused by naming objects the same - which is why it is important to generate unique names for all objects that follow a specific naming convention.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.