Page view counter

Converting existing ASP.NET Application to DotNetNuke- what is the best practice?

Last post 01-06-2006 1:16 AM by MNF. 2 replies.

Sort Posts:

  • Converting existing ASP.NET Application to DotNetNuke- what is the best practice?

    11-17-2005, 8:25 PM
    • Loading...
    • MNF
    • Joined on 07-24-2005, 8:15 PM
    • Posts 71
    • Points 257

    I have an existing ASP.NET 1.1 Application that includes more than hundred different ASPX pages and user controls (ASCX). The application consists of a number search forms, results lists and data details forms to view and edit database data.

    I am considering converting the application to DotNetNuke.

     

    I am looking for information what is the best approach for converting.

    Should I make all my User Controls be derived from Modules.PortalModuleBase or I can use Dynamic Load User Controls Module ?

    Should I locate all my DNN User Control in one folder under DNN\DesktopModules or it’s better to create a few separate Modules?

    Is it allowed to have User Controls in sub-folders of MyModule folder or it is recommended to have all of them in the root of the module?

     

     

    Any info how to simplify the process and references how similar conversions were done would be appreciated.  

    Regards,

    Michael Freidgeim
    Blog: http://geekswithblogs.net/mnf/

  • Re: Converting existing ASP.NET Application to DotNetNuke- what is the best practice?

    11-18-2005, 7:34 AM
    • Loading...
    • nokiko
    • Joined on 10-22-2002, 2:36 PM
    • Utrecht, Netherlands
    • Posts 2,146
    • Points 10,740

    Well you just need to think why you want to convert it over to dnn. Is this becayse you want it to use/show in a dnn environment or if you want to use all the editing etc capabillities of dnn.

    If you just wantto show the data etc in a dnn environment I suggest looking at the open smartmodule from xepient.com.

    With this you can run normal usercontrols in dnn environment instead of rebuildingeverything to behave the dnn way.

    http://www.knipselkrant.nl/Politiek/tabid/102/hmod/menu/uid/28636/pn/Politieke%20partijen/pr/598384/default.aspx

    Here I have build all the controls as normal ser controls and just loaded them into dnn, so i have the show/noshow/edit security of dnn and i dont ahve to cnvert over all the excisitg aspp. Just det a fewproperties that are exposed to the smart module  using reflection and you are off,saves abundle of time

    Armand Datema
    5 Skins, 4 SkinObject, 38 Containers, 2 Modules and more Euro 50 a year.
    SchwingNuke
    Offshore DNN and ASP.net development
    Container Creator
  • Re: Converting existing ASP.NET Application to DotNetNuke- what is the best practice?

    01-06-2006, 1:16 AM
    • Loading...
    • MNF
    • Joined on 07-24-2005, 8:15 PM
    • Posts 71
    • Points 257
Page 1 of 1 (3 items)