Reusing Orchard's Core to build another extensibility framework RRS feed

  • Question

  • I am very keen to hear opinions on this.

    We are building an extensible architecture for web applications. We have a core team that builds the default product. Other dev teams take the default product and want to override/replace/extend its functionality at the code level.

    We are considering using Orchard's Core to achieve this.

    If we did it would probably consist of:

    • Removing everything CMS related from Orchard
    • Stripping out Orchard's database
    • Using/building on Orchard's core DLLs to create the extensible capabilities we require

    One alternative to this is vanilla ASP.NET MVC extensibility.


    Monday, January 16, 2012 9:19 PM