Unlike MVC (which has a convention for views based on the name of the controller), ServiceStack's view selection is based on the name of the Response or Request model (DTO) returned. E.g. If your Service returns a - RockstarsResponse then we first look for a view called - RockstarsResponse.cshtml followed by the Request DTO name Rockstars.cshtml + RockstarsResponse then we first look for a view of the same name as the Request DTO called + Rockstars.cshtml followed by the Response DTO name RockstarsResponse.cshtml (in all registered view engine extensions).
@@ -661,26 +659,6 @@ var rockstars = Db.Select<Rockstar>(q => q.Age == Model.Age); -
- ServiceStack also allows having different custom base classes for different Razor extensions which you can register with: -
- -
- Plugins.Add(new RazorFormat {
- RazorExtensionBaseTypes = {
- {"myrzr", typeof(MyCustomViewPage<>) },
- }
- });
- - This will tell ServiceStack's RazorFormat to also scan for files ending with .myrzr and instantiate them - with the base class of MyCustomViewPage<>. By default ServiceStack looks for Razor views with either - .cshtml or .rzr extensions. Only views with .cshtml get VS.NET's Razor intelli-sense. -
-Since all common web tasks should be easy to configure, we've made it easy to register your own custom IHttpHandler's @@ -800,21 +778,11 @@ We continue to develop with this balance in mind and are continually looking to improve start-up times where possible (in DebugMode).
-- To start with we're deferring compilation of all MVC Razor views onto a work queue which gets processed by multiple background threads - (based on the number of cores) in parallel after Application_Start. -
-- If a View is requested before it's been compiled, it jumps the Queue and gets compiled on the fly in the foreground. - For times when the Layout Template is unknown (i.e. hasn't been registered) we wait for compilation of all pages before continuing. -
-- However the best way to avoid the Start-Up penalty is to avoid having to restart the AppDomain in the first place. So in Debug Mode - we'll also do this where the requested View, it's partials and Layout template is checked for modifications and auto-reloaded - on the fly before rendering. The penalty for these checks is not paid in Release (production) mode. + The best way to avoid the Start-Up penalty is to avoid having to restart the AppDomain in the first place. So in Debug Mode + we'll also do this where a background file system watcher monitors all pages, partials and Layout templates for modifications + and recompiles and auto-reloads them on the fly, all-ready to deliever instant response time once the page is requested.
diff --git a/src/RazorRockstars.WebHost/default.cshtml b/src/RazorRockstars.WebHost/default.cshtml index 8c09a34..2f09105 100644 --- a/src/RazorRockstars.WebHost/default.cshtml +++ b/src/RazorRockstars.WebHost/default.cshtml @@ -228,7 +228,6 @@Unlike MVC (which has a convention for views based on the name of the controller), ServiceStack's view selection is based on the name of the Response or Request model (DTO) returned. E.g. If your Service returns a - RockstarsResponse then we first look for a view called - RockstarsResponse.cshtml followed by the Request DTO name Rockstars.cshtml + RockstarsResponse then we first look for a view of the same name as the Request DTO called + Rockstars.cshtml followed by the Response DTO name RockstarsResponse.cshtml (in all registered view engine extensions).
@@ -661,26 +659,6 @@ var rockstars = Db.Select<Rockstar>(q => q.Age == Model.Age); -
- ServiceStack also allows having different custom base classes for different Razor extensions which you can register with: -
- -
- Plugins.Add(new RazorFormat {
- RazorExtensionBaseTypes = {
- {"myrzr", typeof(MyCustomViewPage<>) },
- }
- });
- - This will tell ServiceStack's RazorFormat to also scan for files ending with .myrzr and instantiate them - with the base class of MyCustomViewPage<>. By default ServiceStack looks for Razor views with either - .cshtml or .rzr extensions. Only views with .cshtml get VS.NET's Razor intelli-sense. -
-Since all common web tasks should be easy to configure, we've made it easy to register your own custom IHttpHandler's @@ -800,21 +778,11 @@ We continue to develop with this balance in mind and are continually looking to improve start-up times where possible (in DebugMode).
-- To start with we're deferring compilation of all MVC Razor views onto a work queue which gets processed by multiple background threads - (based on the number of cores) in parallel after Application_Start. -
-- If a View is requested before it's been compiled, it jumps the Queue and gets compiled on the fly in the foreground. - For times when the Layout Template is unknown (i.e. hasn't been registered) we wait for compilation of all pages before continuing. -
-- However the best way to avoid the Start-Up penalty is to avoid having to restart the AppDomain in the first place. So in Debug Mode - we'll also do this where the requested View, it's partials and Layout template is checked for modifications and auto-reloaded - on the fly before rendering. The penalty for these checks is not paid in Release (production) mode. + The best way to avoid the Start-Up penalty is to avoid having to restart the AppDomain in the first place. So in Debug Mode + we'll also do this where a background file system watcher monitors all pages, partials and Layout templates for modifications + and recompiles and auto-reloads them on the fly, all-ready to deliever instant response time once the page is requested.
diff --git a/src/RazorRockstars.WinService/default.cshtml b/src/RazorRockstars.WinService/default.cshtml index 8c09a34..2f09105 100644 --- a/src/RazorRockstars.WinService/default.cshtml +++ b/src/RazorRockstars.WinService/default.cshtml @@ -228,7 +228,6 @@Unlike MVC (which has a convention for views based on the name of the controller), ServiceStack's view selection is based on the name of the Response or Request model (DTO) returned. E.g. If your Service returns a - RockstarsResponse then we first look for a view called - RockstarsResponse.cshtml followed by the Request DTO name Rockstars.cshtml + RockstarsResponse then we first look for a view of the same name as the Request DTO called + Rockstars.cshtml followed by the Response DTO name RockstarsResponse.cshtml (in all registered view engine extensions).
@@ -661,26 +659,6 @@ var rockstars = Db.Select<Rockstar>(q => q.Age == Model.Age); -
- ServiceStack also allows having different custom base classes for different Razor extensions which you can register with: -
- -
- Plugins.Add(new RazorFormat {
- RazorExtensionBaseTypes = {
- {"myrzr", typeof(MyCustomViewPage<>) },
- }
- });
- - This will tell ServiceStack's RazorFormat to also scan for files ending with .myrzr and instantiate them - with the base class of MyCustomViewPage<>. By default ServiceStack looks for Razor views with either - .cshtml or .rzr extensions. Only views with .cshtml get VS.NET's Razor intelli-sense. -
-Since all common web tasks should be easy to configure, we've made it easy to register your own custom IHttpHandler's @@ -800,21 +778,11 @@ We continue to develop with this balance in mind and are continually looking to improve start-up times where possible (in DebugMode).
-- To start with we're deferring compilation of all MVC Razor views onto a work queue which gets processed by multiple background threads - (based on the number of cores) in parallel after Application_Start. -
-- If a View is requested before it's been compiled, it jumps the Queue and gets compiled on the fly in the foreground. - For times when the Layout Template is unknown (i.e. hasn't been registered) we wait for compilation of all pages before continuing. -
-- However the best way to avoid the Start-Up penalty is to avoid having to restart the AppDomain in the first place. So in Debug Mode - we'll also do this where the requested View, it's partials and Layout template is checked for modifications and auto-reloaded - on the fly before rendering. The penalty for these checks is not paid in Release (production) mode. + The best way to avoid the Start-Up penalty is to avoid having to restart the AppDomain in the first place. So in Debug Mode + we'll also do this where a background file system watcher monitors all pages, partials and Layout templates for modifications + and recompiles and auto-reloads them on the fly, all-ready to deliever instant response time once the page is requested.