Sitefinity template parser: How to use standard ASP.NET parser

Sitefinity template parser: How to use standard ASP.NET parser

April 07, 2009 0 Comments

The content you're reading is getting on in years
This post is on the older side and its content may be out of date.
Be sure to visit our blogs homepage for our latest news, updates and information.

[This post is part of the developer's manual preview published on this blog. You can find temporary TOC here.]

When creating your templates for Sitefinity (control templates that is) you have a choice between standard ASP.NET template parser and Sitefinity template parser. Here are the rules that explain which template parser you will use:
  • Embedded templates always use Sitefinity template parser
  • External templates will use standard ASP.NET parser if they end with .ascx extension
  • External templates will use Sitefinity ASP.NET parser if they end with any extension other than .ascx - in Sitefinity team we have the convention to end these files with .sft extension
We suggest you use Sitefinity template parser for the new templates, because you will have the guarantee that these templates could be embedded effortlessly in the future. For the already existing templates, you can use standard ASP.NET template parser.

The Progress Guys

View all posts from The Progress Guys on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.

Comments are disabled in preview mode.
Latest Stories in
Your Inbox
More From Progress
5 Questions Automakers Should Ask to Improve Asset Uptime
Download Whitepaper
2018 Gartner Magic Quadrant Web Content Management (WCM)
Download Whitepaper
What Serverless Means for Enterprise Apps
Watch Webinar