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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...How To? Running the latest version of DNN under .NET 4.0How To? Running the latest version of DNN under .NET 4.0
Previous
 
Next
New Post
4/28/2011 2:12 PM
 
Hello,

I have search for resources on the easiest way to upgrade the latest version of DotNetNuke to run a site under .NET 4.0 but I am not confident that my results are current as what i have found seems to date back to early 2010.  Can someone please point me in the right direction for resources on how to upgrade existing sites so that version 4.0 of the dot net framework is used on the website?
 
New Post
4/28/2011 2:32 PM
 
I'm pretty sure I go through the process in this video

http://www.dotnetnuke.com/Resources/V...


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
4/29/2011 3:25 PM
 
Thank's Chris.  I do not use webmatrix for my development (maybe I should?).  I still use IIS 7.0 both in my development and production environments.  After watching your video I translated that into "Change the application pool of the website to use 4.0 and that should do it...", it did.  After change the pool I revisited the site and confirmed in my dashboard that it is running 4.0...

Next I opened the project in Visual Studio 2010 and received the following notification:

"The site 'http://domainremoved.com' is currently configured for use with a newer version of ASP.NET (4.0).  This project is targeting ASP.NET 2.0; if not configured some features may make incorrect assumptions, and pages designed with the tool my not render correctly.

Would you like the site to be configured for use with ASP.NET 2.0"

If i choose yes, VS goes and changes the app pool of the IIS site to use the DefaultAppPool which is 2.0.  If I say no i continue to receive this notice every time i open my solution...

Am I on the wrong path trying to continue to use IIS for my development envionroment?  Any suggestions would be greatly appreciated; I am venturing into unknown territory for me and I want to make sure my upgrades are done consistently and correctly through the 20+ DNN websites that I manage.

I have noticed that simply changing the .NET framework version to 4.0 does not change the fact that my web.config references .NET 2.0 assemblies.  I am trying to follow an upgrade path that does not require me to open up visual studio so that i can do this to all of my production sites without using devel tools, but I still have a handful of sites i need to open in visual studio to make changes to custom modules.

Please help!

Matt Christenson
 
New Post
4/29/2011 3:32 PM
 
As an update I have entered into the project properties of the website in VS and on the build tab changed the target framework to .NET Framework 4.0. It gave me the following warning:

"Changing the Target Framework requires that the current project be closed and then reopened. Any unsaved changes within the project will be automatically saved. Changing Target Framework may require manual modification of project files in order to build. Are you sure you want to change the Target Framework for this project?"

I selected "Yes".

I then closed and reopened visual studio and did not receive the warning, however after peeking into my web.config i see VS has updated .NET references for me.

My question is why did the site still work when the app pool was 4.0 but the references were 2.0 and 3.5, and is there a way to change the web.config consistently on other DNN sites to point to 4.0 references without opening each site using Visual Studio, or going over each web.config file line-by-line?
 
New Post
4/29/2011 3:36 PM
 
One more concern - I see in my web.config files that my handlers have a precondition of runtimeVersionv2.0 - i recall seeing concerns about this in 1 year old documentation indicating these needed to be removed... Is this true?

I recall when 3.5 came out you guys put an "Upgrade to 3.5 framework" feature into the host settings menu - is this something we might shortly see in the DotNetNuke core?
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...How To? Running the latest version of DNN under .NET 4.0How To? Running the latest version of DNN under .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