This new custom component of course does not display anything as a result. The previous customer components created in other tabs before recent Radzen designer tool updates are all ok.
Here is the head of the page that cannot be found:
As far as I can see you are posting screenshots from Visual Studio, not sure how Radzen designer is related. I've tried similar setup and it worked normally runtime:
They both say that the namespace name does not exist but only the new custom component added after recent Radzen updates does not work. Let me know if you would like the meta project to investigate.
From your screenshot I can see that the component name is AdminItemPriceList while it is generated as AdminItemPricelist. I'm not sure how to reproduce this however.
Except the picker you can set the component name directly using binding dialog:
I changed this to an upper case L and re-linked the component and Hey Presto! It worked! - no need for binding dialog.
I guess that the code automatically upper cases after a whitespace in the name so if the page name is lowercase after a whitespace then this is where you hit the problem.