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.

I used to believe QR codes were useless marketing gimmicks. Then I visited Japan in 2011 and QR codes were everywhere. You could see them on the walls of skyscrapers in Tokyo, on product packaging - and even on every tiny 1x3-inch ads in the magazines. Usually it's time to re-evaluate an opinion once you see that an large, smart group of people have an opposing point of view. So I re-evaluated.

In this blog I would like to tell you what the QR-Code is (in case you're new to it), why it's great, and how to make bad and good QR-codes (as it's easy to botch up).

As you probably already know, I love no-server-code Apps. They allow admins/web designers to extend their DNN without requiring host-permissions and without risking the system stability. It also allows them to modify the extension with very basic capabilities. When creating the ImageCompare App I ran into some common issues that you will have as well - and would like to share the lessons-learned here.

This Blog is about 2 things. On one hand it's about Syntax-Highlighting, but actually it's more about creating safe No-Server-Code-Apps.

For the DNN-Connect event in Italy, we demonstrated how to create a powerful feature-rich DNN-App in 1 hour. Here you'll find the live-demo, the live-recording from DNN-connect and you'll be able to download the App for any modifications. + you will discover how to create similar Apps with similar effort. Go for the low hanging fruits :)

Let's get strategic - and break some points. Not share-points but breakpoints :).

To understand the challenge: we're creating a website and want it to be responsive. One of the aspect of a responsive site is that it responds to the screen size - presenting the content as best as possible at every possible screen size - and there are thousands of screen sizes - multiplied by browser types and you'll get a lot of test scenarios - too many, to be exact. So we need a strategy...

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

Remember the old days when we pretended we had What-You-See-Is-What-You-Get? Right now I'm writing this blog on the Telerik-editor built into DNN and it's terrible. But that's ok, with responsive webs, the WYSIWYGs days are over.

This is a follow up to my previous blog post how to integrate Google Tag Manager (GTM) into DNN. The post had about 150 reads so I believe there's a need for a packaged App.

The concept of DNN Modules has many weaknesses. What we dislike most are things like...if you install/remove a module, DNN might stop working. We believe there is more sexy way to do things - so we did it :)

Responsive strategies beat Adaptive strategies in about 99% of all cases. So I'll start with explaining what these words mean, and show how Responsive has already kicked Adaptive's but. Then we'll see some statistics and likely explanations.

Many people believe they can create a responsive website simply by downloading a responsive skin. This is like creating a great present simply by buying the right gift-wrapping - it barely scratches the surface. 

This is part 1 of my special responsive/mobile/retina series, in which we first figure out what we're actually trying to do, and segment it into a horde sub-topics.

I really, really hate the DNN-forge.
And I really, really hate how DNN-Corp handles support requests for the forge.
And I've really tried hard - for over 2 f*** years.

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