Display double in immediate window different in vs2013/vs2017 The Next CEO of Stack OverflowUse of var keyword in C#MSBuild doesn't copy references (DLL files) if using project dependencies in solutionVisual Studio Clicking Find Results Opens Code in Wrong WindowVisual Studio debugging/loading very slowVisual Studio displaying errors even if projects buildUpgrading vs2012 project to vs2013 still displays project as vs2012Found conflicts between different versions of the same dependent assembly that could not be resolvedUpgrade Visual Studio 2013 solutions to Visual Studio 2015How to disable the new debug window in VS2017Why does checked_array_iterator work without including <iterator> in VS2013 but fails in VS2017?
Creating a script with console commands
Avoiding the "not like other girls" trope?
How should I connect my cat5 cable to connectors having an orange-green line?
Does Germany produce more waste than the US?
Why does freezing point matter when picking cooler ice packs?
Incomplete cube
What does this strange code stamp on my passport mean?
A hang glider, sudden unexpected lift to 25,000 feet altitude, what could do this?
Is the offspring between a demon and a celestial possible? If so what is it called and is it in a book somewhere?
Upgrading From a 9 Speed Sora Derailleur?
Can this transistor (2n2222) take 6V on emitter-base? Am I reading datasheet incorrectly?
How badly should I try to prevent a user from XSSing themselves?
My boss doesn't want me to have a side project
Is it possible to make a 9x9 table fit within the default margins?
Does the Idaho Potato Commission associate potato skins with healthy eating?
Find a path from s to t using as few red nodes as possible
Is it OK to decorate a log book cover?
MT "will strike" & LXX "will watch carefully" (Gen 3:15)?
Direct Implications Between USA and UK in Event of No-Deal Brexit
Cannot restore registry to default in Windows 10?
Airship steam engine room - problems and conflict
Salesforce opportunity stages
Can Sri Krishna be called 'a person'?
Is it possible to create a QR code using text?
Display double in immediate window different in vs2013/vs2017
The Next CEO of Stack OverflowUse of var keyword in C#MSBuild doesn't copy references (DLL files) if using project dependencies in solutionVisual Studio Clicking Find Results Opens Code in Wrong WindowVisual Studio debugging/loading very slowVisual Studio displaying errors even if projects buildUpgrading vs2012 project to vs2013 still displays project as vs2012Found conflicts between different versions of the same dependent assembly that could not be resolvedUpgrade Visual Studio 2013 solutions to Visual Studio 2015How to disable the new debug window in VS2017Why does checked_array_iterator work without including <iterator> in VS2013 but fails in VS2017?
I have the following line of code:
double r = 0.000056262413896897934;
In visual studio 2013, I go to the immediate windows and type:
?r
And the results display the double's value:
0.000056262413896897934
However if I bring up the project in Visual Studio 2017 and type this in the immediate window:
?r
It display the following result (exponential format):
5.6262413896897934E-05
I would like Visual Studio 2017 to display the format in the same way as Visual Studio 2013 does:
0.000056262413896897934
Not just for this variable or this solution but as a permanent setting. Does anyone know how to do this? Thanks in advance
c# visual-studio visual-studio-2017
edited Mar 15 at 10:12
marc_s
583k13011241270
asked Mar 8 at 19:03
Robert SmithRobert Smith
311213
add a comment |
I have the following line of code:
double r = 0.000056262413896897934;
In visual studio 2013, I go to the immediate windows and type:
?r
And the results display the double's value:
0.000056262413896897934
However if I bring up the project in Visual Studio 2017 and type this in the immediate window:
?r
It display the following result (exponential format):
5.6262413896897934E-05
I would like Visual Studio 2017 to display the format in the same way as Visual Studio 2013 does:
0.000056262413896897934
Not just for this variable or this solution but as a permanent setting. Does anyone know how to do this? Thanks in advance
c# visual-studio visual-studio-2017
edited Mar 15 at 10:12
marc_s
583k13011241270
asked Mar 8 at 19:03
Robert SmithRobert Smith
311213
TheDebuggerDisplayattribute at the assembly level, maybe. Not a permanent setting, but semi-permanent.
– Amy
Mar 8 at 19:31
Tools > Options > Debugging > General, tick the "Use the legacy C# and VB expression handlers" checkbox. It is permanent, but the message box does remind you that getting used to this minor quirk is easier today than it will be tomorrow.
– Hans Passant
Mar 9 at 9:28
It's best not to use the legacy C# and VB expression handlers. While changing that might change this behavior it has a far wider impact. While it's not ideal the workaround below is a better long term solution. If you'd like to change the default for all users open an issue on developer feedback. (Disclosure: I work on the VS debugger)
– Andy Sterland
Mar 9 at 18:08
Andy, you had it working so nice in vs2013! Why default to exponential format which is so tricky? At first glance someone could think it's 5.63... The truth being that the value is less than 1! Very unfriendly to the eyes, just my two cents.
– Robert Smith
Mar 11 at 18:45
add a comment |
I have the following line of code:
double r = 0.000056262413896897934;
In visual studio 2013, I go to the immediate windows and type:
?r
And the results display the double's value:
0.000056262413896897934
However if I bring up the project in Visual Studio 2017 and type this in the immediate window:
?r
It display the following result (exponential format):
5.6262413896897934E-05
I would like Visual Studio 2017 to display the format in the same way as Visual Studio 2013 does:
0.000056262413896897934
Not just for this variable or this solution but as a permanent setting. Does anyone know how to do this? Thanks in advance
c# visual-studio visual-studio-2017
edited Mar 15 at 10:12
marc_s
583k13011241270
asked Mar 8 at 19:03
Robert SmithRobert Smith
311213
I have the following line of code:
double r = 0.000056262413896897934;
In visual studio 2013, I go to the immediate windows and type:
?r
And the results display the double's value:
0.000056262413896897934
However if I bring up the project in Visual Studio 2017 and type this in the immediate window:
?r
It display the following result (exponential format):
5.6262413896897934E-05
I would like Visual Studio 2017 to display the format in the same way as Visual Studio 2013 does:
0.000056262413896897934
Not just for this variable or this solution but as a permanent setting. Does anyone know how to do this? Thanks in advance
c# visual-studio visual-studio-2017
c# visual-studio visual-studio-2017
edited Mar 15 at 10:12
marc_s
583k13011241270
asked Mar 8 at 19:03
Robert SmithRobert Smith
311213
edited Mar 15 at 10:12
marc_s
583k13011241270
asked Mar 8 at 19:03
Robert SmithRobert Smith
311213
edited Mar 15 at 10:12
marc_s
583k13011241270
edited Mar 15 at 10:12
marc_s
583k13011241270
edited Mar 15 at 10:12
marc_s
583k13011241270
583k13011241270
asked Mar 8 at 19:03
Robert SmithRobert Smith
311213
asked Mar 8 at 19:03
Robert SmithRobert Smith
311213
asked Mar 8 at 19:03
Robert SmithRobert Smith
311213
311213
TheDebuggerDisplayattribute at the assembly level, maybe. Not a permanent setting, but semi-permanent.
– Amy
Mar 8 at 19:31
Tools > Options > Debugging > General, tick the "Use the legacy C# and VB expression handlers" checkbox. It is permanent, but the message box does remind you that getting used to this minor quirk is easier today than it will be tomorrow.
– Hans Passant
Mar 9 at 9:28
It's best not to use the legacy C# and VB expression handlers. While changing that might change this behavior it has a far wider impact. While it's not ideal the workaround below is a better long term solution. If you'd like to change the default for all users open an issue on developer feedback. (Disclosure: I work on the VS debugger)
– Andy Sterland
Mar 9 at 18:08
Andy, you had it working so nice in vs2013! Why default to exponential format which is so tricky? At first glance someone could think it's 5.63... The truth being that the value is less than 1! Very unfriendly to the eyes, just my two cents.
– Robert Smith
Mar 11 at 18:45
add a comment |
TheDebuggerDisplayattribute at the assembly level, maybe. Not a permanent setting, but semi-permanent.
– Amy
Mar 8 at 19:31
Tools > Options > Debugging > General, tick the "Use the legacy C# and VB expression handlers" checkbox. It is permanent, but the message box does remind you that getting used to this minor quirk is easier today than it will be tomorrow.
– Hans Passant
Mar 9 at 9:28
It's best not to use the legacy C# and VB expression handlers. While changing that might change this behavior it has a far wider impact. While it's not ideal the workaround below is a better long term solution. If you'd like to change the default for all users open an issue on developer feedback. (Disclosure: I work on the VS debugger)
– Andy Sterland
Mar 9 at 18:08
Andy, you had it working so nice in vs2013! Why default to exponential format which is so tricky? At first glance someone could think it's 5.63... The truth being that the value is less than 1! Very unfriendly to the eyes, just my two cents.
– Robert Smith
Mar 11 at 18:45
The
DebuggerDisplay attribute at the assembly level, maybe. Not a permanent setting, but semi-permanent.– Amy
Mar 8 at 19:31
The
DebuggerDisplay attribute at the assembly level, maybe. Not a permanent setting, but semi-permanent.– Amy
Mar 8 at 19:31
Tools > Options > Debugging > General, tick the "Use the legacy C# and VB expression handlers" checkbox. It is permanent, but the message box does remind you that getting used to this minor quirk is easier today than it will be tomorrow.
– Hans Passant
Mar 9 at 9:28
Tools > Options > Debugging > General, tick the "Use the legacy C# and VB expression handlers" checkbox. It is permanent, but the message box does remind you that getting used to this minor quirk is easier today than it will be tomorrow.
– Hans Passant
Mar 9 at 9:28
It's best not to use the legacy C# and VB expression handlers. While changing that might change this behavior it has a far wider impact. While it's not ideal the workaround below is a better long term solution. If you'd like to change the default for all users open an issue on developer feedback. (Disclosure: I work on the VS debugger)
– Andy Sterland
Mar 9 at 18:08
It's best not to use the legacy C# and VB expression handlers. While changing that might change this behavior it has a far wider impact. While it's not ideal the workaround below is a better long term solution. If you'd like to change the default for all users open an issue on developer feedback. (Disclosure: I work on the VS debugger)
– Andy Sterland
Mar 9 at 18:08
Andy, you had it working so nice in vs2013! Why default to exponential format which is so tricky? At first glance someone could think it's 5.63... The truth being that the value is less than 1! Very unfriendly to the eyes, just my two cents.
– Robert Smith
Mar 11 at 18:45
Andy, you had it working so nice in vs2013! Why default to exponential format which is so tricky? At first glance someone could think it's 5.63... The truth being that the value is less than 1! Very unfriendly to the eyes, just my two cents.
– Robert Smith
Mar 11 at 18:45
add a comment |
1 Answer
1
active
oldest
votes
As @Amy mentioned you can use DebuggerDisplay to change the appearance of an object in the debugger. As double is a built in type you can't just change its implementation. For cases like this the debugger has a feature where it will load in DebuggerDisplay implementations externally that are implemented in autoexp.cs
- Open (as admin) the
autoexep.csfile which should be in a directory that looks like:C:Program Files (x86)Microsoft Visual Studio16PreviewCommon7PackagesDebuggerVisualizersOriginalobviously that will change with your VS version but if you search forautoexp.csyou'll find it. - In that file, add the code below:
[assembly: DebuggerDisplay(@"ToString(""F17""),nq", Target = typeof(Double))]that's going to tell the debugger to basically executeToString("F17")whenever it's displaying adouble. - Open a Developer Command Prompt as admin and navigate to where
autoexp.csis e.g.C:Program Files (x86)Microsoft Visual Studio16PreviewCommon7PackagesDebuggerVisualizersOriginal - Build the file with
csc /t:library autoexp.cs - Reload VS and run your scenario
You should then see something like:
More info on DebuggerDisplay is in our docs over at: https://docs.microsoft.com/en-us/visualstudio/debugger/using-the-debuggerdisplay-attribute?view=vs-2017 and more info on the ToString implementation for Double is over at: https://docs.microsoft.com/en-us/dotnet/api/system.double.tostring?view=netframework-4.7.2.
answered Mar 9 at 4:41
Andy SterlandAndy Sterland
1,062813
Andy, I really appreciate your response. Thank you very much! But very sad that exponential format is the default now. Why default to exponential format which is so tricky? At first glance someone could think it's 5.63... The truth being that the value is less than 1! Very unfriendly to the eyes, just my two cents.
– Robert Smith
Mar 11 at 18:47
I don't think it's a case of it being difficult. The ToString implementation contains a way to visualize the a double in either way (and many others). Again, it's not VS that changed here but the implementation in .NET that changed the ToString implementation. You can look at the .NET Core version at: github.com/dotnet/corefx/blob/…. Which just calls into NumberFormat/NumberToDouble. I have no idea when/if that changed. It could be worth opening an issue on GitHub to find out more.
– Andy Sterland
Mar 11 at 21:07
Though, one reason for the change might simply be that a exponent and mantissa more accurately represent a double than a decimal. Given that the underlying storage is that way.
– Andy Sterland
Mar 12 at 6:13
add a comment |
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55069442%2fdisplay-double-in-immediate-window-different-in-vs2013-vs2017%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
As @Amy mentioned you can use DebuggerDisplay to change the appearance of an object in the debugger. As double is a built in type you can't just change its implementation. For cases like this the debugger has a feature where it will load in DebuggerDisplay implementations externally that are implemented in autoexp.cs
- Open (as admin) the
autoexep.csfile which should be in a directory that looks like:C:Program Files (x86)Microsoft Visual Studio16PreviewCommon7PackagesDebuggerVisualizersOriginalobviously that will change with your VS version but if you search forautoexp.csyou'll find it. - In that file, add the code below:
[assembly: DebuggerDisplay(@"ToString(""F17""),nq", Target = typeof(Double))]that's going to tell the debugger to basically executeToString("F17")whenever it's displaying adouble. - Open a Developer Command Prompt as admin and navigate to where
autoexp.csis e.g.C:Program Files (x86)Microsoft Visual Studio16PreviewCommon7PackagesDebuggerVisualizersOriginal - Build the file with
csc /t:library autoexp.cs - Reload VS and run your scenario
You should then see something like:
More info on DebuggerDisplay is in our docs over at: https://docs.microsoft.com/en-us/visualstudio/debugger/using-the-debuggerdisplay-attribute?view=vs-2017 and more info on the ToString implementation for Double is over at: https://docs.microsoft.com/en-us/dotnet/api/system.double.tostring?view=netframework-4.7.2.
answered Mar 9 at 4:41
Andy SterlandAndy Sterland
1,062813
Andy, I really appreciate your response. Thank you very much! But very sad that exponential format is the default now. Why default to exponential format which is so tricky? At first glance someone could think it's 5.63... The truth being that the value is less than 1! Very unfriendly to the eyes, just my two cents.
– Robert Smith
Mar 11 at 18:47
I don't think it's a case of it being difficult. The ToString implementation contains a way to visualize the a double in either way (and many others). Again, it's not VS that changed here but the implementation in .NET that changed the ToString implementation. You can look at the .NET Core version at: github.com/dotnet/corefx/blob/…. Which just calls into NumberFormat/NumberToDouble. I have no idea when/if that changed. It could be worth opening an issue on GitHub to find out more.
– Andy Sterland
Mar 11 at 21:07
Though, one reason for the change might simply be that a exponent and mantissa more accurately represent a double than a decimal. Given that the underlying storage is that way.
– Andy Sterland
Mar 12 at 6:13
add a comment |
As @Amy mentioned you can use DebuggerDisplay to change the appearance of an object in the debugger. As double is a built in type you can't just change its implementation. For cases like this the debugger has a feature where it will load in DebuggerDisplay implementations externally that are implemented in autoexp.cs
- Open (as admin) the
autoexep.csfile which should be in a directory that looks like:C:Program Files (x86)Microsoft Visual Studio16PreviewCommon7PackagesDebuggerVisualizersOriginalobviously that will change with your VS version but if you search forautoexp.csyou'll find it. - In that file, add the code below:
[assembly: DebuggerDisplay(@"ToString(""F17""),nq", Target = typeof(Double))]that's going to tell the debugger to basically executeToString("F17")whenever it's displaying adouble. - Open a Developer Command Prompt as admin and navigate to where
autoexp.csis e.g.C:Program Files (x86)Microsoft Visual Studio16PreviewCommon7PackagesDebuggerVisualizersOriginal - Build the file with
csc /t:library autoexp.cs - Reload VS and run your scenario
You should then see something like:
More info on DebuggerDisplay is in our docs over at: https://docs.microsoft.com/en-us/visualstudio/debugger/using-the-debuggerdisplay-attribute?view=vs-2017 and more info on the ToString implementation for Double is over at: https://docs.microsoft.com/en-us/dotnet/api/system.double.tostring?view=netframework-4.7.2.
answered Mar 9 at 4:41
Andy SterlandAndy Sterland
1,062813
Andy, I really appreciate your response. Thank you very much! But very sad that exponential format is the default now. Why default to exponential format which is so tricky? At first glance someone could think it's 5.63... The truth being that the value is less than 1! Very unfriendly to the eyes, just my two cents.
– Robert Smith
Mar 11 at 18:47
I don't think it's a case of it being difficult. The ToString implementation contains a way to visualize the a double in either way (and many others). Again, it's not VS that changed here but the implementation in .NET that changed the ToString implementation. You can look at the .NET Core version at: github.com/dotnet/corefx/blob/…. Which just calls into NumberFormat/NumberToDouble. I have no idea when/if that changed. It could be worth opening an issue on GitHub to find out more.
– Andy Sterland
Mar 11 at 21:07
Though, one reason for the change might simply be that a exponent and mantissa more accurately represent a double than a decimal. Given that the underlying storage is that way.
– Andy Sterland
Mar 12 at 6:13
add a comment |
As @Amy mentioned you can use DebuggerDisplay to change the appearance of an object in the debugger. As double is a built in type you can't just change its implementation. For cases like this the debugger has a feature where it will load in DebuggerDisplay implementations externally that are implemented in autoexp.cs
- Open (as admin) the
autoexep.csfile which should be in a directory that looks like:C:Program Files (x86)Microsoft Visual Studio16PreviewCommon7PackagesDebuggerVisualizersOriginalobviously that will change with your VS version but if you search forautoexp.csyou'll find it. - In that file, add the code below:
[assembly: DebuggerDisplay(@"ToString(""F17""),nq", Target = typeof(Double))]that's going to tell the debugger to basically executeToString("F17")whenever it's displaying adouble. - Open a Developer Command Prompt as admin and navigate to where
autoexp.csis e.g.C:Program Files (x86)Microsoft Visual Studio16PreviewCommon7PackagesDebuggerVisualizersOriginal - Build the file with
csc /t:library autoexp.cs - Reload VS and run your scenario
You should then see something like:
More info on DebuggerDisplay is in our docs over at: https://docs.microsoft.com/en-us/visualstudio/debugger/using-the-debuggerdisplay-attribute?view=vs-2017 and more info on the ToString implementation for Double is over at: https://docs.microsoft.com/en-us/dotnet/api/system.double.tostring?view=netframework-4.7.2.
answered Mar 9 at 4:41
Andy SterlandAndy Sterland
1,062813
As @Amy mentioned you can use DebuggerDisplay to change the appearance of an object in the debugger. As double is a built in type you can't just change its implementation. For cases like this the debugger has a feature where it will load in DebuggerDisplay implementations externally that are implemented in autoexp.cs
- Open (as admin) the
autoexep.csfile which should be in a directory that looks like:C:Program Files (x86)Microsoft Visual Studio16PreviewCommon7PackagesDebuggerVisualizersOriginalobviously that will change with your VS version but if you search forautoexp.csyou'll find it. - In that file, add the code below:
[assembly: DebuggerDisplay(@"ToString(""F17""),nq", Target = typeof(Double))]that's going to tell the debugger to basically executeToString("F17")whenever it's displaying adouble. - Open a Developer Command Prompt as admin and navigate to where
autoexp.csis e.g.C:Program Files (x86)Microsoft Visual Studio16PreviewCommon7PackagesDebuggerVisualizersOriginal - Build the file with
csc /t:library autoexp.cs - Reload VS and run your scenario
You should then see something like:
More info on DebuggerDisplay is in our docs over at: https://docs.microsoft.com/en-us/visualstudio/debugger/using-the-debuggerdisplay-attribute?view=vs-2017 and more info on the ToString implementation for Double is over at: https://docs.microsoft.com/en-us/dotnet/api/system.double.tostring?view=netframework-4.7.2.
answered Mar 9 at 4:41
Andy SterlandAndy Sterland
1,062813
answered Mar 9 at 4:41
Andy SterlandAndy Sterland
1,062813
answered Mar 9 at 4:41
Andy SterlandAndy Sterland
1,062813
answered Mar 9 at 4:41
Andy SterlandAndy Sterland
1,062813
1,062813
Andy, I really appreciate your response. Thank you very much! But very sad that exponential format is the default now. Why default to exponential format which is so tricky? At first glance someone could think it's 5.63... The truth being that the value is less than 1! Very unfriendly to the eyes, just my two cents.
– Robert Smith
Mar 11 at 18:47
I don't think it's a case of it being difficult. The ToString implementation contains a way to visualize the a double in either way (and many others). Again, it's not VS that changed here but the implementation in .NET that changed the ToString implementation. You can look at the .NET Core version at: github.com/dotnet/corefx/blob/…. Which just calls into NumberFormat/NumberToDouble. I have no idea when/if that changed. It could be worth opening an issue on GitHub to find out more.
– Andy Sterland
Mar 11 at 21:07
Though, one reason for the change might simply be that a exponent and mantissa more accurately represent a double than a decimal. Given that the underlying storage is that way.
– Andy Sterland
Mar 12 at 6:13
add a comment |
Andy, I really appreciate your response. Thank you very much! But very sad that exponential format is the default now. Why default to exponential format which is so tricky? At first glance someone could think it's 5.63... The truth being that the value is less than 1! Very unfriendly to the eyes, just my two cents.
– Robert Smith
Mar 11 at 18:47
I don't think it's a case of it being difficult. The ToString implementation contains a way to visualize the a double in either way (and many others). Again, it's not VS that changed here but the implementation in .NET that changed the ToString implementation. You can look at the .NET Core version at: github.com/dotnet/corefx/blob/…. Which just calls into NumberFormat/NumberToDouble. I have no idea when/if that changed. It could be worth opening an issue on GitHub to find out more.
– Andy Sterland
Mar 11 at 21:07
Though, one reason for the change might simply be that a exponent and mantissa more accurately represent a double than a decimal. Given that the underlying storage is that way.
– Andy Sterland
Mar 12 at 6:13
Andy, I really appreciate your response. Thank you very much! But very sad that exponential format is the default now. Why default to exponential format which is so tricky? At first glance someone could think it's 5.63... The truth being that the value is less than 1! Very unfriendly to the eyes, just my two cents.
– Robert Smith
Mar 11 at 18:47
Andy, I really appreciate your response. Thank you very much! But very sad that exponential format is the default now. Why default to exponential format which is so tricky? At first glance someone could think it's 5.63... The truth being that the value is less than 1! Very unfriendly to the eyes, just my two cents.
– Robert Smith
Mar 11 at 18:47
I don't think it's a case of it being difficult. The ToString implementation contains a way to visualize the a double in either way (and many others). Again, it's not VS that changed here but the implementation in .NET that changed the ToString implementation. You can look at the .NET Core version at: github.com/dotnet/corefx/blob/…. Which just calls into NumberFormat/NumberToDouble. I have no idea when/if that changed. It could be worth opening an issue on GitHub to find out more.
– Andy Sterland
Mar 11 at 21:07
I don't think it's a case of it being difficult. The ToString implementation contains a way to visualize the a double in either way (and many others). Again, it's not VS that changed here but the implementation in .NET that changed the ToString implementation. You can look at the .NET Core version at: github.com/dotnet/corefx/blob/…. Which just calls into NumberFormat/NumberToDouble. I have no idea when/if that changed. It could be worth opening an issue on GitHub to find out more.
– Andy Sterland
Mar 11 at 21:07
Though, one reason for the change might simply be that a exponent and mantissa more accurately represent a double than a decimal. Given that the underlying storage is that way.
– Andy Sterland
Mar 12 at 6:13
Though, one reason for the change might simply be that a exponent and mantissa more accurately represent a double than a decimal. Given that the underlying storage is that way.
– Andy Sterland
Mar 12 at 6:13
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55069442%2fdisplay-double-in-immediate-window-different-in-vs2013-vs2017%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The
DebuggerDisplayattribute at the assembly level, maybe. Not a permanent setting, but semi-permanent.– Amy
Mar 8 at 19:31
Tools > Options > Debugging > General, tick the "Use the legacy C# and VB expression handlers" checkbox. It is permanent, but the message box does remind you that getting used to this minor quirk is easier today than it will be tomorrow.
– Hans Passant
Mar 9 at 9:28
It's best not to use the legacy C# and VB expression handlers. While changing that might change this behavior it has a far wider impact. While it's not ideal the workaround below is a better long term solution. If you'd like to change the default for all users open an issue on developer feedback. (Disclosure: I work on the VS debugger)
– Andy Sterland
Mar 9 at 18:08
Andy, you had it working so nice in vs2013! Why default to exponential format which is so tricky? At first glance someone could think it's 5.63... The truth being that the value is less than 1! Very unfriendly to the eyes, just my two cents.
– Robert Smith
Mar 11 at 18:45