Re: Is this a viable design idea?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Tosch (tosch_nospam_at_swissonline.ch)
Date: 07/29/04 

Date: Thu, 29 Jul 2004 20:53:00 +0200

Neil,
thanks for your comments.
The base class is indeed just an interface and the 'real' external
DLLs implement that interface.
The way I have designed it now (with circular reference), it does
acutally work, except for a warning when compiling. But it just
doesn't feel right.
I will put the order object and any objects that I pass between the
main application and the external DLLs in a separate DLL, just seams
cleaner to me too.

Tosch
On Thu, 29 Jul 2004 17:29:39 +0000 (UTC), "Neil Woodvine"
<nReEiMl.wooOdviVne@btEinternMet.cEom> wrote:

>It would be a circular reference.
>
>Assuming the following assumptions are correct then the subsequent
>suggestion could be of use to you:
>1) You are using the Base class as a means to expose a limited interface to
>your main application.
>2) Your Order object is used BY your external dll, and your Order object
>does not need a reference to
>your external DLL.
>
>Suggestion:
>1) Take your Order Objects out of the Main App and put them in Order.dll
>2) Add Reference to Order.dll in Main App
>3) Add Reference to Order.dll in your existing 'external' dll
>
>= No Circular References.
>
>Also if the Base Class is just an interface then consider creating an
>Interface and using Implements in your
>external DLL Classes.
>
>Hope this helps some
>Neil
>
>
>"Tosch" <tosch_nospam@swissonline.ch> wrote in message
>news:7s5ig051bt5n4gagcbo0pjeg3phdjim5dv@4ax.com...
>> I have an order processing application with many features.
>> I want to be able to put some features in external and configureable
>> DLLs.
>> The main application has to pass an order object (and possibly some
>> other objects) to the external dll.
>>
>> I have designed a base class with just interfaces on which the real
>> dlls base. The main application has a reference to this base class.
>> The external dlls (and the base class) need a reference to the main
>> application so it can properly use the classes that are passed from
>> the main application to the external dlls.
>>
>> Since the main app has a reference to the external dlls and the
>> external dlls have a reference to the main app this looks to me like
>> circular reference.
>>
>> Can I get into trouble with this design? Is it better to move all the
>> classes to a separate dll and reference this dll from the main
>> application and the external dll?
>>
>> Any comments welcome
>>
>> Tosch
>

Relevant Pages

  • VB FAQs (Interview Questions) lot lot
    ... Consider two objects, A and B. A holds a reference to B, ... Why do so many example programs not use the DLL name ... Private Declare Function SendMessage Lib "user32" ... Private Const BUFFER_LENGTH As Long = 255 ...
    (microsoft.public.dotnet.languages.vb)
  • Re: whats different between asp application and web site
    ... "this means pages can not refer to each other", ... "Without an assembly making a reference to another that it wishes to use the ... all files in the appcode folder go into one dll. ... then the page implements the interface. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Sharing Code
    ... What I found would happen is that when the device dll was built visual ... In the desktop project when you add a reference to the dll, ... > projects, one smart device and one desktop, but they're in the same ... > The 2 form projects have references to this class library projects. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Possible dll boundary problem
    ... >a parameter a reference to a vector of interface pointers (they ... >of the required interface. ... The function returns and the exe then ... >done on the dll side. ...
    (microsoft.public.vc.stl)
  • Re: Namespaces - broad question
    ... Reference the Class Library in your Page, ... > aspx pages that I know I want utilize a specific function within, ... > have the same codebehind page), how can I reference this function. ... >> A .Net assembly is a compiled DLL. ...
    (microsoft.public.dotnet.framework.aspnet)