DNN Community Blog

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.


ASP.NET 2 Migration Update - Private Assembly Development

Shaun has recently blogged about the progress, we have made in migrating DotNetNuke to ASP.NET 2.

He did however miss out one option for Commercial Developers.  In his blog he refers to the fact the a Commercial Developer, who is concerned about IP would need to use a "separate" web-project, for the UI components together with class libraries for the non-UI components, such as the Controller\Info classes and any providers needed.

\lib
  \DesktopModules
    \Module
      Module.vbproj
      Module.vb
      \bin
        Module.dll

\module_web
  web.config ( with pre-compilation option turned on )
  \app_code
    Module.vb
  \bin
    DotNetNuke.dll
    Module_#hash#.dll
  \DesktopModules
    \Module
      ViewModule.ascx
      ViewModule.ascx.vb
      EditModule.ascx
      EditModule.ascx.vb
      \app_LocalResources
        ViewModule.ascx.resx
        EditModule.ascx.resx     
\web (core web-project)

While this approach is a viable option, it does require a post-build event, to copy the module's web project files to the core project.

One of the advantages of the new ASP.NET 2 model is that each page is compiled into its own assembly.  In addition it is possible to get each sub-folder of App_code to compile into its own assembly.  We can therefore develop our UI components (and some non-UI components in the core web-project itself.

\lib
  \DesktopModules
    \Module
      Module.vbproj
      Module.vb
      \bin
        Module.dll

\web (core web-project)
  web.config ( with pre-compilation option turned on )
  \app_code
    \Module
      Module.vb
  \bin
    Module.dll (from \lib)
  \DesktopModules
    \Module
      ViewModule.ascx
      ViewModule.ascx.vb
      EditModule.ascx
      EditModule.ascx.vb
      \app_LocalResources
        ViewModule.ascx.resx
        EditModule.ascx.resx     

In this scenario, the UI components can be placed where they will eventually reside in production.  Non UI components that do not need to be referenced by external assemblies can live in a subfolder of App_Code, and any Provider classes will need to be in a Class Library, with the Build Directory set to the \web\bin folder.

During development the developer can take advantage of dynamic compilation for all those components that are inside the web-project.  When ready for deployment the developer will "Publish" the Website (ie precompile) and using the  Fixed Names option, will be able to identify the assemblies that represent the Module UI components and the App_Code components.

These assemblies can then be packaged in the same way as we currently do.


Comments

There are currently no comments, be the first to post one.

Comment Form

Only registered users may post comments.

NewsArchives


Aderson Oliveira (15)
Alec Whittington (11)
Alex Shirley (10)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (32)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Bogdan Litescu (1)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (209)
Chris Paterra (55)
Clinton Patterson (41)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (154)
Dave Buckner (2)
David Poindexter (4)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (74)
Geoff Barlow (10)
George Alatrash (6)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (274)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matthias Schlomann (15)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (28)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Peter Donker (54)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott S (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Timo Breumelhof (24)
Tony Henrich (3)
Torsten Weggen (2)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (165)
William Severance (5)

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out