If you explicity set the clientIDMode property in the web.config to "Static" certain admin features are broken. I believe this is to do with the way jquery in umbraco_client is selecting elements (perhaps there are some hardcoded id's)... i have also seen script errors on IE that specific target jquery as the source.

Setting a static client id in asp.net 4 has the effect of removing the container id's from page elements that would normally occur in previous versions of asp.net e.g.

"ctl100_myContainer_txtFirstName" becomes "txtFirstName" allowing easier access to elements client side.

This is set in the <pages> section of the web.config : e.g.

<pages enableEventValidation="false" clientIDMode="Static">

My current work around is to explicity set the clientIDMode on page controls themselves rather than globally in the web.config. However, I feel this should be addressed in furture iterations of umbraco so that it can be said if fully supports .net 4.0

Also logged on codeplex... with screenshot

http://umbraco.codeplex.com/workitem/28867

hope this helps anyone else who has been scratching the head for 2+ days! :)

Search Tags (based upon what i was searching for) :

clientIDMode, System.Reflection.TargetInvocationException, web.config, umbraco.uicontrols.PropertyPanel.Render, Input parameter 'controlId' cannot be an empty string, System.Web.UI.ScriptManager.RegisterExpandoAttribute, Document Types, Media Types