|
Get Module by Module ID in DotNetNuke |
|
Brian Dukes
|
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.
|
 |
|
Comments (1)
|
More...
|
|
|
CSS Support in Email |
|
Brad Montgomery
|
By Brad Montgomery on
10/27/2008 9:27 AM
|
|
|
|
Through having to create some HTML emails, I learned that incomplete CSS support seems to be the norm in most current email and webmail clients. Seems like we still need TABLE tags for layouts...
|
|
|
|
Comments (0)
|
More...
|
|
|
Check your CSS for DotNetNuke 4.9.0 |
|
Brian Dukes
|
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.
|
|
|
|
Comments (0)
|
More...
|
|
|
|
DotNetNuke Skinning Approaches |
|
Ian Robinson
|
By Ian Robinson on
10/13/2008
|
|
|
|
With the new skinning changes in DotNetNuke, it may be helpful to give an overview of available approaches to skin developers.
Each of these approaches attempts to answer the question "How do I embed and customize all that great functionality that DNN provides in my skin?" In other words, given that we have a pre-set base of options for functionality (core skin objects), and each of those options exposes certain customization points (skin object properties) that I'd like to set…how the heck do I get it done?
The answer may depend on which technologies you are familiar with (or willing to learn), but let's examine each of the different approaches and see if one clicks for you.
Note: For the sake of simp ...
|
|
|
|
Comments (0)
|
More...
|
|
|
|
C# Compiled DotNetNuke Module Template |
|
Brian Dukes
|
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.
|
|
|
|
Comments (11)
|
More...
|
|
|
Introducing Engage: Events 1.0 |
|
Brian Dukes
|
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.
|
|
|
|
Comments (2)
|
More...
|
|
|
|