I am probably making this more difficult than this should be...

I am trying to figure out the best/easiest way to develop a custom module for DNN.

I would like to be able to have the module be in it's own project.
When checking into source safe I do not want to have to check in/out all of the framework, just my module.
I am not sure the compiled module starter kit is the answer.  
I would like to be able to work in either VS 2005 or VS 2008.
I have been through most of the examples no adefwebserver.com, however I could not find anything that is a complete answer for me.   

Any suggestions?  How are others doing it?

Creating the modules within the framework install itself is not what my company wants.  (Using App_Code etc.)

I would like to be able to use the install or the starter kit install to create the framework and install the database, however after that I need to be able to just add a new project, inherit the DNN library and start writing a custom module.  
Sounds easy enough, but I have not found it to be...am I missing something here?

Please help keep me from losing any more hair.

Chas

The only way I have had success doing module development is within the context of a DNN instalation (the complete DNN framework).  Not a source installation, but a regular, compiled installation.

If you can figure out a way to do what you are a describing, I would love to know about it.  But I'm not aware of a way. :-/

  -Josh

Great, thanks for the information.

Last questions on this;  is there a way to utilize the method Brian described and use the Install or the Framework Web Starter Kit instead of the source code version and can that method be used with the file based system in Visual Studio instead of setting up IIS?

Thanks again,

Chas