circular-dependency

Say I have this table structure: Client ----------- ClientId int not null (identity) CurrentDemographicId int null (FK to ClientDemographic) OtherClientFields varchar(100) null ClientDemographic ------------------ ClientDemographicId int not null (identity) ClientId int not null (FK to Client) OtherClientDemographicFields varchar(100) null The idea is that Client (in EF) will have a ClientDemographics list and a CurrentDemographic property. The problem is when I setup the object structure and try to save it, I get this error: Unable to determine a valid ordering for dependent operations.

I'm in the process of moving a fairly large typescript project from internal modules to external modules. I do this because I want to create one core bundle, which, if and when required, can load other bundles. A seccond requirement which I'm keeping in mind is that I'd like to be able to run the bundles (with some modifications if required) on the server with nodeJS aswell. I first tried using AMD & require.js to build the core bundle, but I came across an issue with circular dependencies. After having reading that this is common with require.js and commonJS is more often adviced for large

I'm setting up a nested categories structure in Backbone with RequireJS. In this structure, a categories collection contains category models, and a single category model can contain a categories collection. Unfortunately this seems to cause the dreaded circular dependencies problem in RequireJS. I have read the docs on RequireJS ( http://requirejs.org/docs/api.html#circular ) however I am finding the explanation with 'a' and 'b' confusing. Here is my code, which is causing the problem: define([ "jquery", "underscore", "backbone", "collections/categories" ], function( $, _, Backbone,

I created 2 dummy projects in my application and named them BAL and DAL . When I build them, they build successfully. If I add a reference to BAL to the DAL project, it added nicely. But while adding the DAL reference to the BAL project, I get the following error: A reference to DAL could not be added. Adding this project as a reference would cause a circular dependency. Can anyone help me to solve this error? Prime By Design Here's what you need to do: Right click on the DAL Project in the solution explorer and select Project dependencies in the context menu. You will now see a window that

I have a circular dependency between two functions. I would like each of these functions to reside in its own dll. Is it possible to build this with visual studio? foo(int i) { if (i > 0) bar(i -i); } -> should compile into foo.dll bar(int i) { if (i > 0) foo(i - i); } -> should compile into bar.dll I have created two projects in visual studio, one for foo and one for bar. By playing with the 'References' and compiling a few times, I managed to get the dll's that I want. I would like to know however whether visual studio offers a way to do this in a clean way. If foo changes, bar does not need

What is a good way of dealing with objects and having them talk to each other? Up until now all my games hobby/student have been small so this problem was generally solved in a rather ugly way, which lead to tight integration and circular dependencies. Which was fine for the size of projects I was doing. However my projects have been getting bigger in size and complexity and now I want to start re-using code, and making my head a simpler place. The main problem I have is generally along the lines of Player needs to know about the Map and so does the Enemy , this has usually descended into

I am designing a system where two modules, one which gestions files and another users. For certain logic operations, they need the services offered by each other. Each module is represented by a singleton which implements a interface offering some services to each other, with abstract factories to provide them, like so: public class UserMain implements UserInternalService { /* * Internal interfaces */ /** * Allows interaction with the projects database. */ FilesInternaService fileSystem; /** * Constructor is private, as this is a singleton. */ protected UserMain() { } private static UserMain

In C++, I have a problem with circular dependencies / incomplete types. The situation is as follows: Stuffcollection.h #include "Spritesheet.h"; class Stuffcollection { public: void myfunc (Spritesheet *spritesheet); void myfuncTwo (); }; Stuffcollection.cpp void Stuffcollection::myfunc(Spritesheet *spritesheet) { unsigned int myvar = 5 * spritesheet->spritevar; } void myfunc2() { // } Spritesheet.h #include "Stuffcollection.h" class Spritesheet { public: void init(); }; Spritesheet.cpp void Spritesheet::init() { Stuffcollection stuffme; myvar = stuffme.myfuncTwo(); } If I keep the includes as