This is not so much a criticism as much as my education. I re-introducing myself to DNN and recently downloaded 4.3.6. In comparing the Install Package to the Source Package (as I may create a setup project for deployment), I noticed all the folders under Admin and AppCode in the Install package had their VB files there. I tried deleted them before testing (as I never deploy ASP.Net apps with VB files) and it would not install.

I guess I am curious why the class files could not have been compiled into DLLs instead of deploying the VB files (or could they be compiled)?

Thanks,

Ken

in ASP.Net, the code behind files get compiled on runtime (and cached).

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

There are 2 ways to deploy .Net 2.0 applications

1) Xcopy: This includes all the files including the source files and DNN compiles pages/code as it is accessed (Dynamic  Compile)

2) Precompiled:  You can also choose to Deploy a web site from within VS and this pre-compiles are the code into another directory and then you can use Xcopy to copy these files to the web server instead.  In this case no source is installed on the server.  When you deploy this way you also have the option of compiling the aspx pages as well, but then they would not be editable (cannot fix markup issues without recompiling and redeploying.  Also, it you want to deploy this way make sure there are not modules installed, since the Deploy process compiles everything under the web site directory.  It is just cleaner install that way, and once copied to server you can then install the modules you want to.