Is there an existing issue for this?
Description of problem
We have sample projects such as https://github.com/dnnsoftware/Dnn.Platform.Samples.Mvc that are meant to show developers how to develop extensions for DNN. It has proved to be impossible to keep this in step with the developments in DNN. Given that we intend to bring some major improvements to DNN that will impact modules, it is not ideal that these demo projects are separate from the main project. I.e. if one changes the platform in a way that requires module to make adjustments, these modules should serve as validation for that.
Description of solution
I propose to include a set of representative (i.e. covering the various module patterns) modules in the main repository that serve both to demonstrate good practice and secondly to test the latest version of DNN. As a bonus changes to the API that would risk breaking modules, would immediately provoke a build error of the entire project in this way.
Description of alternatives considered
No response
Anything else?
No response
Do you plan to contribute code for this enhancement?
Would you be interested in sponsoring this enhancement?
Code of Conduct
Is there an existing issue for this?
Description of problem
We have sample projects such as https://github.com/dnnsoftware/Dnn.Platform.Samples.Mvc that are meant to show developers how to develop extensions for DNN. It has proved to be impossible to keep this in step with the developments in DNN. Given that we intend to bring some major improvements to DNN that will impact modules, it is not ideal that these demo projects are separate from the main project. I.e. if one changes the platform in a way that requires module to make adjustments, these modules should serve as validation for that.
Description of solution
I propose to include a set of representative (i.e. covering the various module patterns) modules in the main repository that serve both to demonstrate good practice and secondly to test the latest version of DNN. As a bonus changes to the API that would risk breaking modules, would immediately provoke a build error of the entire project in this way.
Description of alternatives considered
No response
Anything else?
No response
Do you plan to contribute code for this enhancement?
Would you be interested in sponsoring this enhancement?
Code of Conduct