Find a post...

DNN-Connect Blogs

Making DNN More Design-Centric

The roots of DNN are in Webforms. In the early days of asp.net this was Microsoft’s evolution of the Active Server Pages technology. Since then the world has moved on quite a bit. Various alternatives to Webforms have been introduced on the Winstack and by and large PHP has grown more explosively than any .net based technology. In part, because the php-based cms solutions have been kinder to web designers. How else to explain the vast amount of skins (themes) available to them and the general disdain of any web design firm for .net? OK. Maybe this is not entirely accurate, but the feeling I get is that we could make progress by making DNN more design-centric. And in my opinion that translates to: ensuring a designer has a better grip of where the HTML and CSS is coming from and where to change this.

DNN-Connect.org Officially Live

We’re thrilled to announce that we have launched a new DNN community website dedicated to the DNN platform. A number of DNN community veterans (some of them DNN MVPs) have joined forces under the banner DNN-Connect. And after a couple of months’ hard work we have gone live with http://dnn-connect.org. The motto of our work is “by the community, for the community”. As MVPs it is our role to take initiative and lead community efforts and we feel there is a void left for this site to fill.

(Http) Modules

To our second installment on this two part series on handlers and modules in ASP.NET web applications, their significance and how to begin debugging situations where things have gone haywire. Like I mentioned in the previous post on handlers: modules and handlers go together like peas and carrots. The main difference is the following: whereas a handler runs only when ASP.NET has decided it should handle the incoming request and ASP.NET stops after it has found the handler, the module always runs on every request and ASP.NET continues. So the way that looks is that upon a web request ASP.NET first passes the request to each and every module in the list of modules and then tries to find a handler for it and passes the request on. Most crucially a module can alter a request as it passes through it or set the stage for other components before they run. For the remainder of this post I assume you will have seen/read through the previous post and you are familiar with Fiddler, web requests a ...

Handlers

This post is the first of a two part series about handlers and modules and is an attempt to offload what I know about handlers to you. Knowing what handlers are and how they work is what separates the savvy from the not-so-savvy when it comes to IIS administration. Although very few modules in the DotNetNuke ecosystem use/rely on handlers, those that do experience a steady stream of support calls along the lines of “hey, XYZ doesn’t work” and it is down to a handler issue. Examples of modules that use handlers are Ultra Video Gallery and Document Exchange. DotNetNuke uses handlers itself as well. So what is a handler? In a nutshell a handler is piece of code that handles a web request. To understand why it’s good to know more about this you need to look closer at http traffic (i.e. the bits and bytes that go back and forth between your browser and the server).

Extending DNN - A Nightmare?

At last year's DNN-Europe event our friend Robrecht Sierra moderated a session that started with the provocant statement DNN sucks. While that turned out into an excellent discussion about the road of DNN and the way we are all getting along with the platform, that statement sometimes simply returns true.

Getting ready

Things are getting where they're supposed to be. While we finish the site please hang around, click your way through the communty and let us know your findings.

This Open Source Thing is Cool. How Can I Help? An op-ed.

I can think of two reasons why you’d be a DNN Platform addict. Either you think it’s an awesome tool to make some money or you think you can make some money using this. I’m kidding. There is a second group. Those that itch to work on something bigger than they would otherwise be able to work on, together with some of the sharpest programming minds on the planet. Obviously I’m not excluding you’re here for both reasons. But the focus of this post is on the second group. Those that have been bitten by the Open Source bug.

Blog Module Reborn

I’m happy to announce a new release of the one and only “official” DNN Blog module. And it’s not just some new tweaks here, some bugfixes there. It’s a complete rewrite of this module. I know. That sounds crazy. And it is. But there were some good reasons to do this. In this blog post I’ll elaborate on those reasons and some of the highlights of the new module.

Hosting liberally provided by

Daniel Mettler 11071 88
Geoff Barlow 289 4
Philipp Becker 5345 7
DNN-Connect 426 6
Peter Donker 4202 24
Christopher Hammond 595 2
Olivier Jooris 332 1
Clint Patterson 1 1
Jos Richters 65 1
James Rosewell 224 2
Will Strohl 1438 27
Ernst Peter Tamminga 315 4
Barry Waluszko 1082 2
Gifford Watkins 711 9
Torsten Weggen 1451 3