Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Skins & CodingSkins & Coding
Previous
 
Next
New Post
1/31/2008 5:35 AM
 

Hi

I want to extend my skins with my own code behind file ( which inherits the Skin class of course ). I want to do this for several reasons.

1) I have a lot of code that keeps returning and I don't want to copy paste it time after time again ( lets not think about the maintenance ! )

2) I want to be able to use 3rd party dll's ( yes, I can access them, but not include them in de skin package )

3) This is not the case right now, but might be in the foreseeable future: suppose I want to show a news ticker on each page... I could possibly make a module for it, add Skin Object functionality, but then my skin would depend on wether or not that module is installed... Wouldn't it be better for it to be included in the skin package itself? This is kinda going towards building small websites and using them as skins, btw :-)

I searched around a bit, but even though it is possible to create a code behind file for the skin and make it inherit the Skin class, it wouldn't be possible to add dll's to the skin package. This would be logical as well, since the dll would have to be moved to the bin folder of DotNetNuke to work... is this correct?

It would be usefull to have a mechanism to upload skins with a dnn file, just like with modules... just a thought...

Thanks

- Varcour

 
New Post
1/31/2008 5:45 AM
 

the purpose of skins is to apply a visual design, not functionality. you can install Skin Objects, to add dynamic elements to the skin, but AFAIK they cannot be packaged with the skin currently and need to be installed separately. I expect, this limitation will be torn down with the new installer of DNN "Cambrian".


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
1/31/2008 7:14 AM
 

there is no need for skins that have dlls.  you'll have to wrap your 3rd party functionality around skin objects.


 
New Post
1/31/2008 7:27 AM
 

CurlyFro wrote

there is no need for skins that have dlls.  you'll have to wrap your 3rd party functionality around skin objects.

I agree, but I'd like to include those skin objects in my skin package, so that I don't have to "assume" ( I spit that word out ) that the required skin objects are already installed.

I took a look at the blog post about Cambrian, I hope this will be included.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Skins & CodingSkins & Coding


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out