Hello Lee and others,

I had a question concerning the components of a module.  We had someone else get our website up and running with dotnetnuke and created a module that would allow someone to interact with a table in the database via csv or txt upload.

I have the task of implementing this same concept that was done via this upload module for a different table in order to allow someone to work directly in the database and than populate the table via csv or txt file over-riding the table or tables that already existed with the new data opposed to updating it via the front end and adding one event at a time.

Now I am trying to figure out this upload module and see how it was built to run trying to find out what table and fields the module is affecting when the person on the front end clicks update.  However I am having a hard time figuring this out.

I found some files in the desktopmodule/update folder which consisted of some ascx, ascx.vb, and some resx files.  Only one file seemed to be even remotely close to giving me the behind the scenes look at what was happening int he background when someone clicked on this upload button which was part of this update module.

I guess my question is once the module is installed in dotnetnuke is it possible to find out everything that module was programmed to do or do some files somehow get compiled upon installation of a module when the zip file was installed in dotnetnuke.

What files and where would those files be that point to the engineering behind a given module in order to customize it to perform in a slightly different manner.  Thanks

Bo

Hello Lee,

two questions would the source code of a module be one of the files contained in the installation zip file used to install the module in dotnetnuke

Also what extension does the source code usually have (i.e. vb, java, c# extension, C++ extension, etc...)

Is the dll file in the bin directory that relates to the module basically the cimpiled version such as a .class file is the compilation of a .java uncompiled program thanks for your help

I quess what I am trying to get at is you say that if their is no dll in the bin than their is no way of getting into the inner workings of a module.  Doesn't the inner workings of any given module reside somewhere since someone initally had to create it some time down the line.  So why would some modules contain a .dll file with the capability to pull up the source and others would not?  If could help me understand this that would be great

And lastly if I create my own dnn module when installed would it produce a dll file in the bin directory or in some cases would it not.  Why would some modules do this and some not again thanks I have sort of been handed this web project that in already in dotnetnuke so am trying to learn a little bit about how this module stuff all works and how they are put together for the purpose of possible customizability of the inner workings of any given module.

Bo

regarding the last part of the comment concerning the fact that if I don't have a dll file in the bin directory I don't have much hope of getting into the inner workings of the module what then are these ascx.vb files I see on some of the modules in the destopmodules folder are they not source code for the particular module that is inside the folder weather it be banner aggregator, ecard, etc... if not what really is the purpose of ascx.vb, ascx, and resx files that are located in some of these sub folders of a particular module folder in the desktopmodule directory thanks

Bo