My team is developing a new DotNetNuke web application and would like to know that the development environment with source control setup What is recommended and automated to do? We want to keep separate DNN source code from our custom modules and extensions source code.
The DotNetNuke compiled module template for Visual Studio wants us to store the source code in the desktop module directory of the DN source code and output it to the DNN source code bin directory. Is this the recommended structure? I want to put files in different places, but then it is more difficult to run locally and debug because each change requires modules to be installed. Also, how to organize any change should be an automated build?
How have others installed it? Is there any recommended best practice?
We usually call the module code in the desktop module and the website's Build in the bin directory.
In the source control, we map the individual modules instead of the entire website. Depending on what we are working on, a module can be a complete project in source control, or we may have multiple related modules in the same project, living next to each other.
Arranging changes automatically is somewhat difficult in DNN It is highly recommended that there is a build script that package your module in an installable form. You can copy the reinstallable package into the website's install / module folder, and you can get the URL /Install/Install.aspx?mode=InstallResources , Which will install any package in it folder.
No comments:
Post a Comment