The goal is to provide a web-based tool to rapidly develop and distribute DotNetNuke modules
At the moment there are 2 ways of configuration editing.
- navigate to the module page and click Edit XSLT
- use XsltDb Rich Client.
I believe that building a configuration tree and providing explorer-like configuration navigation would bring XsltDb development process to the next level. And it also solves the problem when a bug in ASP.NET control properties kill module menu and you can
correct your XSLT only using XsltDb Rich Editor.
Package Builder, Versioning And Automatic Upgrade
If I developed a module using XsltDb I can't distribute it as the only way to install it on destination DotNetNuke host is
copy & paste
. I plan to create a packager that will support building an
XsltDb Redistributable Solution
- XRS. XRS will provide:
- Packager. The goal of packager is to put all configurations, SQL scripts, pages of solution in single archive and provide one click installation and upgrade.
- Version management.
- Database upgrade (per-version scripts).
You need more? Just write a comment below!