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 ...Note: You are running on an old version of the .NET Framework.Note: You are running on an old version of the .NET Framework.
Previous
 
Next
New Post
8/23/2010 11:29 AM
 
I am now getting this message when I go to host settings:
"Note: You are running on an old version of the .NET Framework. Future upgrades of the DotNetNuke platform will require .NET 3.5 SP1 or later. If you believe you are running .NET 3.5 SP1 already, please check your web.config file and ensure that the 3.5 or above versions of both System.Core and System.Data.Linq are referenced in the assemblies node"

I am running .NET 3.5 SP1.  And, I did this upgrade in the same environments at the beginning of last week and I did not get this message, but now I am.  What could have changed to cause this message to start showing up?

Judy
 
New Post
8/23/2010 2:56 PM
 
What was the upgrade path?
Do you happen to have a back up copy of your web site, specifically the web.config, and if you do does a diff between the old web.config and the new web.config show changes in System.Core and System.Data.Linq?

You should have these lines under <assemblies>:
<add assembly="System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
        <add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />


Ken Grierson
DotNetNuke Corporation
Test Lead
 
New Post
8/23/2010 11:21 PM
 
Thanks for the reply.

Our upgrade path was 4.5.5 to 4.6.2 to 4.9.5 to 5.1.1 to 5.1.4

Our web.config already had the two items you mentioned.  We fixed the problem by restoring the original 4.5.5 on a local copy and used VS 2008 to migrate to .NET 3.5 first (VS2008 prompted for this when we opened it) and then followed the upgrade path again.  This fixed the problem. 

Comparing the two web.configs, we found several differences.  Not sure exactly which ones fixed the problem.  The changes were:

1. Under <system.webServer> <modules>
    Added 
    <remove name="ScriptModule"/> 

    in front of 
    <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" preCondition="managedHandler" />

2. Under <system.webServer><handlers>
   Added to the beginning of the section:
    <remove name="WebServiceHandlerFactory-Integrated"/>
    <remove name="ScriptHandlerFactory"/>
    <remove name="ScriptHandlerFactoryAppServices"/>
    <remove name="ScriptResource"/>

 and added to the end of the section:
   <add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
   <add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
   <add name="ScriptResource" verb="GET,HEAD" path="ScriptResource.axd" preCondition="integratedMode" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>


3. Under <system.web> <compilation> <assemblies>
Added:
    <add assembly="System.Data.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />


Moving this new web.config to the production server fixed it there too.

Thanks again for your help.

Judy
 
New Post
7/1/2012 4:26 AM
 
Thanks Judy, great work.

In my case it was point 3 - the others were as described.

Best wishes
Michael

Michael Tobisch
DNN★MVP

dnn-Connect.org - The most vibrant community around the DNN-platform
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Note: You are running on an old version of the .NET Framework.Note: You are running on an old version of the .NET Framework.


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