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.
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.
Umbraco.Extensions as a class library
Hi,
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?
Cheers,
Mark.
Hello,
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: http://objcsharp.wordpress.com/2013/07/22/what-is-a-business-logic-layer-anyway/
In this case there is no DAL because that's the Umbraco API or PetaPoco.
Jeroen
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 ;)
Mark..
is working on a reply...