Definition required: C/C++ --> General --> Use Unicode For Assembler Listing - by Vaitalien

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 688776 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 9/16/2011 2:49:53 AM
Access Restriction Public


There appears no documentation on MSDN for the Visual Studio 2010 property 'C/C++ --> General --> Use Unicode For Assembler Listing' (whether set programmatically or through the Property Pages)

Is it equal to 'C/C++ --> General --> Use UNICODE Response Files' in Visual Studio 2008?

The MSDN page for 'Use UNICODE Response Files' ( includes 'Visual Studio 2010' under 'Other Versions'. If the properties are equal then this is misleading.

Also, there are no remarks about either property on the MSDN pages for /utf8output ( or /FAu (

If the two properties are equal then the VCConvertEngine is not aware, because converting an 08 project to 2010 gives the following warning in the Conversion Report:
'VCConvertEngine could not convert attribute UseUnicodeResponseFiles = false under Tool VCCLCompilerTool'
Sign in to post a comment.
Posted by Microsoft on 8/7/2012 at 5:36 PM

This property was used to disable unicode support in the compiler tools, which in VS 2010 became a default and not disable-able. You will not need to convert this property unless you have a reason to specifically disable unicode support in the parameters passed to the tools.

Please let us know if you have a scenario where you need this support for C++ projects in VS 2010 or VS 2012.

~Pete Steijn
Visual C++ Team
Posted by EricLeong [Feedback Moderator] on 9/18/2011 at 8:01 PM
Thank you for submitting feedback on Visual Studio 2010 and .NET Framework. Your issue has been routed to the appropriate VS development team for review. We will contact you if we require any additional information.
Posted by MS-Moderator01 on 9/16/2011 at 3:42 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(