Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

  • Mark Bennett 199 posts 375 karma points
    Oct 08, 2014 @ 20:14
    Mark Bennett

    Umbraco.Extensions as a class library


    Is there a reason why the Umbraco.Extensions project is a website and not a class library?

    Also what is the idea behind the naming convention on the BLL directory?


  • Jeroen Breuer 4861 posts 12135 karma points MVP 3x admin c-trib
    Oct 09, 2014 @ 09:22
    Jeroen Breuer


    It's a web application so it's also possbile to add webform pages and user controls. Umbraco 7 uses AngularJS, but that's only for the content and media section currently. Other sections are still webforms. So if you want to extend those parts with custom webforms pages you can also add those in the Umbraco.Extensions project. 

    BLL means Business Logic Layer. More info about it here:

     In this case there is no DAL because that's the Umbraco API or PetaPoco.


  • Mark Bennett 199 posts 375 karma points
    Oct 09, 2014 @ 10:44
    Mark Bennett

    Hi Jeroen,

    Ok so it's a web application to support some of the 'older' parts of Umbraco that may need extending....makes sense :)

    BLL - Doh!! I new it would be something like that and looking at the code now it makes sense...always had my n-tier apps have a project for the business layer but it makes sense to segregate into a folder in this scenario.

    Thanks for the info ;)


Please Sign in or register to post replies

Write your reply to: