Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsLanguage PacksLanguage PacksApp_GlobalResources causes problems when precompiling site in DNN 4.03App_GlobalResources causes problems when precompiling site in DNN 4.03
Previous
 
Next
New Post
11/30/2006 1:38 PM
 
Bertcord wrote

When recompiling a DotNetNuke using version 4.0.3 the App_GlobalResources directory is removed and all files are compiled into an assembly.  This causes issues for DotNetNuke localization. It is not possible to copy this directory to a precompiled site as you will get the following error.

The directory '/DotNetNuke/App_GlobalResources/' is not allowed because the application is precompiled.

3 solutions I see for this ….

  1. Rename App_GlobalResources directory to AppGlobalResources.  Change line 62 in Localization.vb to

Public Const ApplicationResourceDirectory As String = "~/AppGlobalResources"

I have done this on my local machine for now and it appears to work ok

  1. Rename App_GlobalResources directory to App_localRespource. This directory is not precompiled if site is set to be updateable.  This might not be ideal if site is to be compiled with no update option.
  1. Change logic engine to pull resources from DLL.  Probably not ideal as two code bases would need to be maintained

Any thoughts?

Bert

 

 

Has this original problem been solved in the Nov release? This was a real problem. I have had to just upload the entire site to get around this issue.


Thanks

Harold

 

 
New Post
11/30/2006 2:11 PM
 
ErikVB wrote

It was done, but it turned out the change would cause issues with modules using constant values which contained references to the directory. Constant values are changed into static strings in the vb.net compiler, so modules would point to the wrong directory. Untill we find a better way to solve this, it was reverted to the old situation....

the answer i gave earlier still applies


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
11/30/2006 7:45 PM
 
So is uploading the entire site an appropriate solution or is there some compiled version that can be transferred to the server without running into this problem?

Thanks
Harold
 
New Post
12/7/2006 1:47 PM
 

Hi Erik!

Sometimes it is all in your mindset and prioritization done by top leadership.  In other words, shifting from I CANT to I CAN DO! and carefully evaluating "nice to haves from show stopper bugs".

Here is a tangible example of what I mean, rather than say "Untill we find a better way to solve this, it was reverted to the old situation"

Have Shaun make an top level executive decision to be more "CAN DO" and say this kind of thing here at this location.

We (the DotNetNuke team) strongly believes in supporting professional development and using ROADMAP SOFTWARE PLANNING and will for sure address this problem in DNN version ?.?.?.  We have Shauns word that he had not left professional developers out in the COLD!

Sometimes we all know the solution is hard.  Especially with great software like you guys produce.  Perhaps this problem is very hard to fix.  I do not personally know.  But if Shaun acts as a priority setting manager and sees this is TRUELY A SHOW STOPPER TO PROFESSINAL DEVELOPMENT then he will point your DotNetNuke team at a specific DotNetNuke release in the future and give his word / promise to the public the problem will be fixed in the DNN PLANNED ROADMAP future version of DotNetNuke.


Kevin Donahoe CEO, Architect, and .Net Developer http://www.NewTechnologyAdvantage.com
 
New Post
2/24/2007 9:24 AM
 
Have to bump this up because I'm runnin into the same issue with 4.4.1. Has there been a viable solution for this? It looks like this bug was discovered a while ago and I'm hoping that it has been resolved.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsLanguage PacksLanguage PacksApp_GlobalResources causes problems when precompiling site in DNN 4.03App_GlobalResources causes problems when precompiling site in DNN 4.03


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out