Consider a companion module with a web api, listing available packges.

[dazinator]

The tab on extensions page in dnn that shows modules on the dnnstore is nice, but it only works with the public store.

What about small teams that develop highly bespoke, internal modules. They typically do not and should not be published to the dnn store. The usual route is that the team manually installs the module on dev, uat, production system as required. To enable a smoother workflow for this could:

1. Create a companion module for dnnpackager that has a webapi and can be installed into a dnn site.
2. Add a publish command to dnnpackager so a developer from within VS (or the CI build server) can publish the install zip to the companion Dnn module.

The companion module then should behave like the available extensions tab, showing the newly available zip with an install option.

Could start to add some interesting features around this companion module.. like the ability to "promote" a module from one dnn instance to the next (i.e dev --> test --> live)

Big project though, will leave this as one to think about after the dnn project system is out the door.

[dazinator]

Closing as this would be a seperate project