I've already done that and got a module working. But it seems the way I did it and the way that other modules are developed are completly different.

The source I was given was bundled in a Solution and a Project as a class library. Nothing except a reference to the Dotnetnuke.dll was in this solution. So i'm curious how it was developed in this method and more to the point how it was tested/debugged

The way I did it was a create a new module from the source version of DNN and was able to compile the entire solution and then run my code.

Christoc,

That worked great except when I add a module like that it strips out all the .vb source files and I am unable to continue to develop it really. Unless there is another step to take.

I did some research based on an earlier comment and found this:

http://www.adefwebserver.com/DotNetNukeHELP/DNN4_WAP/

Which I believe is how WildPortfolio was developed, However I'm having problems now adding a project from another solution and having it build properly in my dev dnn solution. It builds fine by itself but not in my solution.

Still trying to find my silver bullet method here...