Forum


HomeHomePremiumPremiumDevelopmentDevelopmentModule developmentModule development
Previous
 
Next
New Post
3/26/2015 4:32 AM
 

Hi Martijn,

There are many ways to skin this cat, but my way would be: Open all files from this project on a simple text editor like NotePad++ and perform a search/replace for "DotNetNuclear.Modules.ViewsTutorial" to the new name you would like to give.

That is my unorthodox way of doing it.

I hope it works for you. Maybe Scott has a different suggestion.

Cheers,

Aderson

 
New Post
3/26/2015 2:41 PM
 
MARTIJN,

I often start my module project by copying another similar project.  Here is a list of things I will change to make sure the new module is unique:

- Rename the project, solution, and .dnn files
- Edit the project properties and change the assembly name and default namespace. Example: "DotNetNuclear.DNN.Module.MyModuleName" and assembly name "DotNetNuclear.MyModuleName"
- Update all existing code classes with the namespace change
- Update the information in the licence.txt and releasenotes.txt
- Update the manifest (.dnn) file with the new module information, ie: package name, basepath and path names, module name, module definition name, etc.
 
Previous
 
Next
HomeHomePremiumPremiumDevelopmentDevelopmentModule developmentModule development



Try FREE
30 days money back guaranteed