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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Auto "upgrades" to .NET 4.0 with each page visitAuto "upgrades" to .NET 4.0 with each page visit
Previous
 
Next
New Post
10/7/2011 2:30 PM
 
Hi,
I had the same problem and at the same time, my site was very slow (~5 sec to load each page).
I just removed all the comments AND the
node (the one after node and the one after )

I really don't know if it is the right thing to do because i really don't know what this "bindingRedirect " node is done for (any idea ?). But maybe it can help to find the solution.

Now my site is ok an pages load very fast ...

Vincent
 
New Post
10/7/2011 2:31 PM
 
Hi,
I had the same problem and at the same time, my site was very slow (~5 sec to load each page).
I just removed all the comments AND the
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" /> node  (the one after <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" /> node and the one  after <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" /> )

I really don't know if it is the right thing to do because i really don't know what this  "bindingRedirect " node is done for (any idea ?). But maybe it can help to find the solution.

Now my site is ok an pages load very fast ...

Vincent
 
New Post
3/28/2012 12:08 AM
 
Hi,
I had the same problem.
In my case, I solved this by upgrading to new dnn version with release.config as new web.config file.
 
New Post
3/28/2012 5:08 PM
 
I have been having this problem ever since adding in the tag into my web.config file in order to allow a child folder to run a .Net application.

I tried the above solution from Quang, but it did not work for me.

I decide to go with option #3, but instead of renaming Net40.config, I opened it up and changed to

Then I created a dupilcate of my web.config file in my root DNN directory and named it "Web.two.config". I removed the tag from that new file (not sure if that was necessary) and then all worked flawlessly.

No more growing web.config file, no more inheritance errors in my child .Net app, no event log errors, and my site was back to running at full speed. Hope this helps the next person.

Still not sure why this is a bug in DNN 6.01.04... shouldn't this be fixed by now?
 
New Post
3/29/2012 9:55 AM
 

Sorry, I realize now that you can't put less than and greater than symbols in your posts... lemme try that again:

I was having the same issue ever since inserting a <location> tag in my web.config file in order to allow a child folder to run a .Net Application.

I tried the solution Quang suggested above, but didn't have any luck.

So I went with option #3 as outlined earlier.  But instead of renaming Net40.config, I edited it and changed:
<nodes configfile="Web.config"> to  <nodes configfile="Web.two.config">

Then I created a duplicate web.config file in my DNN root directory and named it "Web.two.config". I removed the <location> tag from that new file (not sure if that was necessary) and then all worked flawlessly.

No more growing web.config file, no more inheritance errors in my child .Net app, no event log errors, and finally my site was back to running a full speed. Hope this helps the next person.

Still not sure why this is still a bug in DNN 6.01.04.  Shouldn't this be fixed by now?
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Auto "upgrades" to .NET 4.0 with each page visitAuto "upgrades" to .NET 4.0 with each page visit


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