News

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.

With the new skinning changes in DotNetNuke, it may be helpful to give an overview of available approaches to skin developers.

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.

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.

Sometimes a simple change and all of a sudden your module is mysteriously showing errors in strange places. Here's are a couple of tips to keep some of these scenarios from affecting your modules, and how to recognize them if they do.

The final BETA release is feature complete. What you see in Engage: Events BETA will be what you get in Engage: Events 1.0. We're still seeking your help to make sure the features that are included in Engage: Events work properly, function as expected, and position the product to quickly improve upon the initial release.

It's been a few months coming but Engage: Publish 5.2 released last week while I was off in Kansas racing. There are a lot of new features/enhancements and bug fixes in the release. You can read a forum thread where I discuss a lot of the new functionality and changes here. You can also check out the release notes in our Wiki.

Approached by the team at DotNetNuke, Engage agreed to contribute our efforts to help branding DotNetNuke by creating a new design template on the new default skin.

We take pride in trying to offer professional products and services to the DotNetNuke community. In providing commercial modules, two components of the module define professionalism - the quality of the product, and the quality of the support.

Do you have a gauge for your site's effectiveness, performance, and overall health? By offering a consolidated display of site metrics and portal administration tools, Dashboard acts like a diagnostic test for your website.

We've released the next Alpha release of the Engage: Events module for DotNetNuke. Try it out and let us know what you think and what you'd like to see from this module.

We've been hard at work to create a new DotNetNuke module to manage your website's events. Take a look and let us know where you want us to go with it.