When you say "published" code, do you mean that you used Visual Studio's Build -> Publish command to "publish" the DNN website project? If that is the case, it is not possible to compile or publish the website code as it is and needs to remain a website project (WSP), not a website application project (WAP). It is only possible to compile various components of DNN such as the DotNetNuke library, providers, modules which have been developed as web application projects, etc.

All files (including *.ascx.cs) of the website itself should be copied not published to the server on which the site will be hosted.

One of the problems with attempting to compile the DNN website project is that DNN's static localization will break as you found with the missing texts.

Also, are you trying to use the DNN source rather than install package? If so, note that you should use the install package unless you are planning to modify the DNN platform code itself which is not recommended. It is not necessary to use the source package for module or skin development.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner