Install DNN 10.1.2 website to develop custom modules

[kaushalparik27]

I am trying to install DNN website on my local using 10.1.2 Install zip from the Github. I am able to install it successfully on my local. But, I really having pretty hard time in rebuilding website. I receive lot of errors about unknown server tags and other tons of error. I am using VS 2022 and Framework 4.7.2.
Am I using correct file DNN_Platform_10.1.2_Install.zip to install dnn on my local to develop custom module?

[bdukes]

In typical usage, there is no need to "rebuild" the DNN website after it has been installed. What are you trying to accomplish?

[kaushalparik27]

Thanks for quick reply!
Basically, I have a DNN 5.6.1 website and I have few custom modules. I am trying to upgrade my website to 10.1.2. So, I am expecting to rebuild website.

[bdukes]

Generally, you'll want to compile the custom modules separate from the DNN site, rather than recompiling DNN itself. The modules are extensions that DNN loads, rather than changes to DNN itself. Do you have a solution in VS with projects for each module?

[kaushalparik27]

Thanks for reply.
Usually, I create modules in DesktopModules folder itself and then add them as modules from Host » Modules menu.
Is that a correct way of developing custom modules in DNN 10.1.2? If possible and available, can you redirect me to docs or something to understand how can I migrate my existing 5.6.1 modules (Which I had created in DesktopModules folder and used to rebuild/build DNN website itself) to DNN 10.1.2?
Thank you so much.

[valadas]

Well that is fine if it lives on the same site you're are developing on. But if you have scripts, dependencies to deploy, etc. Usually a better approach is to pack it as a package with a proper manifest and such so it can be installed/upgraded on other sites the proper way. You can read some about the manifest here https://docs.dnncommunity.org/content/tutorials/modules/beginning-module-development/wrapping-up/index.html#the-manifest

For packaging there are a lot of ways to do it depending on what you prefer, it could be msbuild scripts, Nuke, Cake, etc. The world is your oyster.

You can find many examples at https://docs.dnncommunity.org/content/tutorials/modules/beginning-module-development/index.html

If you are starting from this old a DNN version, you module is probably webforms, so one of the first things you need to decide is if you just want to invest the minimum amount of work to just make it work, or if you want to modernize it or start fresh... Then we can recommend some solutions more appropriate to what your goal is. DNN is very flexible and there are a lot of ways. Webforms is still supported and having a module just registered without even having a package is still supported, just depends on your goals here.

Is that module something open source? Did you initially build it? What technologies are you familiar with for coding and for build orchestration?

[valadas]

We started publishing NuGet packages from DNN v6 and up, I would suggest you take a local copy of the site and the extensions source code (no need for the DNN source code here). And upgrade the site to 5.6.8 then recompile your extensions and watch for any warnings/errors on using obsolete APIs.

Then you can upgrade the site to 6.2.8 and test.
From that point on, you can reference NuGet packages instead of a hard reference to your site dlls.

Then it would be a rinse and repeat of upgrading one major version at a time, recompiling your solution, checking for obsolete APIs, testing and next major one at a time.

At some major versions, there are special upgrade instructions https://docs.dnncommunity.org/content/getting-started/setup/upgrades/suggested-upgrade-path/index.html