Blog

With the advent of 2010, we at Engage took some time to reevaluate our products business (Engage Modules and Engage Skins).  The last six months or so of 2009, we were swamped with client work and were unable to make any substantial enhancements or fixes to our DotNetNuke modules.  We recognized that this was unacceptable, and have been working to restructure our business and commitments so that we can maintain a consistent support, maintenance, and enhancements for all of our products.  As a result, we've made some internal changes to make sure that work on our product lines cannot be ignored because of client work, however pressing it may seem.

We've just released updates to Engage: Events and Engage: Employment.

 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.

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.

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.

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

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.

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.

Read More »

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.

Read More »

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.

Read More »