![]() call CMSApplication.Init), for example in the Application_Start method of Global.asax, or in your application's Main method. Map the path before you initialize the Xperience API (i.e. Set the SystemContext.WebApplicationPhysicalPath property to the path of your Xperience project's CMS folder. For example, you can use this approach if you wish to externally update or rebuild the files of locally stored search indexes. If you need to call API that works with a specific folder in the Xperience project, you can map the physical path used by the Xperience API in your external application to a specific Xperience project. Additional configuration and tips Sharing project files with the Xperience application For more information, see the WCF Services and ASP.NET article.įor example, you can execute the CMSApplication.Init method within the constructor of your WCF service class. Kentico 12 Tutorial :- Use Webapi with Kentico - YouTube In this video you will get to your how to integrate Custom web api with Kentico portal engine and how to call it.For more info on. It does provide security through a Basic Authentication HTTP header and but authenticates against the normal User accounts created within Kentico. The standard initialization does not occur, because WCF requests are not processed by the ASP.NET HTTP runtime. Kentico has a REST API built-in, which can be used to query, and modify all kinds of data within the application. Otherwise you may encounter errors if the first request that starts the application is destined for the WCF service. If implementing custom WCF services within the Xperience web project, you need to initialize the application before calling the Xperience API within the service code. Instead, add the code into a Class Library project with the AssemblyDiscoverable attribute and reference the assembly from your project. The system is only able to discover such code within assemblies. This includes classes registered using attributes, such as generated wrapper classes for objects, custom module classes, custom implementations of interfaces or providers, etc. Using custom code that requires discoveryįor external projects that compile into a different output type than a DLL assembly (for example Console applications), do NOT directly add any custom classes that need to be detected during the API initialization.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |