Learn More





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...Administration ...Administration ...Hosting all DNN assets on Azure CDNHosting all DNN assets on Azure CDN
New Post
11/3/2015 9:29 PM

HI All,

I host my DNN website on Azure WebApps. I want to move ALL my images and client-side assets to the Azure CDN service. This part is really easy – you can now point Azure CDN at a webapp and it will handle the synching of assets to the cloud CDN. The tricky part is now I have to change every single image across every single module to use the CDN URL instead.

It strikes me that there should be a build in option for this in DNN – instead of always defaulting to the core Portals directory when choosing files, there could be a URL prefix set at Site level. I could then put the Azure CDN address in there and all client side assets could be served up by the CDN instead of my webapp.

Has anyone used Azure CDN in this matter with DotNetNuke?  (and this is another good reason to host on Azure instead of a traditional hosting provider – you can use scalable cloud services ;)


PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

New Post
11/4/2015 2:37 AM
I have created something like this:
1. All files are stored locally in DNN
2. When first request to file comes in for new or modified file, it is being put into into Azure queue to be copied over to new location. Copying is done once an hour by Azure web job.
3. When second requests comes in and file in question has been already copied to new location, browser is simply redirected into this new location

Good with this is that if I decided to stop using this other storage option, I can simply delete the entries from web.config that handle these and everything is served again from DNN own file structures.

This is implemented as a custom HttpHandler for selected file types.

If you think this scenario is something that would interest you, I can for sure open up this more. You can see this in action on my own site, link below.
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Hosting all DNN assets on Azure CDNHosting all DNN assets on Azure CDN

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.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  

What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out