Forum


HomeHomePremiumPremiumDevelopmentDevelopmentModule Folder LayoutModule Folder Layout
Previous
 
Next
New Post
8/11/2014 1:35 PM
 

I've been working on documenting a "standard" layout for modules, this is based on reviewing several modules and the Chris's DAL template. While I understand most any layout would work, and having a "standard" inhibits creativity, I feel having some guidance for structure (that's documented) will enhance the development of DNN modules. This is DAL so far and I'd like to add recommendations for DAL2, Javascript storage, etc, so there's something to work from. If more people follow a standard, then people trying to learn from modules will know where to look for certain functions.

Module Primary Secondary Tertiary CS Filename VB Filename
.build     MSBuild.Community.Tasks.dll
.build     MSBuild.Community.Tasks.targets
App_LocalResources     Edit.ascx.resx
App_LocalResources     Settings.ascx.resx
App_LocalResources     View.ascx.resx
BuildScripts     ModulePackage.targets
BuildScripts     MSBuild.Community.Tasks.Targets
Components     FeatureController.cs FeatureController.vb
Components     Controller.cs
Controller.vb
Components     Info.cs
Info.vb
Data     DataProvider.cs DataProvider.vb
Documentation     Documentation.css
Documentation     Documentation.html
packages     repositories.config
packages MSBuildTasks.1.4.0.74   MSBuildTasks.1.4.0.74.nupkg
packages MSBuildTasks.1.4.0.74 content MSBuild.Community.Tasks.ReadMe.md
packages MSBuildTasks.1.4.0.74 tools Build.proj
packages MSBuildTasks.1.4.0.74 tools Install.ps1
packages MSBuildTasks.1.4.0.74 tools MSBuild.Community.Tasks.dll
packages MSBuildTasks.1.4.0.74 tools MSBuild.Community.Tasks.Targets
packages MSBuildTasks.1.4.0.74 tools MSBuild.Community.Tasks.xml
packages MSBuildTasks.1.4.0.74 tools MSBuild.psm1
Properties     AssemblyInfo.cs AssemblyInfo.vb
Providers DataProviders SqlDataProvider 00.00.01.SqlDataProvider
Providers DataProviders SqlDataProvider SqlDataProvider.cs SqlDataProvider.vb
Providers DataProviders SqlDataProvider Uninstall.SqlDataProvider
Services     RouteMapper.cs RouteMapper.vb
Services     ServicesController.cs ServicesController.vb
      .dnn
      .sln
      .csproj .vbproj
      .csproj.user .vbproj.user
      ModuleBase.cs ModuleBase.vb
      SettingsBase.cs SettingsBase.vb
      Build.proj
      Edit.ascx
      Edit.ascx.cs Edit.ascx.vb
      Edit.ascx.designer.cs Edit.ascx.designer.vb
      License.txt
      module.css
      packages.config
      ReleaseNotes.txt
      Settings.ascx
      Settings.ascx.cs Settings.ascx.designer.vb
      Settings.ascx.designer.cs Settings.ascx.vb
      View.ascx
      View.ascx.cs View.ascx.designer.vb
      View.ascx.designer.cs View.ascx.vb
 
New Post
8/27/2014 4:11 AM
 

Keith,

My template, which I will teaching on this fall, uses the MVP development pattern for modules.  I have some extra folders - Presenters, Models, and Views.  The way I do DAL2 currently is place my "Repository" classes for the DAL2 controllers in the Components folder and the DAL2 entity classes in the Models folder because these are typically used as the model data in our MVP pattern.

When I have done enterprise development where I pull the entire data layer into its own project (class library) to be shared by multiple modules, the module layout changes quite a bit.

 
Previous
 
Next
HomeHomePremiumPremiumDevelopmentDevelopmentModule Folder LayoutModule Folder Layout



Try FREE
30 days money back guaranteed