By Brian Dukes on
12/3/2008 11:50 AM
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.
Read More »
|
By Brian Dukes on
11/20/2008 1:47 PM
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 »
|
By Brian Dukes on
10/29/2008 2:42 PM
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 »
|
By Brian Dukes on
10/17/2008 1:07 PM
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 »
|
By Brian Dukes on
10/7/2008 9:32 AM
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.
Read More »
|
By Brian Dukes on
10/2/2008 2:00 PM
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.
Read More »
|
By Brian Dukes on
10/2/2008 10:16 AM
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.
Read More »
|
By Brian Dukes on
7/24/2008 10:04 AM
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.
Read More »
|
By Brian Dukes on
7/15/2008 1:40 PM
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.
Read More »
|
By Brian Dukes on
4/30/2008 2:38 PM
On our DotNetNuke module demo site, we have a little selector (pictured above) in the upper right hand corner that lets you pick how wide you would like the site to appear. This is based on a similar mechanism on the DNN site. Folks have been asking about it, so feel free to register on our site and grab it for yourself (for free).
Read More »
|