Ok..  I could be wrong but this is what I found:

 

1. The code behind files for the core modules are no longer available within any package (Source, Install or starter kit).
2.  We will need to download each module project separately if we wish to do so, which is understandable.

 

I looked at DNN 4.0.3 documentations and I couldn’t find any thing that talks about this. I’m trying to re-organize my thoughts in order to start developing my custom modules and I would like to know If I should follow the same approach the DNN 4.0.3 is using and create my modules in a completely separate projects and just copy the dll and ascx files into DNN bin and desktopmodules directory that is created during the installation stage.  I would appreciate it if someone can think or provide a best practice approach, if any?

 

 

This is correct. The reason core module code-behind isn't included in the releases is because it is .NET 1.1 code, not .NET 2.0. Having this code-behind in the directory can cause errors if the run-time compiler gets a hold of it. So, to avoid that, the code is not included.

As long as you're developing with .NET 2.0, there is no problem developing custom modules as you did before.

---

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com

Are you saying 4.x uses .net 2.0 but if you want to make changes to core you have to go use vs2003/.net 1.1 and compile there?