Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

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

Posted on 2006-07-10
2
Medium Priority
?
987 Views
Last Modified: 2012-08-14
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???
0
Comment
Question by:pathix
2 Comments
 
LVL 13

Accepted Solution

by:
devsolns earned 2000 total points
ID: 17075788
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
 
LVL 7

Expert Comment

by:RainMan82
ID: 17075999
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

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

One of the pain points with developing AJAX, JavaScript, JQuery, and other client-side behaviors is that JavaScript doesn’t allow for cross domain request for pulling content. For example, JavaScript code on www.johnchapman.name could not pull conte…
I recently went through the process of creating a Calendar Control of events with the basis of using a database to keep track of the dates that are selectable, one requirement was to have the selected date pop-up in a simple lightbox.  At first this…
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Look below the covers at a subform control , and the form that is inside it. Explore properties and see how easy it is to aggregate, get statistics, and synchronize results for your data. A Microsoft Access subform is used to show relevant calcul…

824 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question