Results 1 to 9 of 9

Thread: Plugin Architecture

  1. #1

    Thread Starter
    Addicted Member
    Join Date
    Aug 2002
    Location
    Belfast, N. Ireland
    Posts
    167

    Plugin Architecture

    Hello...

    Not sure if this is the best forum to post in but...

    I'm prototyping an system in VB.NET that has a plugin architecture. Has anyone encountered any articles which discuss the advantages and disadvantages of using this type of architeture?

    My google searches aren't being that helpful.

    Thanks

  2. #2
    Sleep mode
    Join Date
    Aug 2002
    Location
    RUH
    Posts
    8,083
    Search this forum for Cander's post on plugins . It's good one on this site .

  3. #3

    Thread Starter
    Addicted Member
    Join Date
    Aug 2002
    Location
    Belfast, N. Ireland
    Posts
    167
    Hmm.. I'm kinda more interested in a discussion about the benefits of plugin architectures rather than HOW-TOs..

    Thanks anyway.

  4. #4
    Fanatic Member VBCrazyCoder's Avatar
    Join Date
    Apr 2003
    Posts
    681
    Check out the .NET Architecture forum.

  5. #5
    Sleep mode
    Join Date
    Aug 2002
    Location
    RUH
    Posts
    8,083
    Sorry , that's all the help I can offer here , since this seems to be advanced concepts and few guys knows about it .

  6. #6
    Banished Cander's Avatar
    Join Date
    Dec 2000
    Location
    Why do you care?
    Posts
    6,913
    Well its really obvious actually. It has nothing to do with advantages or disadvantages. The only issue is, do you need it. If you need/want 3rd party developers to write add-on's to your application, then you create a plugin architecture.
    Stack Overflow
    See the features of Visual Studio 2010 and C# 4.0: The 10-4 show on Channel9

  7. #7

    Thread Starter
    Addicted Member
    Join Date
    Aug 2002
    Location
    Belfast, N. Ireland
    Posts
    167
    Originally posted by Cander
    Well its really obvious actually. It has nothing to do with advantages or disadvantages. The only issue is, do you need it. If you need/want 3rd party developers to write add-on's to your application, then you create a plugin architecture.
    Not quite. There are many other reasons to adopt a modular architecture besides 3rd party developers - flexibility, parallel development, distribution and maintenance issues...

  8. #8
    Banished Cander's Avatar
    Join Date
    Dec 2000
    Location
    Why do you care?
    Posts
    6,913
    Those are more like benefits of modularity, which isnt neccesarily plugins. Just good use of dll's can provide you all the benfits you really need for an internal application
    Stack Overflow
    See the features of Visual Studio 2010 and C# 4.0: The 10-4 show on Channel9

  9. #9

    Thread Starter
    Addicted Member
    Join Date
    Aug 2002
    Location
    Belfast, N. Ireland
    Posts
    167
    Nah.. I'm still talking specificaly about plug-in architecture. Just simply using a modular approach will not gaurentee the flexibility and scalability required by our clients.

    But it's all semantics at the end of the day so lets not get bogged down. Thanks for your replies folks.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width