The basic process for compiling the source version of a module will be something like this:

1) Download the source version from the project subsite (obviously :) )
2) Unzip the source files somewhere on your hard drive. IIRC, you will need to unzip the resources.zip file, because that's the one that contains the source files. One of these files will be a .vbproj file.
3) Open VS2005, and load this project. Ensure that the companion source files (.vb, .ascx) are also loaded.
4) Compile the project, correct reference errors (see below).

The "second" attempt you described above sounds like it's the closest to working. When you load a project for the first time, it will likely have some bad references that you will need to manually add. This is why you are getting errors about the "security module" -- its reference is not currently in your project.

To correct, click on "My Project", then on the References tab. Add the missing references.

What are the missing references? Well, dotnetnuke.dll is always needed. Other than that, you will need to look at the error list and determine what assembly the missing classes are located in. The object viewer (ctrl-alt-j) is invaluable in performing this task. Say I was missing the class "DNNToolbar". I'd open the object browser, search for DNNToolbar, and see that it was located in the "DotNetNuke.Webcontrols" assembly. I'd add a reference to this assembly to my project, and the compiler would be able to find it.

Hope this helps!

Brandon

---

Brandon Haynes
BrandonHaynes.org

Hi Brandon,
It seems that I am missing Framework.Providers.Provider and .ProviderConfiguration

I will Google to see what I find.