This isn't a bug but I wasn't sure where to ask my question. Let me start by saying thank you for making uBlogsy, I'm very impressed with it. I'm closely following the development of this and the umbraco v6 core, and have a development website up and running with the latest stable release of both. I look forward to seeing it all come together as they're working on issues with the templates in the umbraco core, etc.
I'm very new to Umbraco and Mvc. I am currently running in Mvc mode in umbracosettings.config, and have the MVC version of uBlogsy. What would be the benefit of the Web Forms version? I'm unclear about what the difference would be. For example, in my current, Mvc setup, I'm still able to create a macro based on a web forms-based user control. Sorry, this is probably a really basic question, but I really have no experience with umbraco so far. Thank you in advance, and thanks for the great blog software.
I'm sure Anthony will comment soon, however from what I can tell if you're running MVC then use the MVC version of uBlogsy. If you're using an older version of Umbraco then the older WebForms version has more features.
MVC is basically the future. Overall for a c# developer it has more benefits. A front end dev (even one that dabbles a little in backend) will not really care.
The big difference is form submission, and the fact that you can do razor in a layout template. You can write razor in a master page template (enclosed in a macro tag) but it can be hella ugly and hard to debug.
I made the webforms version of uBlogsy because people are using webforms as it is familiar. I imagine that most of the people using mvc are c# devs. So probably the advantage of sticking with webforms in the short term is more community support. This may be a missconception :)
Ok, so is it accurate to say webforms version is for people who don't want to change to razor templates, or people running an older version of umbraco that doesn't support mvc? Because I was able to add webforms user controls to my mvc instance of umbraco as macros, so I'm not seeing any reason to use the web forms version. I was trained with webforms, so I'm glad I can make a webform user control and add it as a macro if I need to, but I want to try to use "best practices" and do things the more modern way, so I'm learning razor as I go along with learning umbraco. They're both pretty intuitive so far. Thanks again for the responses.
I was asking myself a same question: "Should I use MVC version of uBlogsy or an webforms-razormacro one?" Initially I was going to use MVC because I was afraid webforms ublogsy was discontinued. And you never want to start using something, that's discontinued. Otherwise, MVC solution is inferior, as far as I can see. For example, you can't see detailed performance of every page part with ?umbDebugShowTrace=true in MVC setup.
I only hope ublogsy webforms would be implemented a little different: instead of inlined .cshtml files includes and inlined Razor code (which is indeed ugly and hard to debug!), it would be great if every .cshtml macro would be registered in Umbraco as a Macro. This way it's more clean, easy to debug, and it's easy to manage caching of parts, for example. It is done this way in uCommerce and I like the way they did it very much.
I used to consider myself an MVC dev. But for Umbraco I see how WebForms is so much better. As far as Razor is used to write logic, Razor is great.
The reason the webforms version has cshtml files and inline razor in master pages is because i backported it all from the new mvc version. I wanted to keep them as similar as possible to allow my own bug fixing/development to be easier.
The lack of trace is a drawback with using umbraco in MVC mode.
As with cachable macros... They were there in the uBlogsy 2, however, since everythign is now driven by lucene, I didnt see the point. I will probably re-add them though since they will actualyl add some benefits.
web forms vs mvc
This isn't a bug but I wasn't sure where to ask my question. Let me start by saying thank you for making uBlogsy, I'm very impressed with it. I'm closely following the development of this and the umbraco v6 core, and have a development website up and running with the latest stable release of both. I look forward to seeing it all come together as they're working on issues with the templates in the umbraco core, etc.
I'm very new to Umbraco and Mvc. I am currently running in Mvc mode in umbracosettings.config, and have the MVC version of uBlogsy. What would be the benefit of the Web Forms version? I'm unclear about what the difference would be. For example, in my current, Mvc setup, I'm still able to create a macro based on a web forms-based user control. Sorry, this is probably a really basic question, but I really have no experience with umbraco so far. Thank you in advance, and thanks for the great blog software.
I'm sure Anthony will comment soon, however from what I can tell if you're running MVC then use the MVC version of uBlogsy. If you're using an older version of Umbraco then the older WebForms version has more features.
That makes sense, thanks. I will stick with the MVC version then, since I don't need to use an older version of umbraco.
Hey Steve.
Regarding Webforms vs mvc...
MVC is basically the future. Overall for a c# developer it has more benefits. A front end dev (even one that dabbles a little in backend) will not really care.
The big difference is form submission, and the fact that you can do razor in a layout template. You can write razor in a master page template (enclosed in a macro tag) but it can be hella ugly and hard to debug.
I made the webforms version of uBlogsy because people are using webforms as it is familiar. I imagine that most of the people using mvc are c# devs. So probably the advantage of sticking with webforms in the short term is more community support. This may be a missconception :)
Ok, so is it accurate to say webforms version is for people who don't want to change to razor templates, or people running an older version of umbraco that doesn't support mvc? Because I was able to add webforms user controls to my mvc instance of umbraco as macros, so I'm not seeing any reason to use the web forms version. I was trained with webforms, so I'm glad I can make a webform user control and add it as a macro if I need to, but I want to try to use "best practices" and do things the more modern way, so I'm learning razor as I go along with learning umbraco. They're both pretty intuitive so far. Thanks again for the responses.
I was asking myself a same question: "Should I use MVC version of uBlogsy or an webforms-razormacro one?" Initially I was going to use MVC because I was afraid webforms ublogsy was discontinued. And you never want to start using something, that's discontinued. Otherwise, MVC solution is inferior, as far as I can see. For example, you can't see detailed performance of every page part with ?umbDebugShowTrace=true in MVC setup.
I only hope ublogsy webforms would be implemented a little different: instead of inlined .cshtml files includes and inlined Razor code (which is indeed ugly and hard to debug!), it would be great if every .cshtml macro would be registered in Umbraco as a Macro. This way it's more clean, easy to debug, and it's easy to manage caching of parts, for example. It is done this way in uCommerce and I like the way they did it very much.
I used to consider myself an MVC dev. But for Umbraco I see how WebForms is so much better. As far as Razor is used to write logic, Razor is great.
Dimps you have some valid points.
The reason the webforms version has cshtml files and inline razor in master pages is because i backported it all from the new mvc version. I wanted to keep them as similar as possible to allow my own bug fixing/development to be easier.
The lack of trace is a drawback with using umbraco in MVC mode.
As with cachable macros... They were there in the uBlogsy 2, however, since everythign is now driven by lucene, I didnt see the point. I will probably re-add them though since they will actualyl add some benefits.
is working on a reply...