Forum


HomeHomePremiumPremiumDevelopmentDevelopment8/9 DAL2 SPA Module - Unable to Remove FeatureController8/9 DAL2 SPA Module - Unable to Remove FeatureController
Previous
 
Next
New Post
2/13/2018 7:36 AM
 

*Note: I have posted this question on another forum (dnnsoftware.com) but I was hoping to have a better chance at a good answer to post it here as well. I hope that's alright.*

Hello,

I am attempting to play around with the DNN (DotNetNuke) 8/9 DAL2 SPA Module in order to create a React project. I tried deleting and removing any references to C# code that comes standard with the project.

However what I'm finding is that upon removing the following folders the module no longer renders on my sites page and edit mode no longer works on that page until I remove the module.

Folders/files removed:
- Documentation (optional)
- Scripts (no issues)
- Services
- Components
- ItemEdit.js
 (no issues)
- ItemView.js
 (no issues)

To track down exactly what it is that I removed that causes the module and page to no longer function I have removed each item one at a time and recompiled. It appears the only 'required' file is Components\FeatureController. Removing this file causes the issue although there are no errors in the developer console or in the build output to point me to what is happening here.

Quick note I have commented out the line within the .dnn file that references the FeatureController. Everything still works. I can add HTML and javascript just fine and can see test results in Chrome.

My goal being to remove as much as possible from the project until I have a bare-bones module that I can continue working on with React. So my question is what is so important about the FeatureController? Literally, everything within that file has been commented out. I assume at this point that when the module builds certain files (or a certain number of files?) are expected to be present. I can work with keeping this file and moving on. However, I'd like to know why it's required.

Thanks in advance.

 
New Post
3/5/2018 4:42 AM
 

Michael,

There's nothing special about the FeatureController class in the template.  What make it special is if you define that class as your module's <businessControllerClass> in the manifest.  Then it becomes special.  By the way, the name of the class is irrelevant, it is just important that the fully-qualified namespace and class is specified in the businessControllerClass element.

Once you tell DNN what your business controller class is, you then can implement 3 integration points that allow DNN to call into your module.  Those integration points are: search (ModuleSearchBase), import/export (IPortable), and upgrade (IUpgradable).  These are special integration where DNN will call into your module to perform a task.  If you don't need your module to support custom search data, import/export, or custom upgrade/installation tasks, then you don't need to define the businessContollerClass.

 
Previous
 
Next
HomeHomePremiumPremiumDevelopmentDevelopment8/9 DAL2 SPA Module - Unable to Remove FeatureController8/9 DAL2 SPA Module - Unable to Remove FeatureController



Try FREE
30 days money back guaranteed