Solved

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

Posted on 2006-07-10
2
976 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 500 total points
Comment Utility
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
Comment Utility
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

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Today is the age of broadband.  More and more people are going this route determined to experience the web and it’s multitude of services as quickly and painlessly as possible. Coupled with the move to broadband, people are experiencing the web via …
Problem Hi all,    While many today have fast Internet connection, there are many still who do not, or are connecting through devices with a slower connect, so light web pages and fast load times are still popular.    If your ASP.NET page …
Internet Business Fax to Email Made Easy - With eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, fr…
You have products, that come in variants and want to set different prices for them? Watch this micro tutorial that describes how to configure prices for Magento super attributes. Assigning simple products to configurable: We assigned simple products…

772 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

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now