I was playing around with the UDT project module and trying to put a button on the UserDefinedTable.ascx that would fire a Sub in the UserDefinedTable.ascx.vb page (I placed all of the .vb source files on the site) that exports the rendered datagrid data to an Excel file.  Errors galore!!  Of course it couldn't be that easy...  I tried removing the UDT module related dll's from the site to no avail.  Is it possible to use code behind files for everything and not use dll's?  Or I guess another question would be specifically for this module (UDT)?

Inevitably I have several User Defined Table modules on several pages with different fields/types except for one field/type in common with every User Defined Table.  I need to be able to export (I really could care less of the format as long as I can import it into MS Access) every ROW of EVERY module ...  I thought I would just get rid of the ModuleID parameter of the GetTableData() functions but the Function namespaces/classes pulled from the dll's.  So I pulled the source files down and thought I could do it this way and THEN use the code I found posted by Sameer Lal on aspalliance.com to export the datagrid to excel.  One error after another.. It seems as if the dll's are conflicting namespaces and classes between the code behind files (.vb).

The primary question I have is what takes precedence when both the code behind files and the dll files are there for the framework to compile?

I hope I am not making a fool of myself here but I am fairly new to DNN and this is throwing me for a loop...  Or maybe I was loopy already!!

Thanks for any insight!

Mitch

At risk of complicating things. I need to point out that some modules do run without .dll's and use only the code behind files. This is called the WSP (Web Site Projects) model (see: Setting-up the Development Environment for more information).

For example, the new Survey module uses only code behind files. When you install it it removes the old .dll's to prevent namespace conflicts.

If you attempt to develop a module using the WSP model you will want to first convert the module from needing .dll's using DotNetNuke 4.3.5 Module Upgrade Wizard.

Mitch,

please be aware, that thte current version of UDT is  ASP.Net 1.1 verison, developed using VS2003. You need to migrate it to ASP 2.0 in order to make changes, have a look at the upgrade wizard (available from the download page) and the module development guides from Michael Washington.