summaryrefslogtreecommitdiff
path: root/demos/quickstart/protected/pages/Configurations/AppConfig.page
diff options
context:
space:
mode:
Diffstat (limited to 'demos/quickstart/protected/pages/Configurations/AppConfig.page')
-rw-r--r--demos/quickstart/protected/pages/Configurations/AppConfig.page2
1 files changed, 1 insertions, 1 deletions
diff --git a/demos/quickstart/protected/pages/Configurations/AppConfig.page b/demos/quickstart/protected/pages/Configurations/AppConfig.page
index 97db019f..b0a3c7c3 100644
--- a/demos/quickstart/protected/pages/Configurations/AppConfig.page
+++ b/demos/quickstart/protected/pages/Configurations/AppConfig.page
@@ -43,4 +43,4 @@ Complete specification of application configurations can be found in the <a href
By default without explicit configuration, a PRADO application when running will load a few core modules, such as <tt>THttpRequest</tt>, <tt>THttpResponse</tt>, etc. It will also provide the <tt>TPageService</tt> as a default service. Configuration and usage of these modules and services are covered in individual sections of this tutorial. Note, if your application takes default settings for these modules and service, you do not need to provide an application configuration. However, if these modules or services are not sufficient, or you want to change their behavior by configuring their property values, you will need an application configuration.
</p>
-</com:TContent> \ No newline at end of file
+<div class="last-modified">$Id$</div></com:TContent> \ No newline at end of file