Last post Mar 06, 2006 01:03 PM by DarrylB
Mar 02, 2006 07:27 AM|DarrylB|LINK
Mar 02, 2006 11:15 AMemail@example.com|LINK
Technically, you don't need most of that stuff, but the idea is to present a layered programming model so that you can separate presentation logic from business logic from data provider logic (and plug in multiple data providers if you need to later). That's
just a pretty common design philosophy nowadays and not specific to DNN. ExecuteReader() returns an IDataReader interface which is essentially a recordset coming from a .NET data reader. The FillCollection() method consumes IDataReader data-sets and takes
the object type as an argument. By "reflection" it consults the meta-data of the IDataReader and the type you pass in and dynamically builds a collection of your object. In your case, it builds an ArrayList of ConferencePhoneExtInfo objects.
ModuleId is not required, but a lot modules allow for multiple instances of the same module to be installed on a portal. If you pass the ModuleId in, then you can distinguish which module is calling you T-SQL stored procedure.
The famous "Seabury" videos on the DNN site demonstrate some of these questions in the form of training. They are pretty good. You should check them out.
Mar 02, 2006 11:28 AM|adefwebserver|LINK
Mar 05, 2006 02:01 PM|DarrylB|LINK
Mar 06, 2006 12:02 PM|brian_c|LINK
the easiest is to look at any of the core modules ..
or any modules you might have purchased..
or any modules from the various website examples, templates, etc..
Mar 06, 2006 01:03 PM|DarrylB|LINK