I am trying to amend the Documents module source code but my changes to the VB are not building.

My amendments in the ascx and localisation files are working fine, but if I amend a code behind file then I can't seem to effect the output, its as if it is not compiling to the Documents.dll file. I also tried deleting the Documents.dll file also, then when i rebuilt it just gave errors saying that dll didin't exist. So somehow I don't think i have my environment set up right as it is not rebuilding properly.

I am using latest version 4.4.1 install version of DNN with the latest Document Module Source file. First I installed and deleted the Document Install module that was prepackaged with the DNN install, then I installed the Document Source download so that I have all the VB files.

I believe this is a result of the fact that the Documents module is project based and was created under VS2003 for ASP.NET 1.1, which will work in ASP.NET 2.0. In order to compile and debug in VS2005 using the website senerio, not project based; the module will need to following the rules for creating a new module as laid out by the core when DNN 4x first came out.

I recently went through this process with a third party module that I purchased with source. After converting it to VS2005 and ASP.NET 2.0 and running in DNN 4.3.7, I at least got it to debug. 

This could best be answered by one of the project teams that have convered an existing module. Surveys come to mind.

Note: If the project model had been out when the conversion of DNN from 3 to 4 took place, well you get the picture.

 

---

Thanx

L Douglas

Hi,

Were you able to find a solution to this? I am getting the exact same problem, I'm using Visual Web Developer Express, which doesn't let you compile dll's so I must use dynamic compilation, which doesn't seem to happen with Documents Module.

Any advice would be great.

Nick