Brian Dukes

Embedding JavaScript and Other Resources into .NET Assemblies

bdukes@engagesoftware.com — Tue, 09 Jun 2009 13:35:00 GMT

I just wrote up a guide on why and how to embed JavaScript (and other files) into your assemblies when making DotNetNuke modules. If you're interested in a peek at some of our advanced development practices, take a look over on my personal blog.

More...

Engage: Rotator 2.0

bdukes@engagesoftware.com — Mon, 04 May 2009 15:44:00 GMT

Engage: Rotator is our content rotation module for DotNetNuke. We just released the 2.0 update with full templatability and a huge number of new rotation and animation options.

More...

Packaging Modules for DotNetNuke 5

bdukes@engagesoftware.com — Tue, 17 Feb 2009 14:13:00 GMT

We just released Engage: Events, and realized that our DNN 4 compatible package might not work exactly as we'd like when used in DNN 5. If you're a DNN module developer, you probably already know that there have been a ton of changes to the module installer in 5.0. It will still accept the old module packages, but you'll miss out on a lot if you don't provide an updated package.

More...

Engage Events 1.1

bdukes@engagesoftware.com — Thu, 12 Feb 2009 22:06:00 GMT

The first major update for Engage: Events has been released! Engage: Events is the event management module for DotNetNuke from Engage Software.

More...

Editing .SqlDataProvider scripts within Visual Studio

bdukes@engagesoftware.com — Wed, 03 Dec 2008 17:50:52 GMT

I had finally had it. I was no longer accepting the lack of tool support while editing the .SqlDataProvider scripts for DotNetNuke modules. I needed to figure out a way to make Visual Studio treat those files as if they ended with .sql instead of .SqlDataProvider so that it would give me syntax highlighting for my SQL scripts.More...

Engage: Employment 1.4 for DotNetNuke

bdukes@engagesoftware.com — Thu, 20 Nov 2008 19:47:15 GMT

Have you heard of our Engage: Employment module for DotNetNuke? I'm talking about our module for posting job listings on your website and allowing folks to apply for them. We have today released a new version of the module to fix a number of bugs that have been discovered, while completely revamping the administrative experience.More...

Get Module by Module ID in DotNetNuke

bdukes@engagesoftware.com — Wed, 29 Oct 2008 20:42:46 GMT

When building DotNetNuke modules, a number of times I've run up against the issue of trying to instantiate a ModuleInfo instance with only a module ID. However, the GetModule signature on ModuleController takes both a module ID and a tab ID. In this latest instance where I've come against this issue, I was actually trying to get a tab ID based on the module ID, so I obviously didn't already had one to provide. More...

Check your CSS for DotNetNuke 4.9.0

bdukes@engagesoftware.com — Fri, 17 Oct 2008 19:07:22 GMT

Starting in DotNetNuke version 4.9.0, only the module.css in the main folder of a module is referenced, regardless of where the control being loaded lives (unless there isn't a module.css there). Therefore, you only need one module.css to control the styles of all of your controls.More...

C# Compiled DotNetNuke Module Template

bdukes@engagesoftware.com — Tue, 07 Oct 2008 15:32:54 GMT

It shouldn't be hard to get started writing a module for DotNetNuke, but it doesn't seem like there's a whole lot of help especially when you are wanting to use C#. At Engage, we have created a Visual Studio project template which will get you started developing a C# DotNetNuke module, using a Web Application project (rather than the, in my opinion, much more cumbersome Web Site project). It is available for free on our downloads page after registering on the site.More...

Introducing Engage: Events 1.0

bdukes@engagesoftware.com — Thu, 02 Oct 2008 20:00:26 GMT

After three public pre-releases, and weeks of wrestling through user-submitted bugs and those we found (so that you don't have to!), we are now ready to release Engage: Events to the eagerly awaiting public! After we cemented our feature-set in the Beta release, we have hunted down no less than 15 bugs, ranging from grammar to complete show-stoppers. We are very thankful for the support of the community as we worked together to create a DotNetNuke module that fits your needs, from the ground up, based on your suggestions.More...