From 3b91e1039d8bd9dcc3db14734eca4e88fdbcb2f0 Mon Sep 17 00:00:00 2001
From: xue <>
Date: Tue, 28 Feb 2006 03:06:45 +0000
Subject: another fix about asset tutorial.

---
 demos/quickstart/protected/pages/Advanced/Assets.page | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'demos/quickstart/protected')

diff --git a/demos/quickstart/protected/pages/Advanced/Assets.page b/demos/quickstart/protected/pages/Advanced/Assets.page
index 18b2a2be..d69a1bcd 100644
--- a/demos/quickstart/protected/pages/Advanced/Assets.page
+++ b/demos/quickstart/protected/pages/Advanced/Assets.page
@@ -28,8 +28,8 @@ Asset publishing is managed by the <tt>System.Web.TAssetManager</tt> module. By
 <com:TTextHighlighter Language="xml" CssClass="source">
 &lt;modules&gt;
     &lt;module id="asset"
-            class="System.Web.UI.TAssetManager"
-            BasePath="images"
+            class="System.Web.TAssetManager"
+            BasePath="Web.images"
             BaseUrl="images" /&gt;
 &lt;/modules&gt;
 </com:TTextHighlighter>
@@ -39,7 +39,7 @@ Asset publishing is managed by the <tt>System.Web.TAssetManager</tt> module. By
 PRADO uses caching techniques to ensure the efficiency of asset publishing. Publishing an asset essentially requires file copy operation, which is expensive. To save unnecessary file copy operations, <tt>System.Web.TAssetManager</tt> only publishes an asset when it has a newer file modification time than the published file. When an application runs under the <tt>Performance</tt> mode, such timestamp checkings are also omitted.
 </p>
 <p>
-ADVISORY: Do not overuse asset publishing. The asset concept is mainly used to help better reuse and redistribute component classes. Normally, you should not use asset publishing for resources that are not bound to any components in an application. For example, you should not use asset publishing for images that are mainly used as design elements (e.g. logos, background images, etc.) Let Web server to directly serve these images will help improve the performance of your application.
+ADVISORY: Do not overuse asset publishing. The asset concept is mainly used to help better reuse and redistribute component classes. Normally, you should not use asset publishing for resources that are not bound to any component in an application. For example, you should not use asset publishing for images that are mainly used as design elements (e.g. logos, background images, etc.) Let Web server to directly serve these images will help improve the performance of your application.
 </p>
 
 <h2>A Toggle Button Example</h2>
-- 
cgit v1.2.3