how do you test the DNN manifest before releasing a new version of your modules?
The easiest way to do this right now - beyond testing the installation directly on a test site - is to use the Extension Validation Service (EVS). It hasn't been completely maintained in recent years, so there are a handful of false positives/negatives that you might come across, but you should be able to figure those out after a handful of uses. :)
In the more extreme/complicated use cases, you may want to instead find a DNN agency to help you.
Will is right, the EVS is a good starting point. Anyway, I would always setup a clean test instance and try to install and upgrade the extension. Sometimes, the EVS produces an error and when you fix it and the EVS says that everything is good then the package does not install, but with the "error" it works fine. E.g. EVS reports error, but when correcting it the package does not install · Issue #5375 · dnnsoftware/Dnn.Platform (github.com) - and I don't understand why this issue is closed... :-(
Thanks for the hints guys!
I was hoping to find something similar to a RegEx editor&debugger like https://regex101.com
If you just want to check the XML syntax (if it's well-formed) you can use XmlNotepad (microsoft.github.io) - very useful.
I don't think there is something that checks the correct DNN manifest syntax.
A bit weird :-D
I prefer to use Visual Studio instead, or Visual Studio Code with its plugins.
Exactly, what I'm looking for is something to test the manifest instructions: add, remove, etc...
These Forums are dedicated to the discussion of DNN Platform.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.