WSP projects should never need to be compiled - doing so defeats the purpose of that sort of system.
The same goes for the dnn core itself - compiling the core is a flawed concept. There is little to gain in real terms and a lot to loose.
For example the language system fails if the resource files are compiled into a dll and as you have pretty much identified
pretty much all of the dnn core modules are likely to fail in some way.

If you are wanting to build compiled modules then you should use the WAP process and for that - the christoc templates are far
and away the best option to follow.

Hi Wes,

Thanks for the advise. As per your suggestion, I tried working with christoc templates and found them good. Now my Custom modules can be build / compile and I can only move desired DLL's and the control files.

But even though my custom modules would be kind of WAP model, DNN would still be website (WSP) and what I noticed is that there are still .CS files, for e.g. Default.cs file will still be there on the server.

IMHO keeping .cs files is not at all good idea, what if my server gets hacked and the hacker changes the default.cs file to sabotage my website and since it is WSP model, it won't require any compilation and the changes will take place instantly.

My question is that, is there any workaround to this. So that no .CS files should be there on server.

Thanks & best regards,

Ravindra K Jumrani