at Umbraco.Web.WebApi.UmbracoApiController..ctor(UmbracoContext umbracoContext) at Umbraco.Web.WebApi.UmbracoApiController..ctor() at JPMC.HR.Umbraco.POC.Controllers.DocumentApiController..ctor() at lambda_method(Closure ) at System.Web.Http.Dispatcher.DefaultHttpControllerActivator.Create(HttpRequestMessage request, HttpControllerDescriptor controllerDescriptor, Type controllerType)
</StackTrace>
</Error>
Is there an initialization step I am missing for Umbraco in this scenario? Do I need to remove the routings provided by the initial MVC 4 application? Is what I am attempting to do even possible?
The Umbraco WebAPI only works if it's used on an Umbraco website. If you want a standonline MVC web app that uses the Umbraco API you could have the WebAPI on your Umbraco project do the work with the Umbraco API and connect to that WebAPI in your own project.
Trying to understand UmbracoApiController in standalone MVC 4 Web API project
I am a newbie so please pardon me if this question has been asked and answered elsewhere (I cannot find it at any rate).
I am trying to create a standalone MVC 4 Web API application that I can use to create services that query an Umbraco DB.
I have:
Hello,
The Umbraco WebAPI only works if it's used on an Umbraco website. If you want a standonline MVC web app that uses the Umbraco API you could have the WebAPI on your Umbraco project do the work with the Umbraco API and connect to that WebAPI in your own project.
Jeroen
is working on a reply...