IMPORTANT: This version of Sitefinity CMS is out of support and the respective product documentation is no longer maintained and can be outdated. Use the version selector to view a supported product version.
Telerik.Sitefinity.Frontend.FrontendService service registers a virtual path for each widget assembly and for Telerik.Sitefinity.Frontend itself. It also registers a route handler. This way, an HTTP GET request to the same file, return it as a response: ~/Frontend-Assembly/[Assembly-Name]/[Path]
Telerik.Sitefinity.Frontend.FrontendService
Telerik.Sitefinity.Frontend
HTTP GET
~/Frontend-Assembly/[Assembly-Name]/[Path]
The contents of a virtual file inside the Frontend-Assembly path can come from the file system at location ~/[Path] When not found there, it falls back to retrieving the contents of an embedded resource placed on the same path, inside the specified assembly. For example, ~/Frontend-Assembly/Telerik.Sitefinity.Frontend/Mvc/Scripts/Angular/angular.min.js
Frontend-Assembly
~/[Path]
~/Frontend-Assembly/Telerik.Sitefinity.Frontend/Mvc/Scripts/Angular/angular.min.js
If a file ~/Mvc/Scripts/Angular/angular.min.js exists, then it will be retrieved. Otherwise, the embedded resource Telerik.Sitefinity.Frontend.Mvc.Scripts.Angular.angular.min.js is returned.
~/Mvc/Scripts/Angular/angular.min.js
Telerik.Sitefinity.Frontend.Mvc.Scripts.Angular.angular.min.js
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