Reference / Binding design question
-
Hello, I have a dll that i'm calling 'library' (contains core classes necessary for my app to run). I have a series of dlls that are responsible for various tranactions (security, detailed data, etc) that am doing a loadassembly to when a certain type of transaction is requested. So my website has a reference to the library. The library does loadassembly to transaction dll(s). But there are classes inside the library that the transaction dll(s) could/should use to cut down on duplicate code. So the question...is this type of circular reference acceptable (1 reference is done early and 1 is done late) or how should this be designed? Thank you for your time. Nathan
'Never argue with an idiot; they'll drag you down to their level and beat you with experience.' ~ anonymous