Best way to set up a separate API project extending UmbracoApiController
What is the best way to set up a separate Umbraco web api project in my solution? I want to be able to extend UmbracpApiController and publish just the updated API to my Umbraco installation as a .dll. This has probably been asked before, so if there are any good answers, a pointer in the right direction is much appreciated :)
If you add a new Class Library project to your solution, you can then use Nuget to add only the Umbraco core dlls for the version of Umbraco you are using to your new project.
Best way to set up a separate API project extending UmbracoApiController
What is the best way to set up a separate Umbraco web api project in my solution? I want to be able to extend UmbracpApiController and publish just the updated API to my Umbraco installation as a .dll. This has probably been asked before, so if there are any good answers, a pointer in the right direction is much appreciated :)
Hi Morten
If you add a new Class Library project to your solution, you can then use Nuget to add only the Umbraco core dlls for the version of Umbraco you are using to your new project.
https://www.nuget.org/packages/UmbracoCms.Core/
This enables you to extend/inherit UmbracoApiController from within your class library.
Your class library project will build to a separate dll.
You can reference the project from your website project that includes the main Umbraco install.
regards
Marc
Thanks Marc - very clear and to the point! :)
is working on a reply...