Subscribe: DotNetNuke Developer Chris Hammond
Added By: Feedage Forager Feedage Grade B rated
Language: English
color  csharpcode  dnn  dotnetnuke  module  movember  net  new  project  release  studio  templates  visual studio  visual 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: DotNetNuke Developer Chris Hammond

Chris Hammond

I've been working with DotNetNuke since January 2003. I specialize in DotNetNuke Upgrades, Module development, and implementations. This blog containers posts over the years regarding tips and tricks on how to do things within open source ASP.NET systems.


New scam: Domain Abuse Notice: from

Tue, 22 Nov 2016 16:30:00 GMT

This morning we received an email from leo-wood - with the following information in it

Dear Domain Owner,

Our system has detected that your domain: DOMAINREMOVED is being used for spamming and spreading malware recently.
You can download the detailed abuse report of your domain along with date/time of incidents. LINK REMOVED

We have also provided detailed instruction on how to delist your domain from our blacklisting.

Please download the report immediately and take proper action within 24 hours otherwise your domain will be suspended permanently.

There is also possibility of legal action depend on severity and persistence of your abuse case.

Three Simple Steps:
1. Download your abuse report.
2. Check your domain abuse incidents along with date and time.
3. Take few simple steps for prevention and to avoid domain suspension.


Please look into it and contact us.

Best Regards,
Domain Abuse Admin
DomainCop Inc.
Tel.: (139) 729-59-00

From my research, this appears to be 100% fake, if you receive similar emails from please do not click on any of the links!

New Visual Studio 2015 Templates for DNN, Now With Wizard for Customizing

Thu, 25 Feb 2016 05:07:45 GMT


I’ve been maintaining my DotNetNuke Visual Studio project templates for a number of years now, one of the things they have sorely been lacking is the ability to “customize” the templates without having to crack open the full source code of the VSIX project, making changes, and then recompiling everything. There are 5 specific strings/values that were ripe for customization, but simply were not easily accessible.

  • Root NameSpace – The Namespace for the project, all of the files were populated with this namespace.
  • Owner Name – A DNN Manifest property that is used to provide information on who either developed the module, or commissioned the module development. This also gets used in all of the Copyright statements built into the templates.
  • Owner Email – Another DNN Manifest property, used to provide an Email address for contacting the owner/developer of a module.
  • Owner Website – The URL of the package’s owner, for further contact and information.
  • Local DEV URL – The URL of your local development environment.

Of all of those items, the one that has likely caused the most headache over the years is the Local DEV URL property, that was set at DNNDEV.ME, which if you followed along with my various tutorials, was the URL I always use for local development, that domain name points to This actually works out great, but some people choose not to follow my tutorials or already have existing development environments configured, yet still want to use my templates. You could still use them, but you had to make some modifications to the PROJ files after creation in order to get things working.

With the latest release of the templates, when you create a project using one of the 6 included templates, you will then be prompted with a Wizard interface (single step) that will allow you to customize these fields.


As always, you can download the latest “release” of the templates from the DNN Store, or from the Visual Studio Online Gallery if you want to get creative, you can check out the Repo on GitHub

Why should you list your open source extensions on the DNN Store?

Thu, 28 Aug 2014 14:53:00 GMT

One of the best things I love about the DNN platform is the ease of building, releasing, and updating Extensions for your website. If you need custom functionality you can either build something yourself, or likely find something that someone else has developed previously that might fit your needs.

If you are an extension developer for DNN (previously DotNetNuke), you have many options for how you can get those modules into the hands of potential customers. If you want to get your modules into the hands of as many different users as possible, you can’t just stick to one distribution mechanism, you need to reach out and try to get your extension available in as many places as possible.

Some of the ways for distributing your modules include: 1) Hosting on your own website, 2) Hosting on GitHub, 3) Hosting on Codeplex. The often overlooked one however, especially for free and open source modules, is 4) The DNN Store.

The Store is a great marketplace for DNN extensions, and while it primarily is used to “sell” extensions, there was even a time free extensions were discouraged or even removed, that is not the case anymore. You can list your extensions, modules, skins, or even providers, to get your products out in front of more customers. Some of the benefits of doing so

  1. More exposure – Besides searching on Google, the Store is the single most accessed place when people are looking for an extension for DNN.
  2. Customer downloads - By uploading your extensions to the Store, people can “purchase” them, with $0 pricing. This allows for those customers to easily find those downloads again in the future, as products that they have purchased and download them again.
  3. Customer updates – You can put out a new release of your extensions, and using the Patch tools provided within the Store you can easily get that patch out to customers as well.
  4. Customer email option - After someone purchases one of your modules, you can have the Store automatically send them an email with information related to the module, resources on how to use the module, what your support policy is, etc.
  5. Customer list – One of the biggest benefits of people purchasing your extensions, you can build up a customer list. What you do with that list might vary.
  6. Referrals – Finally, and one of the biggest items, is the ability to earn some cash from your free extensions? How you might ask? Referrals, if you link to the Store with referral codes included in the links, if a customer actually pays for a module, in addition to downloading your free extensions, you can earn a percentage of that sale. You won’t likely get rich from this, but if you do things right you can get yourself a bottle of Jack Daniels here or there!

One thing I would highly suggest, if you are selling modules, DO not use the Store as a way to get people to “try” your modules, and then point them to your own website to do the selling. That is just not cool.

Please be sure to check out some of my free extensions in the Store: HammerFlex and DNNCHAT being the two most popular extensions I have there. And yes, to be upfront, those links have referral codes embedded in them!

DotNetNuke 7.3.0 Upgrade Issues

Sat, 14 Jun 2014 16:29:23 GMT

Originally posted to With the release of DNN 7.3.0 this week, it was time for me to get my sites upgraded. I upgraded most of the sites without any issues, but wanted to point out a few errors that I received on sites, and how I resolved them. The very first upgrade I did started out bad, it was for this site, and while the upgrade was 100% successful, as soon as I tried to load the site I got a generic 500 error. Accessing the site from the webserver gave me a little more information, seen below, but not much. 500 Internal Server Error The requested Url does not return any valid content. AdministratorsChange this message by configuring a specific 404 Error Page or Url for this website. The first thing I did was run to to see if Bruce had a new version of his URLMaster module available. Sure enough, he had one that was released today, so I needed to get that installed. But how do you install a DNN Module when you can’t actually access the DNN website (due to that 500 error above)? You take the ZIP file for the module/extension you want to install, and put it in the /install/module folder in the root of your website. Once you’ve placed the file in that directory, browse to (replace DNNDEV.ME with your domain name).  That should install the upgraded Ifinity package and resolve the 500 error. Another problem I ran into was that one of my sites, upgrading from 7.1.1 to 7.3.0, received errors on the 7.2.0, 7.2.1, 7.2.2 and 7.3.0 SQL upgrade scripts, the errors were all something like System.Data.SqlClient.SqlException (0x80131904): ALTER TABLE failed because the following SET options have incorrect settings: 'ARITHABORT'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations. That one was actually a pretty easy fix, basically in the SQL database options (using SQL Server Management Studio) there is a Database Compatibility option. The site that had the problem was set to SQL 2000! Not sure how that happened, but it was an easy fix. I set compatibility to 2005 (as that is what all my other DBs were at) and ran the upgrades again (after restoring my backups) and everything ran fine the second time around. The last thing you’ll find is that if you have any CSS in your Portal.css file, in 7.3.0, the Portal.CSS file is TURNED OFF BY DEFAULT. Whomever the genius was that made that call at DNN Corp should really be fired. You can turn portal.css back on in the site settings, under the Stylesheet Editor TAB. Besides those few issues, all addressable with a little effort this evening, I’m pretty happy with the 7.3 upgrade. The HammerFlex skin works great without any tweaks for 7.3 in my testing so far, you can download that from the DNNStore for free.[...]

DotNetNuke HammerFlex Free Skin resources

Mon, 03 Mar 2014 16:48:00 GMT

This blog post is a simple collection of free resources for the HammerFlex skin for DotNetNuke. HammerFlex is a responsive, open source skin that utilizes Bootstrap V3 to provide a flexible mobile friendly layout/design for your DotNetNuke (DNN) websites.

Project Website (source):


Tutorials/Blog Posts

New Release: dnnCHAT v01.00.00 now available using #SignalR

Fri, 20 Sep 2013 15:18:00 GMT

Earlier this year I started on a project to learn how to use SignalR, I had reasons to do so for my full time job (non-DNN related) but considering my DNN experience over the past 11 years I figured that learning how to use SignalR with DNN would be my fastest way to get myself up to speed. So I started working on a Chat module. Originally that module was called SignalRChat, and was available on codeplex, but ultimately I decided that name kind of sucked, so it needed to be something else.

In comes the DNN Chat module project, there was a Chat module for DNN long ago, but the last official release of it was in 2008, and while there was a Beta in 2010, it hadn't seen any development and work in years. So I approached DNNCorp about taking over the DNN Chat project and replacing it with my newly developed module, at the same time, going from "DNN Chat" to "dnnCHAT".

So here we are today, and the first official release of dnnCHAT is now available, v01.00.00, you can download it now from Codeplex.

You can see the module in action on

Here are some of the details about the module, but first things first, a note.

Note: If you previously used the DNN Chat module, and still have it installed, this module will not replace that, the namespaces are different, the Module Name in the Manifest is different. This module WILL NOT UPGRADE the older module. I would suggest uninstalling that module if you still have it, and then installing this module.

Module Details

Minimum DNN Version: 7.1.0
Source Control Location: 
Source Language: C#
Issue Tracking:
Live Demo:

Module Description and Features

This module is based on SignalR, utilizing C#, and requires DNN 7.1.0+, it provide basic Chat Room functionality, allowing both Anonymous and logged in users to communicate in the Lobby, logged in users can also join Rooms.

This is an entirely new module, old instances of the DNN CHAT module should be removed before attempting to use this module (they most likely weren't working anyways).

  • Chat logging in DotNetNuke Database using DAL2 (logs connections and all messages)
  • Ability for users to change their name in the chat window with /nick
  • Ability to create rooms with /join, or join existing rooms
  • Shows the number of connected chat users when in the room
  • Defaults anonymous users are named Anonymous# based on their number in the user queue
  • Uses Display Name if the a user is logged in to the DNN site
  • Strips all HTML from posts
  • Shows when a user connects or disconnects
  • Highlights messages that mention your "nick" in a different CSS class
  • Shows previous message history when you connect

The powerful .NETMF on your wrist! Meet the Agent

Tue, 21 May 2013 12:16:00 GMT

 So if you've been under a rock lately, you might have missed this little phenom known as KickStarter. Well today you're going to want to check it out. Secret Labs, the folks who brought you Netduino (hey, I'm wearing a Netduino t-shirt today, what a coincidence) have teamed up with a watch maker in New York City (SL is based there as well) to bring you Agent!

So what is Agent? I could write this whole long blog post about it, but you'd be better off just reading the KickStarter page.

Basically though, it is a .NET MicroFramework powered device, with long battery life, and awesome features, that will allow you to easily develop for the watch, using the Microsoft tools you already love (Visual Studio 2012).

The project is in a funding phase right now, but I believe the SDK will release by the time the KickStarter campaign ends.

So get to it, fund this project!

Using SignalR with DotNetNuke Modules

Mon, 25 Mar 2013 14:02:00 GMT

Originally posted on, all comments and discussion on this topic should be done there. This post will provide you with a basic tutorial for utilizing SignalR with custom DotNetNuke Modules. If you want to bypass the blog post go check out the source on GitHub, you can Fork my Repository. The module created here will be very simple, if you want a full blown module with more features be sure to check out the open source DotNetNuke Module SignalRChat, and see it in action at SignalR is an ASP.NET library for using websockets and long polling in your applications. Basically what this means, is that you can have your web pages (or apps) maintain an open connection with a webserver, passing data back and forth, without having to do standard posts and gets for the content and functions. SignalR is a free library that you can get from and you can DL from right into your Visual Studio projects. With my new daytime job I had the need to dive deeply into the pool that is SignalR, so I figured what better way to do that than try to create a DotNetNuke module that would use SignalR. There are plenty of Chat examples for SignalR, so I figured that would be a good place to start. This post assumes you already have a DotNetNuke development environment setup locally at, and that you have my Visual Studio templates installed. If you don’t, head on over to the DNN Wiki To start, you should create a new DotNetNuke module using my templates,, I used the C# DAL template, but you can use any of the C# templates. The DAL template has less information that will need to be removed than if you use the DAL2 template, the DAL2 template actually has a working sample in it). I called the module I used for this blog DNNSignalR, but you can name yours whatever you want. Install SignalR Install SignalR into the project using NUGET. To do this open your Package Manager Console (found under Tools/Library Package Manager) in Visual Studio 2012. In the Console run the following line Install-Package Microsoft.AspNet.SignalR This will download the SignalR resources into a Packages folder inside of your module’s folder. SignalR provides a variety of resources that will be utilized, as well as an older version of jQuery which will not be used. Add a Reference In your project add a reference to DotNetNuke.Web.DLL in the website’s BIN folder, this will allow you to use the Route Mapping in DNN 7. Map the Route In order for SignalR to work in DNN7, you need to tell DNN how to handle requests to the path /signalr/hubs/ that path won’t physically exist, due to the way the service framework in DNN7 works this is actually very easy to do. Add a class to your project called RouteMapper.cs using the code in the screenshot here. (In the sample code check out the /components folder) Note: If you are using URLMaster, you will need to add |/signalr to the end of the doNotRewriteRegex setting on the Regex Settings tab of the URLMaster Friendly URL Settings module (under the HOST menu). Create the ChatHub The ChatHub.cs class will be the listener on the SignalR side, “clients” (the view of the module) will send to that chathub using the Send method. The Hub will then broadcast that information back out to all connected clients using the addMessage javascript function, implemented in view.ascx later in this post. In this example ChatHub is really simple, but you’ll find that this class will likely be fairly complex as you start to build our the ability to send messages to different “Groups”, which is supported by SignalR. Creating the View Control The View Control in this DotNetNuke module is going to be pretty simple, but it also does everything for the module. It will communica[...]

Customizing the latest Module Dev Project Templates

Mon, 28 Jan 2013 21:12:00 GMT

With the 2.0 release of my module development project templates last week I’ve had a few inquiries into how to customize the templates. You can download the templates from

Why Modify the Templates?

First, why might you want to modify the custom templates? The main reason is that these templates are defined using a specific namespace, DotNetNuke.Modules.*, which is fine in most cases, but what if you want to use your own namespace? Well you have to create a project, then search/replace all instances of that namespace, while not removing any DNN references at the same time. Customizing the project templates will allow you to define your own company namespace, email address, website, and even copyright information, in the template so that you do not have to search/replace every time you create a new project.

Read the full post on

Comments are disabled due to the spam problem on

Using the new Module Development Templates for DotNetNuke 7

Fri, 25 Jan 2013 18:12:00 GMT

(image) With the release of DotNetNuke 7.0 (and now the more recent 7.0.2), it was time to update my module development project templates. If you have worked with my module development templates before, here are the major changes for this release. If you haven’t worked with them before please read this whole blog post as I discuss how to get up and running with the templates.

What’s New

This section will cover some of the “new” features of this template release. If you’re familiar with my previous releases this will hopefully get you up to speed on what is new. If you are new to the whole process it will help you understand a few of the features in the templates.

For more information about the templates read my full blog post on my website.

Comments are turned off here due to the fact that has a horrible spam problem

10 Years of DotNetNuke

Tue, 25 Dec 2012 04:54:57 GMT

In case you haven’t heard, today is our birthday! Back on 12/24/2002, Shaun Walker released an open source project he called (at the time) IBuySpy Workshop in the forums here on IBSW was a project which containers many enhancements to the IBuySpy Portal that Microsoft had released as a reference app in the early days of the .NET Framework.

Well 10 years later, that application is still here, a few months after that first release it was renamed to DotNetNuke. Check out Shaun’s blog post for a little insight into the early days, and also be sure to check out our 10 Year Timeline/Info Graphic has a problem, it is spam

Mon, 17 Dec 2012 15:24:55 GMT

Is anyone at Microsoft listening to the SPAM problem here on My “Can anyone do anything about the spam here on” post from October got over 12 spam comments posted to it in the past 24 hours. I have comments all moderated, but that just means I have a crapload of work to do each time people comment.

Also, when you click on a link from a comment notification email you are taken to an insecure site warning due to an invalid SSL Cert.

We really just need some updates software, something with better filtering, better captcha, etc. Please, can we get an upgraded sometime in 2013?

DotNetNuke 7.0 released

Thu, 29 Nov 2012 00:54:52 GMT

It is a big day in the world of DotNetNuke (yes, DNN is still around folks). DNN 7.0 was released today, you can find out more information by visiting

Be sure to read Will Morgenweck’s blog post for all the details.

For a quick peak into DNN 7 check out these two videos, What’s New and Getting Started.

What's new in DNN 7

height="315" src="" frameborder="0" width="420" allowfullscreen="allowfullscreen">

Getting Started in DNN 7

height="315" src="" frameborder="0" width="420" allowfullscreen="allowfullscreen">

New free DotNetNuke 7.0 Skin

Sat, 24 Nov 2012 06:25:02 GMT

With the pending release of DotNetNuke 7, scheduled for this week, I updated my free DotNetNuke (DNN) skin, MultiFunction v1.3. This latest release requires DotNetNuke 7, it shouldn’t install on an earlier version of DNN.

This release updates a number of the CSS classes for DNN 7 specific styles and objects. Overall the design of the skin doesn’t really change much, just cleans up CSS mainly for this release.

I also updated to the 3.0 version of the Orangebox jQuery plugin, you can find the code included inside the package.

You can also find the Source package (c#) of the skin there on codeplex, useful if you are looking for an example of how to create/modify a skin for DNN.

If you’re using MultiFunction, I’m curious to see some links to sites that use it, feel free to post in the comments below.

Using jQuery to customize the styles in table cells

Wed, 31 Oct 2012 20:18:19 GMT

Originally posted on I was trying to do some work with the Form and List module in DotNetNuke today and I needed to apply some custom styles to the LIST view of a module, without going in and creating a full XSL template for the module to use, I wanted to style the default table based grid view. In order to customize this view though I needed to do some custom jQuery that runs after the table is loaded, the jQuery then goes through and looks for columns, and based on the number of columns, adjusts the way those columns display. First I wanted to make it so that a specific column didn’t have text wrapping, which in HTML would normally use the nowrap property on a column, but because of the dynamic nature of F&L you can’t configure that manually. To achieve this I needed to loop through each Table Row (TR) in the table, and then find the column in question, and apply the css attribute/value for white-space/nowrap. To do this I used code like the following. $("#tableId tr").each(function(){ var cellCount = $(this).find("td").length; if(cellCount==4) { $(this).find("td:eq(0)").css("white-space","nowrap"); } else { $(this).find("td:eq(1)").css("white-space","nowrap"); } }); .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: #ffffff; /*white-space: pre;*/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: #008000; } .csharpcode .kwrd { color: #0000ff; } .csharpcode .str { color: #006080; } .csharpcode .op { color: #0000c0; } .csharpcode .preproc { color: #cc6633; } .csharpcode .asp { background-color: #ffff00; } .csharpcode .html { color: #800000; } .csharpcode .attr { color: #ff0000; } .csharpcode .alt { background-color: #f4f4f4; width: 100%; margin: 0em; } .csharpcode .lnum { color: #606060; } Basically that goes through and finds each row in the table, then checks to see how many columns there are. I do this because the VIEW for the table when you are logged in, versus when you aren’t logged in, is different, the F&L module adds an Edit column at position 0, so you can see in the ELSE statement I basically want to set the width on the 2nd column, position 1 in the zero-based array. If you want to do something similar for the HEADER row of the table you have to do things slightly differently, using the following code $("#tableId tr:eq(0)").each(function(){ var cellCount = $(this).find("th").length; if(cellCount==4) { $(this).find("th:eq(0)").css("text-align","left"); $(this).find("th:eq(1)").css("text-align","left"); } else { $(this).find("th:eq(1)").css("text-align","left"); $(this).find("th:eq(2)").css("text-align","left"); } }); .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: #ffffff; /*white-space: pre;*/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: #008000; } .csharpcode .kwrd { color: #0000ff; } .csharpcode .str { color: #006080; } .csharpcode .op { color: #0000c0; } .csharpcode .preproc { color: #cc6633; } .csharpcode .asp { background-color: #ffff00; } .csharpcode .html { color: #800000; } .csharpcode .attr { color: #ff0000; } .csharpcode .alt { background-color: #f4f4f4; width: 100%; margi[...]

Are you ready to grow that Mo (moustache)? Movember is coming

Fri, 26 Oct 2012 19:40:00 GMT

Well here we are, nearing the end of the month of October and coming up on the month of NMovember once again. We here at DNNCorp are in our third year of supporting the Movember cause, growing facial hair on our upper lips to raise awareness and money for men’s health issues. Anyone can participate in Movember, and if you sign up, join a team, you can order some free materials from the Movember organization that you can use to help try and raise funds. The rules for Movember are simple. Start clean shaven on Movember 1st (if you want to cheat here, I won’t frown upon starting completely clean shaven) Grow a moustache for the entire month, but it should be a moustache! It can’t connect to your sideburns, that is a beard It can’t connect at your chin, that is a goatee (handlebars are fine) Spread awareness about men’s health by engaging in conversations that start because of your moustache Conduct yourself like a gentleman. How to be successful with a Moustache Still not sure what Movember is? Check out my 5 minute IGNITE Session from DNNWorld 2012 height="315" src="" frameborder="0" width="560" allowfullscreen="allowfullscreen"> Join a Team DNNCorp has created two teams, one for our employees in the US, and one for our employees in Canada. Feel free to join one of these teams (preferably in your country of residence), or you can also create your own team (see below). Here are some links to the teams and the Network as a whole. Register at Movember – Join Team DNN US - or Join Team DNN Canada - DotNetNuke Network - Create your own team We are encouraging companies or even DNN user groups to create their own Movember team, and then join the DNN Network, to get started head on over to and register, then create your team and invite your friends and fellow employees to join your team. After you create your team email me chris.hammond @ to let me know what your team URL is so that I can have it added to our Network, I don’t think you can do that yourself (but you might). Download the Movember App If you have an IPhone or Android device, there is a Movember app that you can download from the appropriate store. The app will allow you to track your donations, and even take a photo once a day for all 30 days for the month so that you can put together a short video at the end of the month tracking your progress. Fundraising, start small The point of Movember is to raise awareness for men’s health, you can do that through discussions, as well as by raising money for Movember. Donations then go between the Prostate Cancer Foundation and other organizations. I would encourage you to set a goal of raising $100 for Movember. With a few donations from friends and family raising $100 is hopefully a small enough goal that you can easily achieve it, then, if you desire, you can increase your goal and try to raise more money! Join Now! Movember starts in less than a week, head on over to and register! Over the next few weeks I will be posting additional blogs with ideas on how you can reach out to friends/family to garner donations, as well as fun ideas for things you can do around the Movember theme.[...]

Can anyone do anything about the spam here on

Mon, 01 Oct 2012 07:20:00 GMT

If there anyone out there who can do something about the spam here on Perhaps we could get some new software here that we could use to blog with? The old software barely works in Chrome (I can't see the rich text editor at this point), and lately the notification emails for Comments (which are mostly spam anyways) are pointing to which tries to get you to login with Anyone still maintaining this place?

New Visual Studio 2012 Project Templates for DotNetNuke

Mon, 27 Aug 2012 21:13:41 GMT

Earlier this month Microsoft put the bits up for Visual Studio 2012 RTM out on MSDN Subscriber downloads, and during the first two weeks of September they will officially be releasing Visual Studio 2012. I started working with VS2012 late in the release candidate cycle, doing some DNN module development using my templates at These templates work fine in Visual Studio 2012 from my testing, but they still face the same problem that they had in Visual Studio 2008 and 2010, you have to install the MSBuild Community Tasks project prior to using the templates, otherwise projects failed to be created. The other problem with the templates is that they are not easily discoverable, you couldn’t find them in Visual Studio, and they weren’t part of the Visual Studio Gallery. Enter the latest version of my module development templates. I’ve from the ground up rewritten the project templates, and built them into a VSIX package, a unit of deployment for Visual Studio 2012. While it is true that you can create VSIX files that work in both Visual Studio 2010 and 2012, this project was designed specifically for 2012, and will not likely work in 2010, though I will do some testing and see if I can’t make it work in the future. Overview of the DotNetNuke Project Templates There are currently two templates available within the project, one for C# and one for VB.Net. These templates utilize MSBuild for automated packaging of the modules you create, just as previous versions of the templates have. They create compiled modules, meaning stand alone projects, that have their own DLL’s, making them easy to deploy and manage. They differ slightly from the previous version of the templates in that the deployable packages are now in the INSTALL folder within the module, instead of the packages folder. You can now download new templates directly from within Visual Studio using the Tools\Extensions and Updates menu option. The templates are currently packaged as a Tool in the Visual Studio Gallery, not as individual template projects, so they can only be found by searching for them online, or via the Tools\Extensions and Updates option. As I release new versions of the template project you will be able to upgrade to the later templates using the same Extensions and Updates interface. In order to start using the templates for you module development within DotNetNuke you will need to perform a number of steps, the first thing being installing the templates (if you don’t have Visual Studio 2012 installed, that would be your first step). How to Install the Visual Studio 2012 DotNetNuke Project Templates Installation of the templates is pretty easy, there are multiple ways to do this, choose one of the three options below and perform the steps listed for the option you choose. You only need to do one of these options, not all three. Install using the Tools\Extensions and Updates menu Mouse over the Tools menu Click on Extensions and Updates Search for DotNetNuke Choose the Install button for the DotNetNuke Project Templates option Install manually by downloading the VSIX file from the online gallery Visit the Visual Studio Gallery – DotNetNuke Project Templates page Download the VSIX file via the Download link. Double click on the downloaded file to install the templates. Install manually by downloading from Codeplex Download the VSIX file from Codeplex Double click on the downloaded file to install the templates. Cr[...]


Wed, 15 Aug 2012 02:52:03 GMT

Earlier today the latest release of the .NET MicroFramework (v4.2 QFE2) was released over on You might ask, why does a DotNetNuke guy care about that? Toys! Well, I call them toys, they are my toys. I’ve dabbled with Netduino over the past year or more and am looking forward to getting the new firmware from Netduino installed on my devices.

Along with the new .NETMF release Netduino has updated the Firmware for the devices to be able to utilize the new bug fixes. Check out Chris Walker’s post over on for the full details.

A quick snippet from his post to get your juices flowing:

This exciting new release includes a number of major enhancements over .NET MF 4.1:

  • 50% more RAM for Netduino Plus (42KB vs 28KB)
  • Visual Basic support
  • New WinUSB drivers (for those who had ocassional BSODs)
  • StringBuilder and other new classes
  • New core AnalogInput and PWM classes
  • Garbage collector bugfixes
  • More bugfixes; see

Users are welcomed to upgrade to their boards to .NET Micro Framework 4.2 at the time of their choice. The new SDK supports both 4.1 and 4.2 projects, so you will be able to use both boards with the same SDK. We will continue supporting users on both versions for the time being.

Now, which project do I upgrade first? The Netduino Tank, or DNNFoos? Probably the later as that has direct applicability at the office (image)

Here are some of the posts over on Netduino that will be helpful for you to get going with upgrades.

  1. Upgrading .NETMF 4.2 qfe2 and Netduino SDK
  2. Upgrading the Firmware on your Netduino(s)

The risks of using hosted resources, hosted jQuery

Mon, 13 Aug 2012 22:09:28 GMT

Long ago when we started shipping jQuery resources with DotNetNuke we began offering a Host Setting which allowed you to use a HOSTED version of the jQuery resources. There are a number of benefits for using the hosted jQuery resources, of which I will mention some below, but there are also some potential disadvantages or risks to this as well.

First a quick summary of what the setting allows you to do. With DNN (specifically with DNN 6.*+) we ship both jQuery resources and the jquery.ui resources. These are javascript files that exist on the web server that hosts your DotNetNuke website. Using the HOSTED setting allows you to basically have those files distributed from a CDN (content delivery network).