2sxc is all about solving common content and web tasks quickly and efficiencly. Because of this we're enhancing the in-page toolbar with advanced features (only visible for users with elevated permissions). Let's discover...

This is a part of my series The New Features of 2sxc 7 and introduces you to using SQL-Data from DNN in the Visual Query to Re-Template / Re-Design any DNN-Module. In this case I prepared a demo using DNN Events. 

This is a part of my series The New Features of 2sxc 7 and introduces you to using the Visual Query together with Razor Views/Templates. There are many ways to consume Query data - the most powerful version on the server is to use Razor.

This is a part of my series The New Features of 2sxc 7 and introduces you to the Visual Query Designer. 

We've been contributing thousands of hours to DNN development - mostly in regards to 2sxc, Razor, AngularJS, Training blogs and similar. As we continue to develop 2sxc, we often focus on aspects we need or our customers need - but we would like to hear your needs.

This is part 3 of my short series about JavaScript MVC Frameworks. It will show you some examples of templates with MVC-Frameworks, which basically contain the HTML and placeholders where the data is added.

In this post which is part 5 of my mini-series Learning Razor with an RSS-App I want to get you hooked on the power of Razor (and 2sxc while we're at it :). I will show you how much easier it is to create new designs thanks to the open source, html-close nature of Razor.

As a Q3 special we (actually Raphael) just published a new gallery App based on blueimp, and we pimped it up with neat features like drag-and-drop file upload (in Razor) and optional metadata. In this post, I'll teach you how to do this too!

In this post which is part 4 of my mini-series Learning Razor with an RSS-App we'll enable DNN-Search support for the new Lucene-based search built into DNN in Version 7.2, outsource some complex code and use much nicer template placeholders...

This is part three of my mini-series Learning Razor Part 1 - Create an RSS-App. In this part we'll add animations, client-dependency JavaScript and CSS, support various feed-formats and more!

This is part two of my mini-series Learning Razor Part 1 - Createan RSS-App. In this second part we'll improve it's functionality and security and thereby remove most of its previous shortcomings. After this post, normal admin users can add the App to any page and specify the feed-url without your help.

Since it's now time to get our hands dirty, let me show you how to create a Razor based App. In this first post I'll show you what we'll do in what steps, and we'll create the first version which will already work.

I've written a few posts in my series The Future of DNN Speaks Razor explaining why many technologies are obsolete or going that way. I've also mentioned a few neat new things and in this post I will recommend what HTML-creation technology to use for what part of each application.

So I hope you're read my previous posts why you should migrate to Razor ASAP, what it is and why WebForms and ASP.net MVC are all dead. In this part I would like to delve into WebAPI, why It's awesome (especially for Apps) and why JSON-data is the future - especially combined with AngularJS or similar frameworks.

You may have ready my article on the death of ASP.net WebForms. Along came MVC to provide a new solution. 

 

I'll explain why ASP.net MVC started well but was overtaken by the internet, and why the resulting good solution is still called MVC, even though it's not Model-View-Controller. Our goal is to focus our time and energy on the relevant parts and ignore the rest.

As you might have heard, you have to migrate to Razor soon. Old-school developers have a hard time understanding why WebForms should be replaced, since it's worked to well for more than 10 years. So in this part 3 of my Series The Future of DNN Speaks Razor, I'll explain why WebForms turned out to be the wrong solution for web development and how the web changed to make WebForms' strengths obsolete.

As you might have heard, you have to migrate to Razor sooner than later, and the earlier you start, the more you will be creating future-compatible material today. This is part 2 of the Series The Future of DNN Speaks Razor. In this post I'll explain what Razor is, why it's not MVC (even though Razor is popular there as well) and more.

If you're an old-school DNN developer you're used to using ASP.net Forms - and you've developed tricks and techniques to compensate for various issues like clean SEO-HTML, JavaScript-Control-IDs and more. You've also implemented 3rd party controls (like a Telerik Grid) and spent hours of your time trying to compensate for certain shortcomings. Well, it turns out that this is not necessary any more - but most DNN-dudes don't realize this yet. Because the future is in absolute HTML control - using Razor. Let me tell you why, and how to get started.

This is part 1 of the Series The Future of DNN Speaks Razor. In this post I'll explain why you have to migrate now.

Razor is the future for most output-oriented .net stuff. This also applies to WebForms-based CMS like DNN. But fortunately, they got it right and added Razor-Support about 2 years ago. So here goes: all the ways you could use to access SQL-data directly from Razor without pre-compiling something.
So no Entity-Framework or similar. The five options we'll review are: PetaPoco, SQLReader, DataTable, 2sxc-DataPipelines

Google has an awesome scrips-management engine called GTM. The integration is a bit tricky - but easy once you know how.