News

All Posts Blog: Brian Dukes

Check your CSS for DotNetNuke 4.9.0

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.

C# Compiled DotNetNuke Module Template

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.

Introducing Engage: Events 1.0

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.

DotNetNuke Gotcha: Upgrading DotNetNuke Modules

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.

Announcing Engage: Employment 1.3

We at Engage Software have just released the latest update to our DotNetNuke Jobs Listing module, Engage: Employment, version 1.3.  This is a module you can use on your company's DNN site to list the job openings you have available at your various locations, and accept and sort applications and applicants.

Navigating With Environment Variables

As a developer, and specifically as a DotNetNuke developer, there are a number of directories that I have to navigate to regularly.  In particular with DotNetNuke, I'm going to C:\inetpub\wwwroot\DotNetNuke\Website\DesktopModules quite a bit.  So, instead of having to try to type that in all the time, or navigate through the folder structure, I've defined an environment variable "dm" that is defined as that path to my Desktop Modules folder.  I can just type %dm% into an explorer prompt and be there without any hassle.  I've also setup a %wwwroot% shortcut, though it gets used much less often.  It's a lot like keeping a shortcut around in your dock/quick launch toolbar, but you can also use it in dialogs.  Hopefully this can help you trim off a few more seconds/minutes of monotony throughout your day.

Ready to work with a team that delivers excellence?

Let’s make your vision a reality.

Contact Us →
© 1999-2025 Engage