Vulnerability in EPiServer.Forms

Try our conversational search powered by Generative AI!

EPiServer CMS 6.0.530.0 + .NET 4.0 problem



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 clues?

/ Thomas


Apr 13, 2010 14:13

I think this is related to changes in ID generation for webforms. There is a javascript function related to the edit tree that makes certain assumptions about control IDs.

Apr 13, 2010 14:57

Any ideas for fixing this?

Apr 22, 2010 12:08

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





Edited, Apr 22, 2010 17:15

Pelle, when is support for .NET 4 planned?

Apr 22, 2010 17:45

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...

Edited, Apr 23, 2010 5:32

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:

Keep truckin'

Edited, Apr 23, 2010 5:52

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.

Apr 23, 2010 9:44

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.

Detail: When in Legacy-mode control-ID's will have a "_"-prefix (_ctl0xxx instead of ctl00xxx). This made the xmlResponse-calls map to non-existing controls since there is a line of javascript in WebResource.axd (so not editable by us mortals) replacing "_" with "$"...

Aug 27, 2010 16:01

I'm assuming you all know that EPiServer officially support .net 4 now?

Sep 08, 2010 1:54

thanks guys. helped a stack..

Mar 13, 2012 11:47

Glad it helped - there is a package on the EPiServer Nuget Feed called EPiServerCMS6ToNetFour that will do all the conversion work for you.

Mar 13, 2012 14:04

I don't believe I've ever thanked you for that NuGet package David. So: THANK YOU! :)

Mar 13, 2012 15:42

No worries Joel :)!

Mar 13, 2012 16:29
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.