I have just updated my Blazor WASM app to .NET 10 and it builds and works fine on my dev machine.
I have come to deploy it to my staging site and I am getting this error:
This implies that it is looking for files in a path that is still set to .NET 9 (the version I am upgrading from).
I have looked at the settins for my app in Azure and can confirm I have set them to .NET 10:
I did wonder if it was to do with any residual detritus from my .NET 9 predecessor so I created an entirely new staging area and have the same sort of errors.
I have checked my local folders for the paths and they all seem to follow the Proj-name/(bin or obj)/(Debug or Release)/net10.0/{stuff} format.
I suspect I am missing something at the Azure end but for the life of me can't figure out what it is? Any ideas?
UPDATE - FIXED
Many thanks to Brian for pointing me in the right direction. Details of my error are in my reply to his comment. Thanks all.

