错误输出的代码页 [英] codepage of error output

问题描述

我正在以编程方式调用Visual C ++来构建我的解决方案。 （BuildManager :: Build）我将一个记录器传递给它（ILogger）。直到最后一次更新（我不确定它是2017年的更新还是2017年的次要更新）警告和错误
消息，而不是构建消息（!!）是...错误格式化。它们都是unicode字符串（我猜，因为它是.net）但这些值似乎是使用错误的代码页从单字节字符串转换而来。

我可以改变一些东西让它再次起作用？是设置还是错误？ ...对我来说奇怪的是，构建消息是正确的......

Rudolf

解决方案

< blockquote>

感谢您在这里发帖。

>>直到最后一次更新（我不是确定它是2017年的更新还是2017年的次要更新）警告和错误消息，但不是构建消息（!!）是......错误的格式化。它们都是unicode字符串（我猜，因为它是.net）
但这些值似乎是使用错误的代码页从单字节字符串转换而来。

As据我所知，ILogger接口使用格式化字符串进行日志记录。请提供有关如何调用ILogger以使用c ++记录输出字符串的更多信息。

这是一个关于如何格式化输出的文档，你可以参考。

https://msdn.microsoft.com/en-us/library/yxkt8b26.aspx

<希望这可以帮到你。

最好的问候，

Baron Bi

I'm building my solutions by calling Visual C++ programmatically. (BuildManager::Build) and I'm passing a logger to it (ILogger). Until the last update (I'm not sure if it was the update to 2017 or just a minor 2017 update) the warning and error messages, but not the build messages (!!) are... wrong formated. They are all unicode strings (I guess, because it's .net) but those values seem to be converted from single byte strings using a wrong codepage.

Can I change something to make it work again? Is it a setting or a bug? ... for me the strange thing is, that the build messages are correct...

Rudolf

解决方案

Hi,

thanks for posting here.

>>Until the last update (I'm not sure if it was the update to 2017 or just a minor 2017 update) the warning and error messages, but not the build messages (!!) are... wrong formated. They are all unicode strings (I guess, because it's .net) but those values seem to be converted from single byte strings using a wrong codepage.

As far as I know, the ILogger interfaces log with formatted strings. Please provide more information about how do you call ILogger to log the output strings with c++.

Here is a document about how to format the output, you could refer to.

https://msdn.microsoft.com/en-us/library/yxkt8b26.aspx

Hope this could be help of you.

Best Regards,

Baron Bi

这篇关于错误输出的代码页的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！