Hello,

If you're a programmer, but you need some functionality which is so custom and special, that the DNN and its modules cannot give you i think there are 3 options:

1) Add module IFrame and create your web stuff there using normal aspx and codebehing. You can mask it with design removing scrollbars etc.

2) Develop your custom module control (ascx) along with DNN rules..

3) Trying to enter the core DNN source code and 'hack' something small to achieve your functionality. This of course seems less recommeded because i realize that i can break something bad in the whole CMS system when i'm not well known with all its code. But it's still an option so i listed it, if you think you can share something on that point which works safely...


Is it a good option to choose module IFrame thing (option 1)? What plus and minuses (mostly minuses) you see with that option.

in general I recommend against using iframe's except for simple rehosting of existing webpages for reading purposes - if you try to make it interactive you will rapidly run into problems, though the dotnetnuke iframe module does guard against some of this by allowing you to pass tokens in so the url is more dynamic.

There are many extensibility options in dotnetnuke, not just modules, in some cases widgets http://www.dotnetnuke.com/Resources/W... , skin objects http://www.dotnetnuke.com/Resources/W... , providers http://www.dotnetnuke.com/Resources/W... or even sheduled tasks http://www.dotnetnuke.com/Resources/W... are more approriate for the intended task

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US