Hi Anthony. I look at two Razor-ified Umbraco packages: ublogsy and ucommerce. At first I was wondering why ucommerce implemented their Razor this way: templates contain aspx code, with simple <Macro:>, which refers to cshtml. I have found that this way is not making my developer work harder. But it allows me to use ?umbDebugShowTrace=true and see statistics. While in your "pure mvc" way it doesn't show any info. Is there no way to get such debug information for your razor ublogsy?
If there is not, maybe it's worth to make it like ucommerce did: put logic to cshtml macros, and leave templates in aspx?
The way of implementing MVC/Razor stuff
Hi Anthony. I look at two Razor-ified Umbraco packages: ublogsy and ucommerce. At first I was wondering why ucommerce implemented their Razor this way: templates contain aspx code, with simple <Macro:>, which refers to cshtml. I have found that this way is not making my developer work harder. But it allows me to use ?umbDebugShowTrace=true and see statistics. While in your "pure mvc" way it doesn't show any info. Is there no way to get such debug information for your razor ublogsy?
If there is not, maybe it's worth to make it like ucommerce did: put logic to cshtml macros, and leave templates in aspx?
A lack of trace is an MVC issue.
uBlogsy 3.0 is built using MVC.
Trace is only available in Webforms mode. If you want to use Webforms, you can use uBlogsy 2.x.
is working on a reply...