can you please tell me about your development environment? specifically what version of DNN? and what version of Visual Studio? or VWD? If you are running a DNN 4.X site, then you can't install the source version. The Repository module was (and continues to be) developed in VS 2003. The reason for this is that if I develop the Repository module as a DNN 3.X (.net 1.1) module, then the resulting compiled module can be installed on any 3.X AND 4.X DN installation. If I convert the Repository source code to .net 2.0 and develop using VS 2005, then the resulting compiled module can ONLY by run on a DNN 4.X installation, effectively reducing the number of users who can install and use the module.
Understanding that, if you are running a DNN 4.X environment and install the source version of the Repository, then the source files (because they will be located in the web site folder structure ) will be automatically included when you attempt to run the web site. The dynamic compilation of .net 2.0 will cause the Repository source files to be re-compiled at runtime, and since they are written against the .net 1.1. framework will not compile successfully throwing all kinds of errors.
If you intend to re-compile or modify the source code of the Repository module, then you MUST do so in a DNN 3.X / VS 2003 development environment. Once debugged and running, you can create a new installation package ( using the included .build NANT file is the easiest way ) and then install the updated package on your DNN 4.X environment. I'm sorry if that was not clearly stated.
thanks, and I hope that you understand my hesitancy to convert the Repository over to a .net 2.0 module at this time, until a much larger percentage of DNN users migrate to the newer .net version.
I do plan to provide a native 2.0 verison of the module at some point, but that will be a total rewrite to take full advantage of the .net 2.0 (or by that time more likely .net 3.0) framework.