blocks|key|1174803|text|当项目处于调试模式时，解决方案不是。当我改变它的时候，它起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1174804|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

While the project was in debug mode, the solution was not. When I changed it, it worked.

blocks|key|960662|text|我在使用VS2010的时候遇到了这个问题。我的解决方案配置已选择(调试)。我通过取消选中项目属性下的Optimize+Code属性解决了这个问题。项目(右键单击)+=>属性=>+Build+(选项卡)=>取消选中优化代码|type|unstyled|depth|inlineStyleRanges|entityRanges|data|960663|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had this issue when I was using VS 2010. My solution configuration has (Debug) selected. I resolved this by unchecking the Optimize Code property under project properties.
Project (right Click)=> Properties => Build (tab) => uncheck Optimize code

blocks|key|1175898|text|对我来说，这发生在VS2017和VS2019。在我选择了“在模块加载时抑制JIT优化”选项后，它就停止了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1175899|​|1175900|📷|atomic|offset|length|1175901|1175902|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/044ae9a9baa349e219fb712a789eb3e6.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

For me it was happening in VS2017 and VS2019. 
It stopped happening after I selected the option "Suppressed JIT optimization on module load".

<a href="https://i.stack.imgur.com/J9jS6.png" rel="noreferrer"><img src="https://i.stack.imgur.com/J9jS6.png" alt="enter image description here"></a>

blocks|key|960894|text|在VS2013中，转到:+Tools+(工具)、->+Options+(选项)、->+Debugging+(调试)和->+(常规)，并启用'Use+managed+compatibility+mode(使用托管兼容模式)‘。这将禁用新函数求值行为。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|960895|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In VS2013 go to: Tools -> Options -> Debugging -> General and enable 'Use managed compatibility mode'. This disables the new function evaluation behavior.

blocks|key|1175437|text|尝试在debug+mode.If中运行您正在发布模式下运行，您将收到此消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1175438|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Try to run in debug mode.If you are running in release mode you will get this message.

blocks|key|961251|text|我的情况没有被上述任何一个答案所涵盖。我发现了以下内容:关于线程的MSDN+article，它解释了当停留在一些原始的本机线程操作中时，调试器无法访问数据。例如，当一个线程位于Task.Wait()上时，就会出现这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|961252|entityMap|0|LINK|mutability|MUTABLE|url|https://msdn.microsoft.com/en-us/magazine/jj891052.aspx^0|X|C|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

My situation was not covered by any of the above answers. I found the following: <a href="https://msdn.microsoft.com/en-us/magazine/jj891052.aspx" rel="noreferrer">MSDN article</a> on threading that explains that when stuck in some primitive native threading operations, the debugger can't access the data. As an example, when a thread is sitting on Task.Wait(), this comes up.

blocks|key|961360|text|我也有同样的问题。但在我的例子中，Debuggable属性是在我的项目的AssemblyInfo.cs文件中硬编码的，因此不会通过编译(覆盖)来编写。在删除指定Debuggable属性的行之后，它可以工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|961361|entityMap^0|H|A|10|F|28|A|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

I had the same problem. But in my case, the <code>Debuggable</code> attribute was hard coded in the <code>AssemblyInfo.cs</code> file of my project and therefore not (over-)written by compilation. It worked after removing the line specifying the <code>Debuggable</code> attribute.

blocks|key|960611|text|我在VS2008中也遇到了同样的问题。在我的案例中，它是通过solution-rebuild解决的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|960612|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same problem in VS2008. In my case it was solved via solution-rebuild.

blocks|key|1174764|text|除了提到的@Kragen之外，如果你正在调试一个web项目|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1174765|关闭visual+studio并尝试删除C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary+ASP.NET文件中的临时文件|1174766|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Apart from @Kragen mentioned, If you are debugging a web project

close the visual studio and try deleting the temporary files at C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files

blocks|key|1175207|text|您可以做的另一件事是，创建一个与优化的dll同名但扩展名为ini的文件，并在其中添加以下内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1175208|.NET框架调试控件|1175209|GenerateTrackingInfo=1|1175210|AllowOptimize=0|1175211|这将告诉JIT不要优化您的变量。|1175212|请注意，您仍然需要pdb，因此最终将得到如下内容:+yourDll.dll+yourDll.pdb+yourDll.ini|1175213|当您没有权限使用debug选项重新生成dll时，这种方法尤其适用。|1175214|http://www.hanselman.com/blog/DebugVsReleaseTheBestOfBothWorlds.aspx|offset|length|1175215|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|0|0|0|1W|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|11|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|13|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|14|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|15|8|@]|9|@$P|16|Q|17|1|18]]|A|$]]|$1|R|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|O]]]]

One other thing that you may do is, create a file with the same name as the dll that is optimized but with ini extension and add the following to it:

[.NET Framework Debugging Control] 
GenerateTrackingInfo=1 
AllowOptimize=0 

This will tell the JIT not to optimize your variables.

Note that you still need the pdb, so you will end up with something like this:
yourDll.dll
yourDll.pdb
yourDll.ini

This works specially well in scenarios when you don't have access to re-generate the dlls with debug option.

<a href="http://www.hanselman.com/blog/DebugVsReleaseTheBestOfBothWorlds.aspx" rel="nofollow">http://www.hanselman.com/blog/DebugVsReleaseTheBestOfBothWorlds.aspx</a>

blocks|key|960718|text|关于“优化代码”属性未被选中但代码仍被优化编译的问题:在尝试了所有方法后，最终帮助我的是选中相同设置页面(项目属性-调试)上的“启用非托管代码调试”复选框。它与代码优化没有直接关系，但启用此功能后，VS不再优化我的库，我可以进行调试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|960719|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Regarding the problem with "Optimize code" property being UNCHECKED yet the code still compiling as optimized: What finally helped me after trying everything was checking the "Enable unmanaged code debugging" checkbox on the same settings page (Project properties - Debug). It doesn't directly relate to the code optimization, but with this enabled, VS no longer optimizes my library and I can debug.

blocks|key|1174987|text|当我从一个测试床web应用程序中调试类库时，我也遇到了同样的问题。我在测试床中引用了发布版本，并将其设置为在类库属性中进行优化。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1174988|在类库属性中取消选中发布版本的optimise+code复选框，就在我写它的时候，已经解决了这个问题。|1174989|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had the same problem while debugging a class library from a testbed web app. I was referencing the release version in the testbed and that was set to be optimised in the class library properties.

Un-ticking the optimise code checkbox for the release version in the class library properties, just while I am writing it, has solved the issue.

blocks|key|1175366|text|我意识到这是一个较晚的答案，但我找到了另一种参考，以解决这个问题，可能会在未来帮助其他人。这篇web+page描述了如何设置一个环境变量(COMPLUS_ZapDisable=1)来阻止优化，至少我是这么做的！(不要忘记禁用Visual+Studio宿主进程的第二部分。)在我的例子中，这可能更相关，因为我是通过符号服务器调试外部DLL的，但我不确定。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1175367|entityMap|0|LINK|mutability|MUTABLE|url|http://www.cplotts.com/2009/01/07/disabling-optimizations-when-debugging-net-framework-source-code/^0|1B|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I realize this is a later answer, but I found another reference to a way to address this issue that might help others in the future. This <a href="http://www.cplotts.com/2009/01/07/disabling-optimizations-when-debugging-net-framework-source-code/" rel="nofollow">web page</a> describes setting an environment variable (COMPLUS_ZapDisable=1) that prevents optimization, at least it did for me! (Don't forget the second part of disabling the Visual Studio hosting process.) In my case, this might have been even more relevant because I was debugging an external DLL thru a symbol server, but I'm not sure.

blocks|key|1175679|text|我在Visual+Studio和MonoDevelop之间的一个F#项目中遇到了这个问题，这个项目可能起源于后者(我忘了)。在VS中，optimize框未被选中，但就调试器而言，似乎确实发生了优化。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1175680|在将项目文件的XML与健康项目的XML进行比较后，问题显而易见:健康项目有一个显式的<optimize>false</optimize>行，而糟糕的项目则完全缺少它。VS显然是从它的缺席中推断出优化被禁用了，而编译器却在做相反的事情。|offset|length|style|CODE|1175681|解决方案是将此属性添加到项目文件中，然后重新加载。|1175682|entityMap^0|0|16|Q|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I had this problem with an F# project that had been here and there between Visual Studio and MonoDevelop, perhaps originating in the latter (I forget). In VS, the optimize box was unchecked, yet optimization certainly seemed to be occuring as far as the debugger was concerned. 

After comparing the XML of the project file against that of a healthy one, the problem was obvious: the healthy project had an explicit <code>&lt;optimize&gt;false&lt;/optimize&gt;</code> line, whereas the bad one was missing it completely. VS was obviously inferring from its absence that optimization was disabled, while the compiler was doing the opposite.

The solution was to add this property to the project file, and reload.

blocks|key|1175718|text|当我迁移到Visual+Studio+2017时，我开始收到这条消息。我在这个页面上尝试的想法对我来说都不起作用。在另一篇文章中，我找到了这个建议，它确实起作用了--删除：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1175719|[assembly:+Debuggable(DebuggableAttribute.DebuggingModes.IgnoreSymbolStoreSequencePoints)]|code-block|syntax|javascript|1175720|...from你的AssemblyInfo文件。|1175721|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I started receiving this message when I migrated to Visual Studio 2017. None of the ideas on this page that I tried worked for me. On another post I found this suggestion and it DID work - remove:

<pre><code>[assembly: Debuggable(DebuggableAttribute.DebuggingModes.IgnoreSymbolStoreSequencePoints)]
</code></pre>

...from your AssemblyInfo file.

blocks|key|1175046|text|我在VS2010中也遇到了同样的问题。清理并重新构建解决方案，它起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1175047|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same issue in VS 2010. Cleaned-up and rebuild the solution and it worked.

blocks|key|961039|text|vickramds上面提到http://torulflundgren.blogspot.com.au/2010/03/cannot-obtain-value-of-local-or.html的评论，为我做到了这一点。我检查了一切-从本地bin文件夹中删除了所有dll、pdb文件，清理、重建，清除了所有临时ASP.NET文件的文件夹，确保设置了跟踪/调试标志，检查了DLL路径等。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|961040|对于受影响的项目，要将其放下以便不会丢失：|961041|项目属性-->构建-->高级-->调试信息:完整。|961042|在执行此操作之前，您需要检查是否选择了Debug配置，当然，除非您打算这样做。|961043|entityMap|0|LINK|mutability|MUTABLE|url|http://torulflundgren.blogspot.com.au/2010/03/cannot-obtain-value-of-local-or.html^0|D|2A|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

vickramds's comment above, referring to <a href="http://torulflundgren.blogspot.com.au/2010/03/cannot-obtain-value-of-local-or.html" rel="nofollow">http://torulflundgren.blogspot.com.au/2010/03/cannot-obtain-value-of-local-or.html</a> , did it for me. I checked everything - deleted all the dll, pdb files from local bin folders, Clean, Rebuild, cleared all folders of Temporary ASP.NET Files, ensured TRACE/DEBUG flags were set, checked the DLL paths, etc.

To put it down so it isn't lost, for the affected project(s):

Project Properties --> Build --> Advanced --> Debug Info: Full.

You want to check that you have the Debug configuration selected before you do this, unless of course, you intended otherwise.

blocks|key|1175562|text|如果您正在尝试调试ASP.NET项目，请确保该项目的Properties+>+Web+>+Servers下拉菜单设置为"IIS+Express“(除了检查此处的所有其他内容)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1175563|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you're trying to debug an ASP.NET project, ensure that the project's Properties > Web > Servers dropdown is set to "IIS Express" (in addition to checking everything else here).

blocks|key|1175813|text|我混合了c%2B%2B/cli+mfc扩展dll，即使是调试配置也进行了优化(参见VS2017模块窗口)。正如前面的回答所建议的，我更改了“在VS2013中，转到:工具、->选项、->调试和常规，并启用‘使用管理兼容模式’。这会禁用新的函数求值行为。”这一设置在VS+2017中也可以找到。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1175814|但这还不够，所以我还将UseDebugLibraries设置从另一个MFC应用程序的项目文件复制到了扩展dll项目文件。|1175815|++++<PropertyGroup+Condition="'$(Configuration)%7C$(Platform)'=='Debug%7CWin32'"+Label="Configuration">
++++++...
++++++<UseDebugLibraries>true</UseDebugLibraries>|code-block|syntax|javascript|1175816|然后重新构建，这样就解决了问题。|1175817|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I had mixed c++/cli mfc extension dlls, that were optimised even if debug configuration (seen from VS 2017 Modules window). 
As previous answer suggested I changed "In VS2013 go to: Tools -> Options -> Debugging -> General and enable 'Use managed compatibility mode'. This disables the new function evaluation behavior." That settings find also in VS 2017.

But that was not enough, so I also copied the UseDebugLibraries setting from another MFC app's project file to extension dll project file.

<pre><code> &lt;PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'" Label="Configuration"&gt;
 ...
 &lt;UseDebugLibraries&gt;true&lt;/UseDebugLibraries&gt;
</code></pre>

Then rebuild and that fixed the problem.

I am using Visual Studio 2010 in debug mode and I have "optimize code" unchecked. I can't quick watch (or hover on) any variable in the debugger. I get this error "Cannot evaluate expression because the code of the current method is optimized".

Even a line like: int i = -3, doing a quick watch on i, I get "Cannot obtain value of local or argument 'i' as it is not available at this instruction pointer, possibly because it has been optimized away."

This <a href="http://blogs.msdn.com/b/jmstall/archive/2005/11/15/funceval-rules.aspx" rel="noreferrer">link</a> referenced in a similar question doesn't seem to apply.

Is there a setting I am missing?

"Cannot evaluate expression because the code of the current method is optimized" in Visual Studio 2010

Visual Studio

服务器

编译器

调试器

Windows

我在调试模式下使用Visual Studio2010，并取消选中“优化代码”。我不能快速观察(或悬停)调试器中的任何变量。我得到这个错误“无法计算表达式，因为当前方法的代码是优化的”。甚至像这样的行: int i = -3，在i上做一个快速观察，我得到“无法获取local或参数'i‘的值，因为它在这个指令指针上不可用，可能是因为它已经被优化掉了。”类似问题中提到的这个似乎并不适用。有没有我遗漏的设

问Visual Studio 2010中的“无法计算表达式，因为当前方法的代码已优化”
EN

回答 19

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Visual Studio 2010中的“无法计算表达式，因为当前方法的代码已优化”EN

回答 19

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Visual Studio 2010中的“无法计算表达式，因为当前方法的代码已优化”
EN