Last post Dec 20, 2005 05:02 AM by rodneyjoyce
Dec 09, 2005 11:20 PM|johnebailey|LINK
I just read Shaun's excellent article on developing modules for DNN 4.x using the provided starter kit. It is an excellent guide to distributing any web user controls separate from the web application in ASP .Net 2.0.
Unfortunately the article did not describe how to package your business rules and data provider in separate assemblies.
I have a need to distribute my data provider and business logic in separate assemblies as I am using the same assemblies in another web application and do not wish to maintain two versions. Is this as simple as adding a reference to my DNN project and pre-compiling
everything else as usual or is there more involved? My provider is coded as a typical ASP .Net 2.0 provider.
Dec 19, 2005 09:54 PM|BKdotNet|LINK
No reply yet, eh?
Well never fear... The answer is to create a separate class library assembly for your module. Works great, it's less filling... and is great for encapsulation.
The alternative is to do a precompile - but if you're like me, and enjoyed the project separatist movement, and having finite control over your assembly deliverable... create that separate library. Your front-end ASCX will simply reference a different namespace
(like it did with ASP.NET 1.1) and ASP.NET will do the rest as it always has.
Dec 20, 2005 05:02 AM|rodneyjoyce|LINK