Create a clean install of DNN

If the source is in a standard DNN install format - try installing it as you would a normal module from inside DNN.
The source files should populate into the appropriate DesktopModules folder etc

Otherwise - you should manually unpack the zip into a FOLDER inside the DesktopModules folder etc.

THEN open the .sln solution.

You will find that most of the references may need to be remapped.

Westa

sorry guys, i'm still having problems. I'm trying 2 different things:

1) installing the module (UDT) through DNN framework, as Michael suggested. then I open the DNN website with Visual Studio and try to modify the UDT code from within /DesktopModules. The problem is, while some files can be modified (like the .ascx's and data providers .vb's), the code-behind files are nowhere in sight. when I add the code behind files (from the source located elsewhere) to /DesktopModules/UserDefinedTable, they are properly grouped with their respective .ascx's; however, modifications to these code-behind files make no changes to the website. Are there Visual Studio settings somewhere that tell the site not to compile already-compiled codebehinds or something like that?

2) i tried unpacking the 'resources' folder into /DesktopModules, and renaming it 'UDT'. The problem is that the directory structure is different from the structure provided when I create a new DNN module from Visual Studio, and I have no idea how to work with this package. if my #1 attempt above can be tweaked to work, that would be preferable. in either case, here is the directory structure of both as i'm seeing it, maybe you could provide some insight.

Visual Studio DNNModule

• App_Code
  • NewModule
    • (data provider and controller .vb's)
• DesktopModules
  • NewModule
    • App_LocalResources
      • .resx's
    • Documentation
    • SqlDataProvider
    • (.ascx's and .vb's)
    • NewModule.dnn

UDT Source

• sql data providers, .dll's, UDT.dnn
• resources.zip
  • App_LocalResources
  • BuildSupport
  • Components
    • data provider and controller .vb's
  • Providers
    • more data providers... why separate?
  • .sln, .ascx's, and .vb's

 if I open the .sln, i get yet another directory structure opened in Visual Studio.  This structure excludes some files, including the code-behinds.  I have to remap a lot, so i'm avoiding this method.