You really don't need to go through this to get DNN running, and you certainly don't need to "compile" anything.

Installing DNN is an absolute snap if you use nvQuickSite (https://github.com/nvisionative/nvQuickSite). It does absolutely everthing to get a DNN install up and running.

Thanks for the reply Joe, the install of DNN 9.4.1 is working fine.

The issue with the site I am building arises when I use the "precompile during publishing" setting in VS2017 to hide the .cs files. I upload the site and it works on initial load however sometime later when the site is refreshed it will show a 500 internal server error.

The error log shows "No service for type 'DotNetNuke.UI.Modules.IModuleControlPipeline' has been registered."

When the precompile setting is unchecked in VS2017 the error message is no longer an issue and the site functions properly but with the .cs files present.

The targetting framework is .NET Framework 4.7.2.

 

Like I said, but not very well, you should not be installing DNN this way. As a minimum, you shouldn't use the "precompile during publishing" option. If you are using the Install package or an Upgrade package, nothing needs to be compiled.

It is normal for some .cs files to be present. Which ones concern you?

We have a few custom modules on the site and our App_Code folder contains some .cs files that we'd like to sit on the server as one .dll file to make it more secure.

You should set your custom modules up as compiled modules, compile them outside of DNN, create installation packages that don't include the cs files, and install them like other modules.

Take a look at Chris Hammonds module development templates to see how this is done (the scaffolding is there to create both "install" and "source" packages.

Thanks for the guidance on the custom modules Joe.

From doing some reading it appears the best way to get the App Code converted into one .dll file is using the precompile during publishing option in VS. If we execute this it will throw that No service for type 'DotNetNuke.UI.Modules.IModuleControlPipeline error for which there seems to be no known fix. Would you know if there is a different way to try and compile the App Code folder to a single .dll file?

I'm afraid that I don't have an answer for you other than to repeat my suggestion that you convert this into a compile module. That really is the standard way to do things.

Using one of the common module templates will create a new C# project for you, and compile all of your code into a DLL.  You won't be using the <code>App_Code</code> folder anymore. Here are some module template options:

• Chris Hammond's Visual Studio templates
• Matt Rutledge's <code>generator-dnn</code>
• David Poindexter's <code>starter-module-web-forms</code>

Richard - Could you please share how did you resolve the issue. I am experiencing the same issue as you.