Calling unmanaged DLL with fixed buffer from managed code (Encoding issue)?

You cannot convince the pinvoke marshaller to convert from utf8. It will either assume utf-16 or the system default code page and always convert to utf-16 Not a problem, just do it yourself. Declare the arguments of type byte instead.

Create the arrays before the call with the proper length, after the call use Encoding. UTF8.GetString() to convert.

You cannot convince the pinvoke marshaller to convert from utf8. It will either assume utf-16 or the system default code page and always convert to utf-16. Not a problem, just do it yourself.

Declare the arguments of type byte instead. Create the arrays before the call with the proper length, after the call use Encoding. UTF8.GetString() to convert.

Nice, clean and working solution. Thanks! – eckes Nov 7 at 11:05.

There's an absolutely awesome article on this topic which helped me solve exactly this problem. Here it is: undermyhat.org/blog/2009/08/tip-force-ut... Essentially, you have to use xmlWriter. ForceEncoding(Encoding.

UTF8) to force the encoding, but there are some caveats to it. Give the article a read and it should help you understand what's going on, why it's UTF-16 in the first place and how to get round it.

Thanks for the answer. I already read the article before but it doesn't actually cover my problem: the writing of the xml files is just for debugging. In normal application use, the content of outputXml and errorXml is directly used in the application without writing it out to a file... – eckes Nov 7 at 9:36.

Try doing something like this (it gives a way to override the default nature of . NET's UTF-16): public class StringWriterWithEncoding : StringWriter { Encoding encoding; public StringWriterWithEncoding (StringBuilder builder, Encoding encoding) :base(builder) { this. Encoding = encoding; } public override Encoding Encoding { get { return encoding; } } } The logic behind this is it gives a means to override .

NET's default UTF-16 encoding for StringWriters. Then you can cal it like this: edit StringBuilder builder = new StringBuilder(); StringWriterWithEncoding stringWriter = new StringWriterWithEncoding(builder, Encoding. UTF8) XmlWriter writer = new XmlTextWriter( stringWriter ); return stringWriter.ToString().

You cannot convince the pinvoke marshaller to convert from utf8. It will either assume utf-16 or the system default code page and always convert to utf-16.

There's an absolutely awesome article on this topic which helped me solve exactly this problem. Here it is: http://www.undermyhat.org/blog/2009/08/tip-force-utf8-or-other-encoding-for-xmlwriter-with-stringbuilder.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.