DNN Blogs

The DNN Platform has strong support for internationalization. You can install so-called language packs that ensure the UI can be seen in another language and you can make fully multilingual sites using the "content localization" feature. The latter allows you to create alternative content for different languages and is not the subject of this blog post. This post is all about the former: showing texts baked into your DNN system in other languages than English.

You probably will have seen this coming. It is with great sadness that we have to announce DNN Connect 2020 will be postponed. "First the European Football Championship, now this", I hear you say. Indeed. It's a bitter pill. What would have undoubtedly been the highlight of this DNN year is no longer.

If you're familiar with the source code of the DNN Platform, you probably agree with me that it is not easy to set up for development purposes. And you'll probably agree with me that it is not entirely clear how to build. Or even what build does. Just so you know: we are working to improve this. If only to make our own lvies easier developing DNN.

There are a number of things that change when you progress from developing a module just for yourself to developing modules for a wider audience. DNN has a ton of features to make life easier for you and to protect the user on the other side. This is vital because you have no idea where the module will be installed. Like the version of DNN your module will be running on, other extensions that have been installed or the selected theme. In this post I'll delve into some of the factors influencing the decision which DNN version to target with your extension.

I have said on many an occasion. And I'll readily admit that in part this is just an old coder's frustration with a new technology. One of the many "get off my lawn" moments I've gone through. But like it or not, NuGet is here to stay and in our Microsoft-oriented world it is the standard way to resolve references. Before we had NuGet we'd do this "manually". So before I go any deeper into this, let's first explore what the breadth of the problem is and how we used to do this in the old days. You know, when telephones were still attached to a wall.

A few of us are discussing whether to move away from Slack as a collaboration tool in favor of the forums on the new community website. The two main drawbacks with Slack are (1) that it is "yet another tool" and therefore not immediately available to someone who wishes to join a conversation and (2) that old discussions fade away in time (and also not searchable etc).

Unless you have been living under a rock, you probably know there was a DNN party earlier this month in Switzerland. The party was called DNN Connect and held in the Alpine mountain village of Champéry. As both the president of DNN Connect and the location manager for this event, I had quite a bit to do with proceedings this year. So the hole I dropped into when I waved the last attendee goodbye was immense. A severe case of the post-conference-blues. So besides picking up "regular work" again I've been staring at my monitor thinking "now what?" Well, time to reflect on this event.