I have Umbraco 9 running with it split over 3 projects, a bit like what JonDJones and Dennis Adolfi have done;
UmbracoSite.Core: This contains my controllers, composers, view components, migrations, interfaces etc etc.
UmbracoSite.Models: This contains my models.
UmbracoSite.Web: This contains my views, my www root etc.
With Umb 9 Forms I can see on Nuget there are:
Umb Forms Core (I guess I put this in my core proj)
Umb Forms Web (I guess I put this in my web proj)
Umb Forms Core Providers (Do I need this in core and web or just core?)
Umb Forms Examine (where's this go)
Any ideas on where I should put these in my architecture? Ideally I'd like to be able to upgrade forms without it touching my views as I normally do lots of view customisation.
Hey Paul,
I'm a fan of keeping the separation - and for all the reasons you note.
That being said, I've been fine with simply adding Umbraco.Forms to the *.Web project and that's it.
The Umbraco.Forms is the only package we use and the views are copied into the *.web\views\partials\forms dir on each build.
The way that Umbraco allows for Themes is really fantastic as you can modify your views/fieldtype renderings as needed and, if you haven't created custom renderings for an particular fieldtype, for example, Umbraco will simply fallback to the stock defaults - love it!
This whole approach allows for the worry free upgrades, it's wonderful.
Installing Umbraco 9 Forms to split architecture/project seperation
Hi,
I have Umbraco 9 running with it split over 3 projects, a bit like what JonDJones and Dennis Adolfi have done;
UmbracoSite.Core: This contains my controllers, composers, view components, migrations, interfaces etc etc.
UmbracoSite.Models: This contains my models.
UmbracoSite.Web: This contains my views, my www root etc.
With Umb 9 Forms I can see on Nuget there are:
Any ideas on where I should put these in my architecture? Ideally I'd like to be able to upgrade forms without it touching my views as I normally do lots of view customisation.
Is this the right place to post about Umb Forms? I got my license.
Hey Paul, I'm a fan of keeping the separation - and for all the reasons you note. That being said, I've been fine with simply adding Umbraco.Forms to the *.Web project and that's it.
The Umbraco.Forms is the only package we use and the views are copied into the
*.web\views\partials\formsdir on each build. The way that Umbraco allows for Themes is really fantastic as you can modify your views/fieldtype renderings as needed and, if you haven't created custom renderings for an particular fieldtype, for example, Umbraco will simply fallback to the stock defaults - love it!This whole approach allows for the worry free upgrades, it's wonderful.
Thanks Damian, this is what I ended up doing, including creating my own theme etc. Seems to be working ok thus far.
is working on a reply...