I am trying to write a modified version of noNodes.aspx and have hit another road block. There appears to be no way to reference umbraco.IO which apparently is needed by IOHelper.MapPath.
The umbraco.IO namespace is located in the businesslogic.dll did you modified the source directly or did you create a seperate project? if you've created a seperate project make sure you reference the assemblies:
Ah I know what happened, thanks Jorge. I the same once with the new install of my machine. I couldn't reference any Umbraco assembly. then I looked at the warnings and noticed that it needed the older (1.0) version of asp.net ajax. When I installed that it worked just fine. Just google on the warning that you see and it will point you to the correct download link.
umbraco.IO missing / not found
I am trying to write a modified version of noNodes.aspx and have hit another road block. There appears to be no way to reference umbraco.IO which apparently is needed by IOHelper.MapPath.
How do I solve this?
The umbraco.IO namespace is located in the businesslogic.dll did you modified the source directly or did you create a seperate project? if you've created a seperate project make sure you reference the assemblies:
Cheers,
Richard
I have all three referenced and Visual Studio is not finding the umbraco.io namespace. It finds the others I need.
The code below fails to compile. The IO in umbraco.IO does not exist in the umbraco namespace.
Hi Connie, the same issue, but when i use the VS 2010, but in the VS 2008 works perfect.
Hope, helps.
Jorge
Ah I know what happened, thanks Jorge. I the same once with the new install of my machine. I couldn't reference any Umbraco assembly. then I looked at the warnings and noticed that it needed the older (1.0) version of asp.net ajax. When I installed that it worked just fine. Just google on the warning that you see and it will point you to the correct download link.
Hope this helps you both,
Richard
Thanks Richard, i'll take a look about the ajax issue.
Jorge
I also noticed that by default my project was not using the 4.0 version of the .NET framework.
is working on a reply...