How to set up DotNetNuke for development

Question

I am part of the .NET development team and we are trying to use the DNN platform as a way to create a website template, so we don’t have to spend weeks or months creating basic functions such as authentication, permissions, navigation, etc. However, I am very confused about how the platform works and how it is installed. I spent many hours researching online at http://www.dnnsoftware.com/ , as well as other sites that just added to my confusion. Here are some specific questions that still remain unanswered:

• Are we installing the source code or not? http://www.dnnsoftware.com/wiki/how-to-install-the-source-package-of-dotnetnuke says it is not recommended to install the source code. On the other hand, http://www.dnnsoftware.com/wiki/packages says that we should use the source code if we are developers (which we are).
• If we do not use the source code, how will we write the code that will be used to add functionality, style or business logic to our website? Where exactly do we put this code?
• I continue to consider the term "module." What is the module in the world? Is this a separate .csproj file? Is this a .cs file saved as part of the website? If so, how can we enable it without source code?
• Like any other application, we must be able to maintain full control over assemblies and deployments. With this, we can see the history of what we have done, discard changes, if necessary, etc. For our other projects, we are currently creating TeamCity and deploying it with OctopusDeploy. Where is this suitable for working with DNN without source? I also know that DNN is configured as a website project, not a web application project (see here http://www.dnnsoftware.com/forums/threadid/338902/scope/posts/threadpage/1 ), and projects Web Sites - This technology is not supported by modern versions of Visual Studio and can be more difficult to deploy. Assuming I DO NOT want to convert ( http://blogs.msdn.com/b/webdev/archive/2009/10/29/converting-a-web-site-project-to-a-web-application-project. aspx ), how do I create / deploy a website project?
• http://blogs.msdn.com/b/webdev/archive/2009/10/29/converting-a-web-site-project-to-a-web-application-project.aspx does not seem to state that It is recommended that you remove dependencies from DNN and replace them with others. If this is true, then the whole platform looks very fragile and makes me wonder if I am using the wrong tool at all. Was DNN really designed for developers or not? (And if not, then what was it intended to use?)

Answer 1

Start here →

http://www.christoc.com/Tutorials/All-Tutorials/aid/1

1) Do not touch the source of DNN, believe me, this is not worth the headache.

2) You add functionality, override style, etc. using the extension (modules and skins)

3) Separate CSProj (check out my templates http://www.christoc.com/Tutorials/All-Tutorials/aid/2

4). You will expand by taking a ZIP file from each extension and either downloading it through the host / extension page, or taking the ZIp file and pasting it into / install / module / at the root of your deployment target, calling the /install/install.aspx?mode=installresources process

5) DNN, of course, is intended for developers, but this is a framework based on the structure, do not enter or start the frame itself.

Answer 2

I would start by starting the DNN site on your site. This is true for any .NET developer.

The module is an extension for the DNN infrastructure, which can essentially (after proper installation) be dropped to the DNN page (called the tab). All your business logic will go into your own modules, and the code for these modules will be the only thing you will have to manage the source code. Do not make major changes to DNN, as they will be deleted if you are ever updated.

You do not need to use the Christoc module template if your module only needs to be deployed. I find that it contains a lot of unnecessary components and links that you probably won't need. Build your module using webUserControls, which inherit from DotNetNuke.Entities.Modules.PortalModuleBase. Drop the .ascx file into your folder in the DNN folder of DesktopModules and all the necessary DLL files in the DNN bin folder. In DNN, go to Host> Extensions and create a new extension. Add a module control to the extension and add your ascx files as controls (leave the blank key empty by default). Other views must have unique keys, and you can navigate to them in DNN using EditUrl ("KeyName").

Drop your module on the DNN page and go from there.

This, of course, is a simpler simplification, but it should make you go. There are many tutorials on the Internet in which I advise you to learn the basics, such as Globals.NavigateUrl (), to navigate between tabs and how to combine DNNs. This forum topic can help you http://www.dnnsoftware.com/answers/dnn-7-module-development-step-by-step-tutorial