The following code example demonstrates how you can implement an Web ApiController. You can inject a parameter in the controller's constructor leveraging the Ninject bindings. For more information, see Implement the service layer with Ninject.
RECOMMENDATION: To make sure you can easily differentiate between the Classic MVC controllers and widget controllers, we recommend that you place the ApiController in the <root>/ApiControllers folder.
Once you build the project, the controller gets the service as a parameter to its constructor. When you request the domain/api/<ControllerName>/get route, the controller is executed by the ASP.NET pipeline and returns the corresponding string.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2022 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity