Cannot change float values in a native application in debugger - by Ondrej Spanel

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


5
0
Sign in
to vote
ID 772511 Comments
Status Closed Workarounds
Type Bug Repros 5
Opened 11/28/2012 6:06:13 AM
Access Restriction Public

Description

When debugging and trying to change a value of a float variable, only very limited set of values is accepted, like 1 or 0. Values like 0.1 or 2 are not accepted.
Sign in to post a comment.
Posted by Microsoft on 12/13/2012 at 2:16 PM
Thanks a lot for the information. We should have this fixed in a future release of Visual Studio.
Posted by Bc_msdn on 12/3/2012 at 5:16 AM
We have the same issue on several systems and changing the locale is a workaround that 'fixes' it.

This means that almost EVERY Visual Studio user in the following countries will be affected:

Albania, Andorra, Argentina, Armenia, Austria, Azerbaijan, Belarus, Belgium, Bolivia, Bosnia and Herzegovina, Brazil, Bulgaria, Cameroon, Canada (French-speaking), Chile, Colombia, Costa Rica, Croatia (comma used officially, but both forms are in use elsewhere), Cuba, Cyprus, Czech Republic, Denmark, Dominican Republic, Ecuador, Estonia, Faroes, Finland, France, Germany, Georgia, Greece, Greenland, Honduras, Hungary, Iceland, Indonesia, Italy, Kazakhstan, Kirgistan, Latvia, Lebanon, Lithuania, Luxembourg (uses both marks officially), Macau (in Portuguese text), Macedonia, Moldova, Mongolia, Morocco, Netherlands, Norway, Paraguay, Peru, Poland, Portugal, Romania, Russia, Serbia, Slovakia, Slovenia, South Africa (officially[15]), Spain, Sweden, Tunisia, Turkey, Ukraine, Uruguay, Uzbekistan, Venezuela, Vietnam.
Posted by Microsoft on 11/30/2012 at 5:34 PM
Thank you for your feedback. We have had reports of similar issues from other customers and determined that the problem was caused by the use of a system locale setting in which decimals were formatted using a comma, rather than a period. We are considering fixing this for a future release, but in the meantime, the issue can be worked around by editing your region settings in control panel to use English for number formatting. To verify that this is indeed your issue, can you confirm that you are indeed using decimal-point-as-comma locale settings on your computer?

Eric Feiveson - Visual Studio Debugger Team
Posted by Ondrej Spanel on 11/29/2012 at 12:00 AM
I am sorry, I cannot. I have no experience with capturing video and I have no idea what to do. Moreover, the repro steps I have provided are really trivial and detailed, it does not seem like then need a video to accompany them. Is there any problem with the repro?
Posted by Microsoft on 11/28/2012 at 11:38 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a video of this issue so that we can conduct further research?

We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 11/28/2012 at 6:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)