Project.Web.UI - umbraco install with just my views and nothing else (well, ninject for DI and my bundleConfig but that will prob get moved to Web when I get round to it)
If I was to introduce a Project.WebApi class library it would mean referencing Umbraco.Core and Merchello.Core in that project so I can certainly see the benefit of a more simpler 'Api' folder in my controllers folder.
So, when you create the new solution, you create an empty web project Project.Web.UI and the nuget Umbraco. This is the main project when you start the app.
And Merchello Solution or project where is?
How to create an external WebApi project? If I remember is possible to add another MVC or MVC/WEBAPI project in the same solution, but maybe some error on execution on start. Is't right?
I always create a blank solution in VS first then add to it what I need. First of all you need an empty web project titled something like <ProjectName>.Web.UI then from package manager console i install umbraco via nuget. Once you're done with that you'll need to install the merchello package. Seeing as that's an umbraco package it will live in the App_Data folder of your web.ui project. You can do all your merchello / umbraco controllers in that project but I choose to keep them in a seperate class library <ProjectName>.Web
If you're set on a sepeate WebApi project just create one of those in your solution titled <ProjectName>.WebApi
How to configure a solution under VS with Umbraco + Merchello Sources + my custom project?
Hi,
someone can give an example how to configure a solution under vs2013 to develop with Umbraco + Merchello Sources + custom Web/API solution.
Thank you.
Any help, please?
You can create 5 projects:
1 for umbraco (you can use nuget to install it): reference to your library and merchello projects;
1 for your library: reference to umbraco and merchello dll (you can use nuget to add core libraries);
3 for merchello (Core, Examine and Web): you can download it directly from github.
Be sure that the umbraco and Merchello references versions are the same for evey project.
Hi,
that is...I create a new solution with 3 projects:
- 1 - main Web/Api with Umbraco
- 2 - Merchello
- 3 - My Web/API project.
Reference:
3 -> 2 and 1
2 -> 3 and 1
Is't right? have you some example of this?
Hi Biagio, I suggest you look at the Merchello Bazaar codebase for reference.
https://github.com/Merchello/Merchello/tree/1.9.0/src/Merchello.Bazaar/Controllers/Api
They have opted for placing their web api controllers in the controllers folder.
I have a structure similar to this:
Project.Core - core business logic class library
Project.Tests - tests project
Project.Web - controllers / models / factories / extensions
Project.Web.UI - umbraco install with just my views and nothing else (well, ninject for DI and my bundleConfig but that will prob get moved to Web when I get round to it)
If I was to introduce a Project.WebApi class library it would mean referencing Umbraco.Core and Merchello.Core in that project so I can certainly see the benefit of a more simpler 'Api' folder in my controllers folder.
So, when you create the new solution, you create an empty web project Project.Web.UI and the nuget Umbraco. This is the main project when you start the app.
And Merchello Solution or project where is?
How to create an external WebApi project? If I remember is possible to add another MVC or MVC/WEBAPI project in the same solution, but maybe some error on execution on start. Is't right?
I always create a blank solution in VS first then add to it what I need. First of all you need an empty web project titled something like <ProjectName>.Web.UI then from package manager console i install umbraco via nuget. Once you're done with that you'll need to install the merchello package. Seeing as that's an umbraco package it will live in the App_Data folder of your web.ui project. You can do all your merchello / umbraco controllers in that project but I choose to keep them in a seperate class library <ProjectName>.Web
If you're set on a sepeate WebApi project just create one of those in your solution titled <ProjectName>.WebApi
This article is outdated but the same logic applies http://www.theoutfield.net/blog/2012/12/visual-studio-project-structure-for-umbraco-%28updated%29
is working on a reply...