Radiating Awesomeness, One Blog Post at a Time.

What’s this about?

This is about TagHelper’s in ASP.NET Core, and how to get more flexible @addTagHelper directives.

... Read More

DnnPackager - v2.0.6
19 March 2016

DnnPackager Release -v2.0.6

A short post to announce that a new minor release of DnnPackager is out.

You can find the release notes here explaining what’s new: https://github.com/dazinator/DnnPackager/releases/tag/2.0.6%2B2

For an introduction to DnnPackager in general see here

Special thanks to @nvisionative for requesting this feature.

... Read More

I have been doing some work on DnnPackager recently, and I’ve come accross the concept of “Source” packages. I have to admit I am not entirely new to these, but I’ve never personally used them for my projects in the past.

Source packages are basically identical to the ordinary install zip’s for your dnn module / extension, i.e you “install” them into your Dnn site like any other install package, except that they also include “source code” files within them, like .cs, .vb files etc.

... Read More

This post is part two of a series. For part one see here

Part 2 - Replacing Bower with JSPM

In part 1 of this series we created a shiny new ASP.NET 5 project, and I introduced some fundamentals.

For reasons discussed in part 1, let’s now go ahead with our first task, which is to ditch Bower in favour of JSPM as our javascript package manager.

... Read More

Introduction

When developing DotNetNuke extensions, we typically use one of the existing Visual Studio Project Type’s, for example - an ASP.NET Web Application project.

Even when using a Project Template such as Christoc’s, the project template is still based upon one of the standard Visual Studio project types - usually an ASP.NET Web Application project.

However these Project Types do not “gel” well with DotNetNuke development in a number of areas, the main ones being:

  1. Running the project in VS (clicking play) - wants to run the extensions as a Web Application, but this makes no sense for a Dnn extension - which has to be hosted by the DotNetNuke website.
  2. Deploying the extension - there is no support for that in the project system - you have to manually deploy your extensions to the Dnn instance.
  3. Debugging the extension - you have to manually attach to process.

So.. what if there was a new Project Type, one that was purpose built for DotNetNuke development? What would that look like?

... Read More