![]() ![]() ![]() Those requests that match the anycodings_kentico-11 ~/filename.html could then be anycodings_kentico-11 intercepted by Kentico and your custom anycodings_kentico-11 code, read the contents of that anycodings_kentico-11 filename.html from disk, and use it as a anycodings_kentico-11 datasource type of webpart (if portal anycodings_kentico-11 engine) or a repository / model (if anycodings_kentico-11 MVC), then use that info to populate the anycodings_kentico-11 presentation layer of the response of anycodings_kentico-11 the final html to the browser. ![]() The custom code anycodings_kentico-11 could possibly build out a content tree anycodings_kentico-11 that is based on the folder structure of anycodings_kentico-11 the files (if portal), or build out some anycodings_kentico-11 routing logic (if mvc) to route anycodings_kentico-11 requests. You could create some custom logic and anycodings_kentico-11 use the Kentico API (maybe in a anycodings_kentico-11 scheduled task if the content is anycodings_kentico-11 periodically refreshed). However, if anycodings_kentico-11 someone was very determined to make it anycodings_kentico-11 work and if you really had to, custom anycodings_kentico-11 programming could make that happen. I also agree it is not a anycodings_kentico-11 great approach overall. There is definitely no out of the box anycodings_kentico-11 way to that. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |