So this function would be useless in vb.net? I understand xmlContent is obsolete. But XmlContent with a capitial X not. It would be nice to have obsolete functions other naming conventions (as example with underscore or something like that), because vb.n4et does not work out for a solution like this?
Are you referencing the "XmlContent" property anywhere else ... as in apart from using "Instance.XmlContent"? ... or even another reference to "umbraco.content" that is causing this ambiguity?
Would you mind providing a bigger code snippet? So that we can get a better understanding of the context?
I'm coming up against the same "umbraco.content.Instance.XmlContent ambigious" error in my VB custom section. The case sensitivity issue seems to be the issue. Is there a solution?
umbraco.content.Instance.XmlContent ambigious
I'm using Windows XP with VS 2010 beta 2 and get an error:
Error 1 'XmlContent' is ambiguous because multiple kinds of members with this name exist in class 'umbraco.content'. \site\usercontrol.ascx.vb
code:
.Instance.XmlContent
Am i missing something?
It might be a clash with the static (obsolete) property umbraco.content.xmlContent since VB is not case sensitive.
But this is just a guess.
So this function would be useless in vb.net? I understand xmlContent is obsolete. But XmlContent with a capitial X not. It would be nice to have obsolete functions other naming conventions (as example with underscore or something like that), because vb.n4et does not work out for a solution like this?
Hi asper,
Are you referencing the "XmlContent" property anywhere else ... as in apart from using "Instance.XmlContent"? ... or even another reference to "umbraco.content" that is causing this ambiguity?
Would you mind providing a bigger code snippet? So that we can get a better understanding of the context?
Thanks, Lee.
I'm coming up against the same "umbraco.content.Instance.XmlContent ambigious" error in my VB custom section. The case sensitivity issue seems to be the issue. Is there a solution?
Thanks, Simon
is working on a reply...