I have a web service, accessed from an ASP page. Somewhere between calling the web service, and it being de-serialised at the WS end, any UTF-8 'wide' characters like £ get translated to '??'. These then get saved on the database (NVARCHAR columns, so Unicode should be OK).
However, if I store '£' on the database table manually, and then enquire on it using another method of the same web service, the '£' comes through unscathed, and displays correctly in the UI.
All the WSDL specifies utf-8, and web.config files have globalization entries for request and response encoding utf-8.
Has anyone seen anything like this, where serialisation works fine in one direction but not the another?
However, if I store '£' on the database table manually, and then enquire on it using another method of the same web service, the '£' comes through unscathed, and displays correctly in the UI.
All the WSDL specifies utf-8, and web.config files have globalization entries for request and response encoding utf-8.
Has anyone seen anything like this, where serialisation works fine in one direction but not the another?