The name 'GetLegacyIActionJavascript' does not exist in the current context
Though this was highlighted in Visual Studio, it seem to run no problems, now after adding a piece of media and reloading the page, it threw the error...
this is on a upgraded project to v4.5.1
Compiler Error Message: CS0103: The name 'GetLegacyIActionJavascript' does not exist in the current context
on a win2008 server I don't get the GetLegacyIActionJavascript but now I get an empty tree. treeWindow_content stays empty without any javascript errors :(
Error 393 The name 'GetLegacyIActionJavascript' does not exist in the current context c:\Projects_IGT.com\Umbraco\Web\umbraco\controls\Tree\TreeControl.ascx 60
trying to compile the the whole thing with Umbraco/umbraco folder in it...
The name 'GetLegacyIActionJavascript' does not exist in the current context
Though this was highlighted in Visual Studio, it seem to run no problems, now after adding a piece of media and reloading the page, it threw the error...
this is on a upgraded project to v4.5.1
Compiler Error Message: CS0103: The name 'GetLegacyIActionJavascript' does not exist in the current context
Source Error:
Line 60: <%#GetLegacyIActionJavascript()%>
Source File: d:\My Developments\UMBRACO\v4.5.1_for_net_3_5\build\umbraco\controls\Tree\TreeControl.ascx Line: 60
any ideas? help! :(
Full exception ..
got the same problem,
copying the 4.5.1 bin folder from the download once again did the trick for me
Thanks Bram, I did that and it enabled me to get back in, but when trying to media it errors again.
So it's not really a solution. :(
on a win2008 server I don't get the GetLegacyIActionJavascript but now I get an empty tree.
treeWindow_content stays empty without any javascript errors :(
this are the console errors I get
I'm getting the same error
Error 393 The name 'GetLegacyIActionJavascript' does not exist in the current context c:\Projects_IGT.com\Umbraco\Web\umbraco\controls\Tree\TreeControl.ascx 60
trying to compile the the whole thing with Umbraco/umbraco folder in it...
Any ideas ?
What server are you running on?
We got this problem on a new Win2008Server and we solved this problem by uninstalling and reinstalling IIS7 again.
Hope this will help you.
is working on a reply...