Learn More





DNN Community Blog

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.

Extension Verification Service (EVS)

Recently, I've been able to divert from my normal Store activities and work on a project that I feel will have a big impact on the platform, community, Store and the overall DNN ecosystem. This project is the Extension Verification Service (EVS). EVS attempts to simplify the extension development and testing process by automating some of the initial compatibility checks. Currently EVS conducts this compatibility checking by focusing on three key areas which include the package manifest, SQL scripts and assemblies.

First, EVS checks the extension to ensure that it is complete and well-formed. This process first extracts the extension then checks for the existence of a .dnn manifest file. Once it finds the manifest file, it will then check that file for completeness and correct form. If optional sections are missing, it will issue a warning for each one. If required sections are missing, it will issue an error message for each missing section. Over the next few weeks we also plan to add support for the legacy manifest used before version 5. We also plan to add a two-way file check that ensures that every file listed in the manifest is included in the extension package and conversely that every file in the package is accounted for in the manifest. I know there have been times in the past that I've included a new file in an install package and neglected to add it to the manifest file. Another item that we would like to add in the near future is the ability to link the most common errors reported by EVS to respective areas in the wiki to help quickly inform users what can be done to correct the issues.

The second area that EVS will check for compatibility is the data layer. If the extension has SQL scripts, it will scan and parse the SQL looking for primarily for SQL Azure compatibility issues. With the push to make DNN SQL Azure compatible, there have been some issues raised by early adopters of DNN on the Azure platform. Many third-party extensions and even some of the core extensions have had issues with the SQL scripts that keep them from installing correctly on SQL Azure. In an attempt to make SQL server scale better in a cloud environment, Microsoft has removed some functionality from the typical SQL server feature set when they developed the SQL Azure platform. Many of these differences are difficult to identify. There is already a project in CodePlex ( that attempts to ease the process of moving from SQL server to SQL Azure. We used this project as a basis for our SQL scanner with a few extra methods on top to help track the changes and to handle locating the scripts in the extension. Over the next few weeks, we also plan on expanding the functionality of the SQL scanner by returning a zip file which contains the SQL Azure compatible versions of the scripts found in the extensions. Another check that we would like to add to this area of EVS in the future is a check that ensures the proper usage of {databaseOwner} and {objectQualifier}. We would also like to add a function that will check to ensure that the uninstall script will correctly remove all of the objects added by the installation scripts.

The third area the EVS will check for compatibility is the assemblies. If the extension has assemblies, it will scan them looking for potential assembly reference errors, and to determine based on assembly references the minimum required DotNetNuke version and the minimum required .Net version. This part of the system relies on reflection to examine the references of each assembly included in the extension. That list of references and versions are then compared against a known list of .Net and DotNetNuke assemblies for each version of the respective platforms the system can then determine from that the minimum required version of both the .Net and DotNetNuke platform needed for the extension to run correctly. Over the next few weeks we will expand upon this functionality to also track each reference to ensure that they are either included in the .Net GAC, DotNetNuke or are included in the extension. If not we will then return an error to alert the user to a potential assembly reference error.

With all the functionality already included in EVS and the functionality that is already planned to be added over the next few weeks EVS will be a useful tool to help developers and users to evaluate the compatibility of extensions. However, it's important to note that this is not a certification system. Just because an extension doesn’t return errors from the EVS system, there is no guarantee that the extension will be problem free. EVS is also not a replacement for proper testing and traditional safeguards like performing a back-up when installing new extensions. The purpose of the current beta test is for people who have recently experienced compatibility issues to submit the extensions in question and see if EVS is able to identify the potential issue. If issues have been identified, it would be very helpful to bring those to our attention so that we can see if there is a way for EVS to automate the detection of that issue in the future.

Hopefully you will find this utility to be useful and I welcome any feedback regarding EVS. Feedback can be left via the forum located at and the EVS site is located at


Comment Form

Only registered users may post comments.


2sic Daniel Mettler (124)
Aderson Oliveira (15)
Alec Whittington (11)
Alex Shirley (10)
Andrew Nurse (30)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (21)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (203)
Chris Paterra (55)
Clinton Patterson (28)
Cuong Dang (21)
Daniel Bartholomew (2)
Dave Buckner (2)
David Poindexter (3)
David Rodriguez (2)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (74)
Geoff Barlow (6)
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 (269)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matthias Schlomann (15)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Mike Horton (19)
Mitchel Sellers (28)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Peter Donker (52)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott S (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)
Timo Breumelhof (24)
Tony Henrich (3)
Torsten Weggen (2)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (37)
Will Strohl (163)
William Severance (5)
Try Evoq
For Free
Start Free Trial
a Demo
See Evoq Live
Need More Information?