Forum

This thread may be answered somewhere else, so forgive me and point me to the solution. 

I'm currently using DNN 4.08.04 and doing some module and skin development with the Full Source Code Version of DNN. 

That being so, I've created and tested my new modules and new skins on my local DEV environment and now want to push the entire site to my webhost4life ASP.Net account.

So, I have 2 options:

1 - Copy the entire project in its pre-compiled state to the webhost account
2 - Use VS2005's "Publish Website Feature" to create a Pre-Compiled and Faster Loading/Running Website

Well Option #1 works great, but I'm kind of funny about deploying Source Code to a production site.

Also, it runs so painfully slow without being precompiled.

So in this case I've chosen Option #2.

And herein lies the Problem:

1. When Publish the site and try to invoke it in a browser, I get the following runtime error: "Could not find a part of the Path C:\DotNetNuke\App_GlogalResources\Locales.xml"

2. And sure enough, when I look at my deployed project there is no App_GlobalResources folder. 

3. When I copy it there and invoke the site, I get a message "'App_GlobalResources/' is not allowed because the application is precompiled."

4. So, I start debugging this with VS2005 and set a break point to find out that the App_GlobalResources folder is hardcoded into the Localization.vb module via Line via Line 819 and the static object Localization.ApplicationResourceDirectory

5. See my VS2005 Screen shots.....

http://www.gorudeetours.com/DebugStuff/Local_XML_Not_Found1.png
http://www.gorudeetours.com/DebugStuff/App_GlobalResources_not_allowed1.png
http://www.gorudeetours.com/DebugStuff/App_GlobalResources_not_allowed2.png


Solution?

* I can always hard code around this and deploy the files in App_GlobalResources to another directory, but that sound like hack. 

* Or, I research MSDN on the proper deployment steps for packaging resource files in an ASP.Net precompiled project but I thought that this would have been covered by the DNN Localization Team. However, I can't find anything on DNN about this either...

So, perhaps, I'm missing the obvious.  If, so please enlighten me!

Thank you and Best Regards to All,
Fletcher

• Make a working copy of your site on a local machine, using copies of your database and web directories.
• Install your skins
• Install your modules
• Configure your site
• Move the local working copy of your site back to your production server