Since Microsoft release VS 2010 and .NET Framework 4.0 yesterday, I tried it out by converting an Episerver project. Almost everything seems to run smoothly except one thing.
In Edit Mode I get an error when clicking a "+" to expand a parent node in the tree view. A popup says:
"Error: The target 'FullRegion$explorerTreeView$treeView' for the callback could not be found or did not implement ICallbackEventHandler".
Any ideas for fixing this?
Sorry EPiserver CMS 5 or 6 don't officaly support .NET4, at the moment we only support Microsoft .NET Framework 3.5 SP1
Please read the System Requirements
Pelle, when is support for .NET 4 planned?
I just did a quick test installing CMS 6 with public templates, and got it working (thanks to Cristians tip) by setting the clientIDMode attribute of the system.web/pages element to AutoID.
If you don't want to do this for you whole site, I know I don't, you can set it just for the UI and Util locations!
I set the controlRenderingCompatibilityVersion to 3.5 as well just to be safe...
Haven't tried workflows or content channels or mirroring but everything seems find so long...
Just found another issue: When trying to save a page, the tougher request validation in 4.0 doesn't let the post through. This can again be easily fixed by setting <httpRuntime requestValidationMode="2.0" /> in web.config.
As with the clientIDMode you could limit it to the UI and Util locations, but only if you are not using the Edit-on-page feature. If this is enabled you need to change the validation mode for the whole site.
For more infor, see: http://www.asp.net/learn/whitepapers/aspnet4/breaking-changes/#0.1__Toc256770147
Regarding "when is support for .NET 4 planned": .NET 4 support is in the top of our backlog but we cannot today tell when we will have full support for it available. We´ll come back to this as soon as we have more information to give.
I found myself in with a similar problem but a different solution:
After installing .NET 4.0 I had the exact same problem with expanding nodes. The problem in our case was because of an "upgrade" of the web.config adding the line <xhtmlConformance mode="Legacy" />.
Removing this line solved the problem.
I'm assuming you all know that EPiServer officially support .net 4 now?
thanks guys. helped a stack..
Glad it helped - there is a package on the EPiServer Nuget Feed http://nuget.episerver.com/ called EPiServerCMS6ToNetFour that will do all the conversion work for you.
I don't believe I've ever thanked you for that NuGet package David. So: THANK YOU! :)
No worries Joel :)!