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!

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.

DNN Platform Update Service

As the DNN Community continues to take over responsibility for the management of the DNN Platform we continue to chip away at the assets and features that were not fully under the control of the community. One of these key elements, that is often overlooked, is the Update Service. I have developed and contributed to the DNN Community a replacement to the Update Service, completely re-written in .NET Core with a focus on security & data privacy. Support from the .NET Foundation will allow us to host the service. Starting with DNN 9.4.0 this service will become the new standard going forward, however, we are looking to get users testing with the update service on older versions of DNN, and would appreciate ANY metrics that can be gathered from these older installations.

What Does the Update Service Do?

Many might be unaware of exactly what the DNN Update Service does, so I thought it would be great to be fully transparent and describe the features/functions included.

Extension Package Updates

This is the most commonly visible portion of the Update Service system. When viewing the “Extensions” functionality within the DNN Platform the grid contains an “Upgrade?” column. The display of the upgrade version is provided by the upgrade service.


This information is managed for ALL extensions, regardless of the vendor based on installations. If a new version of an extension is discovered the upgrade is communicated to the greater community.

Extension Package Upgrade Links

Related to the above feature, if an upgrade is available and displayed on the Extensions page, users are able to click on the upgrade version number. The initial intention for this was to link to the vendors website. The current behavior of the existing update service is to render a blank page. The new update service will take users to a page outlining that an upgrade is available, but that they need to contact the vendor.

Future enhancements are being planned for the Update Service that will allow us to redirect to the module vendor, or other location to obtain the needed information.

Security Bulletin Listing

Within the PersonaBar a listing of Security Bulletins is displayed.

The information for this page comes from the Update Service. This functionality for installations prior to DNN Platform version 9.4.0 will continue to come from the existing service that is managed by DNN Corp/ESW as the service URL is not configurable in DNN.

What & When Is Information Collected

The DNN Community strives to be transparent with all of the information that we collect as part of operating this service. The following outlines all information that is retained by the new Update Service, we do not have visibility into the existing Update Service, therefore, their information storage may be different than this new Community Driven service.

Extension & Framework Update Information

The Update Service is contacted any time that an installation has been configured with the “Check for Software Updates” option enabled. If this option is disabled, no information is transmitted to the service.

When checking for updates the following information will be provided to the Update Service

  • Host GUID - The unique GUID value for the DNN Platform Installation (Example: AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE)
  • DNN Platform Version - The current installation version (Example: 090400)
  • Portal Count - The total number of portals in the installation (Example: 24)
  • Windows, SQL, and .NET Framework Versions - Currently running information (Example, 17/17/45)
  • Instance Count By Extension - How many times an individual extension is used (Example: 24)
  • Extension Name - The unique name of each extension installed (Example: DNN_HTML)
  • Extension Version - The current version of each extension (Example 090400)

The Update Service retains all of this information, however, it should be noted that this service does NOT, in any situation retain the URL, Host Email, or other identifying information on your installation.

Security Bulletin Download

Currently, in prior to 9.4.0, an installation will communicate to the update service at ANY time regardless of the “Check for Updates” or other configuration when viewing the “Security Bulletins” tab on the “Security” feature in the Persona Bar. When making this request the current installed DNN Platform version is included.

This process might change with the DNN 9.4.0 release, however, the exact change isn’t known at this time.

Why Collect This Information

The Update Service is a critical tool for analysis as we continue to move the platform forward technologically we will have greater ability to assess the community size, versions used, and overall health of the community.

Armed with this information we can make smarter decisions on technology changes, usage patterns, and testing processes.

Privacy of Information

All information stored as part of the DNN Upgrade Service is stored in a manner that is anonymous and cannot be traced back to a specific installation. However, we still take the privacy of the collected information seriously. All collected information will be used for the sole purpose of providing update notifications to DNN Platform Information and aggregated reporting on technology adoption within the DNN Platform installation base.

Getting Involved - Use the New Service

The new service is hosted, live, and ready to be used. It will work with historical versions of DNN, however, it requires a small web.config change to actually be used. We are encouraging any/all that are willing to update their existing installations, regardless of DNN/Evoq version, to use this new service so that the DNN Community can get access to the data. We do NOT have ready access to the historical information from the existing DNN Corp provided service.

To use the new service update the UpdateServiceUrl appSetting within your web.config to match the following:

<add key="UpdateServiceUrl" value="" />

Once this has been completed the update service will use this new location for service. Be sure to also have the “Check for Updates” option enabled. If you have any issues/feedback feel free to share here.

The Future

At this time direct access to the stored information is severely limited, as the community continues to collect the information I have a desire to share relevant usage information with the greater community in aggregate. I also believe that we can extend the existing functionality to help improve upgrade experiences. So there will be continued change to this service to improve our community.


Will Strohl
This is outstanding news for the community. Thank you for your hard work on this feature and announcing it, Mitch!

@Everyone: If you're unsure of how to make this update, the following video should help. :)
Will Strohl Wednesday, May 1, 2019 5:21 PM (link)
Ian Sampson
Excellent news.

Seems like the first critical step towards getting end users, who are not technical, to seamlessly upgrade themselves, much like Wordpress does.

Can you elaborate what module vendors need to do on their end to provide access to upgrade info.

And as a module vendor, are we able to access info about our clients sites?
Ian Sampson Wednesday, May 1, 2019 6:43 PM (link)
Mitchel Sellers
@Ian - As we continue to roll out the new functionality, I will be working to identify the best way to get the information out to vendors regarding adoption/usage of their modules as reported.

I hope to have a follow-up on this in a few weeks as we continue to get more information.
Mitchel Sellers Monday, May 13, 2019 10:11 PM (link)

Comment Form

Only registered users may post comments.


Aderson Oliveira (22)
Alec Whittington (11)
Alessandra Daniels (3)
Alex Shirley (10)
Andrew Hoefling (3)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (37)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Bogdan Litescu (1)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (213)
Chris Paterra (55)
Clint Patterson (108)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (181)
Daniel Valadas (48)
Dave Buckner (2)
David Poindexter (12)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (80)
Francisco Perez Andres (17)
Geoff Barlow (12)
George Alatrash (12)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (274)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Kelly Ford (4)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matt Rutledge (2)
Matthias Schlomann (16)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (40)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Oliver Hine (1)
Patricio F. Salinas (1)
Patrick Ryan (1)
Peter Donker (54)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Sacha Trauwaen (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott Schlesier (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Steven Fisher (1)
Tony Henrich (3)
Torsten Weggen (3)
Tycho de Waard (4)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (180)
William Severance (5)
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out