News

Saturday, October 2nd was the Day of DotNetNuke in Chicago. A number of us from Engage attended and spoke.

I’m really excited to finally be able to introduce version 1.4 of Engage: Events.  This release addresses, in my opinion, the biggest missing feature of the module, event categorization.

We recently released a new version of Engage: Rotator which featured four new templates to display rotating content on your DotNetNuke site.

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.

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.