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 ...DNN 6 upgrade to .net 4.0DNN 6 upgrade to .net 4.0
Previous
 
Next
New Post
7/28/2011 1:49 PM
 
Downloaded a fresh copy of DNN 6 and opened it up in Visual Studio 2010 as a website.  VS initially displays a prompt asking if I want to upgrade the website to the latest .net framework (.net 4.0), to which i say yes.  After the upgrade process completes, I check the web.config and see some of the changes upgrading to .net 4.0:

<assemblies>
        <add assembly="Microsoft.VisualBasic, Version=10.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
        <add assembly="System.DirectoryServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
        <add assembly="System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
        <add assembly="System.Management, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
        <add assembly="System.Data.Linq, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
        <add assembly="System.Web.Abstractions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
      </assemblies>

I then run the website through Visual Studio and go through the installation process successfully.  After browsing through the site, I noticed that whenever I click the "Update" button under Admin -> Site Settings or Host -> Host Settings, I get a javascript error, and the page never saves or changes, but instead just sits and spins.  Looking at firebug, the error "can't convert undefined to object" is occurring in the jQuery file.

After doing some testing, I decided to just try installing the website on the server directly and not use Visual Studio.  So I setup up a website on our server, using IIS 6 with the .net version set to .net 4.0.  After completing the installation process, I try updating the Site Settings and of course they work as expected.  I check the .net version under Host -> Host Settings and it shows .net 4.0.  However when I look at the web.config, everything in there still looks like it is using .net 3.5.:
<assemblies>
        <add assembly="Microsoft.VisualBasic, Version=8.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
        <add assembly="System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
        <add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
        <add assembly="System.Management, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
        <add assembly="System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
        <add assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
        <add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
        <add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
        <add assembly="System.Data.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
        <add assembly="System.Web.Abstractions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
      </assemblies>
        <providerOption name="WarnAsError" value="false" />
      </compiler>
    </compilers>
  </system.codedom>

What is the correct way to upgrade the site to .net 4.0?  And why am I seeing errors when I do the upgrade through Visual Studio?
 
New Post
7/28/2011 4:47 PM
 
the correct way is to NOT do it with visual studio, but like this:

* open the site with visual studio, say NO to the upgrade question
* compile site
* close visual studio
* browse to site and install dotnetnuke
* switch application pool to .net 4 framework
* browse again to your site. DNN will do the proper modifications to your web.config
* open site again in visual studio...

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

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

 
New Post
7/28/2011 5:54 PM
 
Thanks for the help!

So I performed this process, and checked the Host -> Host Settings page and verified that it is now displaying .net framework 4.0.  However, it doesn't look like DotNetNuke modified the web.config file at all.  Using WinMerge to compare it to the originall DotNetNuke web.config that came with the download, I don't see any changes.

It still appears that the web.config is referencing 3.5 assemblies, etc. Shouldn't the it now be referencing the .net 4.0 ones?

As a side note, the website is being run under IIS 6, if that matters.
 
New Post
7/28/2011 8:39 PM
 
Been looking at the web.config for a couple of our sites that are running asp.net4.0 and am seeing the same sort of things reported as the poster in the original thread.

In the web.config for the compiler definition we have the following - on a site that is running live with asp.net 4.0 integrated

<compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CSharp.CSharpCodeProvider,System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" warningLevel="4">
        <providerOption name="CompilerVersion" value="v3.5" />
        <providerOption name="WarnAsError" value="false" />
      </compiler>

But for a asp.net 4.0 site this should in fact be something more like the following according to msdn and other sources.

  <compiler language="c#;cs;csharp" extension=".cs" warningLevel="4"
    type="Microsoft.CSharp.CSharpCodeProvider,System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
   <providerOption name="CompilerVersion" value="v4.0"/>
   <providerOption name="WarnAsError" value="false"/>
  </compiler>
 </compilers>

Please correct me if I'm wrong but surely this is telling the site to use the older 3.5 compiler at runtime and NOT the new 4.0 compiler which i would have thought should be the case.  What am i missing here ?

Westa
 
New Post
7/29/2011 12:51 PM
 
yes that seems weird. I will do some checking around and report back here

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

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

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN 6 upgrade to .net 4.0DNN 6 upgrade to .net 4.0


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