blocks|key|318493|text|将Response+的第二个参数设为false，如下所示。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|318494|Response.Redirect(url,false);|code-block|syntax|javascript|318495|entityMap^0|1|8|A|D|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|D]]|E|@]|F|$]]|$1|G|3|H|5|I|7|S|8|@]|E|@]|F|$J|K]]|$1|L|3|-4|5|6|7|T|8|@]|E|@]|F|$]]]|M|$]]

Make second argument of <code>Response</code> false as shown below.

<pre><code>Response.Redirect(url,false);
</code></pre>

blocks|key|320249|text|在我调查的一个bug中，有一个Response.Redirect()，它在的意外位置中执行(读取:不适当的位置-在成员属性getter方法中)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|320250|如果您正在调试一个问题，并且遇到"Unable+to+evaluate+expression...“例外：|320251|320252|执行Response.Redirect()搜索，并将第二个参数endResponse+=设为false，或使用|ordered-list-item|CODE|320253|临时禁用重定向调用。|320254|320255|这令人沮丧，因为它似乎是在调试器上的“单步执行”到达该位置之前执行Redirect调用。|320256|entityMap^0|11|5|0|0|0|2|J|18|7|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|X|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|Y|8|@$9|Z|A|10|B|L]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|M|3|N|5|K|7|13|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|14|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|15|8|@]|D|@]|E|$]]|$1|R|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|S|$]]

In a bug I was investigating there was a Response.Redirect() and it was executing in an unexpected location (read: inappropriate location - inside a member property getter method).

If you're debugging a problem and experience the "Unable to evaluate expression..." exception:

<ol>
<li>Perform a search for <code>Response.Redirect()</code> and either make the second parameter endResponse = false, or</li>
<li>Temporarily disable the redirect call.</li>
</ol>

This was frustrating as it would appear to execute the Redirect call before the "step through" on the debugger had reached that location.

blocks|key|321235|text|我也有同样的问题，而且很棘手。对我来说，这是因为我使用的是Ext.Js+javascript库。如果在Ajax调用中访问的服务器端代码中执行response.redirect，就会出现问题。Ext.js对他们的Ext.Redirect方法有一个变通办法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|321236|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 same problem too, and it was tricky. For me, it was because I'm using Ext.Js javascript library. If you are doing a response.redirect in server-side code that you accessed in an Ajax call, there are problems. Ext.js has a workaround with their Ext.Redirect method.

blocks|key|3069598|text|Request.Redirect(url,false);|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|3069599|false指示当前页面的执行是否应该终止。|unstyled|offset|length|style|CODE|3069600|entityMap^0|0|0|5|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|N|8|@$G|O|H|P|I|J]]|9|@]|A|$]]|$1|K|3|-4|5|F|7|Q|8|@]|9|@]|A|$]]]|L|$]]

<pre><code>Request.Redirect(url,false);
</code></pre>

<code>false</code> indicates whether execution of current page should terminate.

blocks|key|323229|text|请检查此链接，了解此问题背后的原因和错误的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|323230|http://support.microsoft.com/kb/312629/EN-US/|offset|length|323231|Microsoft支持文章：|323232|如果您使用Response.End、Response.Redirect或Server.Transfer打印打印电子邮件，则会发生ThreadAbortException|323233|323234|若要解决此问题，请使用以下方法之一:对于Response.End，请调用HttpContext.Current.ApplicationInstance.CompleteRequest方法而不是Response.End，以绕过对Application_EndRequest事件的代码执行。|blockquote|323235|323236|对于Response.Redirect，使用重载Response.Redirect(String+url，bool+endResponse)，它将false传递给endResponse参数以取消对Response.End的内部调用。|323237|例如:+Response.Redirect+("nextpage.aspx"，false)；|323238|如果使用此解决方法，将执行Response.Redirect后面的代码。对于Server.Transfer，请改用Server.Execute方法。|323239|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|19|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@$D|13|E|14|1|15]]|A|$]]|$1|F|3|G|5|6|7|16|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|17|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|19|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1B|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1C|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1D|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|C]]]]

Please check this link for the reason behind this issue and solution for the error:
<a href="http://support.microsoft.com/kb/312629/EN-US/" rel="noreferrer">http://support.microsoft.com/kb/312629/EN-US/</a>
Microsoft Support Article:
PRB: ThreadAbortException Occurs If You Use Response.End, Response.Redirect, or Server.Transfer Print Print Email Email
<blockquote>
To work around this problem, use one of the following methods: For
Response.End, call the
HttpContext.Current.ApplicationInstance.CompleteRequest method instead
of Response.End to bypass the code execution to the
Application_EndRequest event.
For Response.Redirect, use an overload,
Response.Redirect(String url, bool endResponse)
that passes false for
the endResponse parameter to suppress the internal call to
Response.End.
For example: Response.Redirect (&quot;nextpage.aspx&quot;,
false);
If you use this workaround, the code that follows Response.Redirect is executed. For Server.Transfer, use the
Server.Execute method instead.
</blockquote>

blocks|key|3282711|text|您也可以使用Server.Execute|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3282712|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/ms525849%2528v=vs.90%2529.aspx^0|6|E|6|E|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

Also You Can Use <a href="http://msdn.microsoft.com/en-us/library/ms525849%28v=vs.90%29.aspx" rel="nofollow"><code>Server.Execute</code></a>

blocks|key|3282832|text|分辨率|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3282833|3282834|要解决此问题，请使用以下方法之一：|blockquote|3282835|3282836|3282837|对于|3282838|，请调用方法而不是Response.End以绕过对Response.End.事件的代码执行。对于|unordered-list-item|offset|length|style|BOLD|3282839|+，请使用重载E113)，它为E117+E117E218参数传递了false+E216以取消对suppress的内部调用例如：Response.Redirect+++("nextpage.aspx",+false);如果使用此解决方法，Response.Redirect后面的代码是executed.|CODE|3282840|For+，请改用方法。|3282841|3282842|3282843|症状|3282844|3282845|如果使用Response.End、Response.Redirect或Server.Transfer方法，则会发生ThreadAbortException异常。您可以使用try-catch语句来捕获此异常。|3282846|3282847|3282848|原因|3282849|3282850|+Response.End方法结束页面执行，并将执行转移到应用程序的事件管道中的Application_EndRequest事件。不执行Response.End后面的代码行。|3282851|3282852|此问题出现在Response.Redirect和Server.Transfer方法中，因为这两个方法都在内部调用Response.End。|3282853|3282854|状态|3282855|3282856|此行为是故意设计的。|3282857|3282858|3282859|属性|3282860|3282861|文章ID:+312629+-上次审查:2012年8月30日-修订版:+4.0|3282862|3282863|适用于的|3282864|3282865|2.0|3282866|Microsoft+1.1|3282867|
|3282868|Microsoft+|3282869|+ASP.NET+4.5|3282870|Microsoft+ASP.NET+4|3282871|Microsoft+ASP.NET+1.0|3282872|3282873|3282874|关键字：+kbprb异常处理kbprb+KB312629|3282875|来源：+PRB:+ThreadAbortException+Occurs+If+You+Use+Response.End,+Response.Redirect,+or+Server.Transfer|3282876|entityMap|0|LINK|mutability|MUTABLE|url|http://support.microsoft.com/kb/312629/en-us^0|0|0|0|0|0|0|9|C|P|C|0|1R|19|1R|19|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|3|0|0|D|0|0|0|A|0|0|C|0|0|J|0|0|L|0|0|0|0|S|0|0|3|4|2N|4|2N|0|0^^$0|@$1|2|3|4|5|6|7|2L|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|2M|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|2N|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|2O|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|2P|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|2R|8|@$M|2S|N|2T|O|P]|$M|2U|N|2V|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|L|7|2W|8|@$M|2X|N|2Y|O|P]|$M|2Z|N|30|O|S]]|9|@]|A|$]]|$1|T|3|U|5|L|7|31|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|32|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|33|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|34|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|35|8|@]|9|@]|A|$]]|$1|10|3|11|5|E|7|36|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|37|8|@]|9|@]|A|$]]|$1|13|3|-4|5|6|7|38|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|39|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|3A|8|@]|9|@]|A|$]]|$1|17|3|18|5|E|7|3B|8|@]|9|@]|A|$]]|$1|19|3|-4|5|6|7|3C|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|3D|8|@]|9|@]|A|$]]|$1|1C|3|-4|5|6|7|3E|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|3F|8|@]|9|@]|A|$]]|$1|1F|3|-4|5|6|7|3G|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|E|7|3H|8|@]|9|@]|A|$]]|$1|1I|3|-4|5|6|7|3I|8|@]|9|@]|A|$]]|$1|1J|3|-4|5|6|7|3J|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|3K|8|@]|9|@]|A|$]]|$1|1M|3|-4|5|6|7|3L|8|@]|9|@]|A|$]]|$1|1N|3|1O|5|E|7|3M|8|@]|9|@]|A|$]]|$1|1P|3|-4|5|6|7|3N|8|@]|9|@]|A|$]]|$1|1Q|3|1R|5|6|7|3O|8|@]|9|@]|A|$]]|$1|1S|3|-4|5|6|7|3P|8|@]|9|@]|A|$]]|$1|1T|3|1U|5|6|7|3Q|8|@$M|3R|N|3S|O|P]]|9|@]|A|$]]|$1|1V|3|1W|5|L|7|3T|8|@$M|3U|N|3V|O|P]]|9|@]|A|$]]|$1|1X|3|1Y|5|6|7|3W|8|@]|9|@]|A|$]]|$1|1Z|3|20|5|L|7|3X|8|@$M|3Y|N|3Z|O|P]]|9|@]|A|$]]|$1|21|3|22|5|L|7|40|8|@$M|41|N|42|O|P]]|9|@]|A|$]]|$1|23|3|24|5|L|7|43|8|@$M|44|N|45|O|P]]|9|@]|A|$]]|$1|25|3|26|5|L|7|46|8|@$M|47|N|48|O|P]]|9|@]|A|$]]|$1|27|3|-4|5|6|7|49|8|@]|9|@]|A|$]]|$1|28|3|-4|5|6|7|4A|8|@]|9|@]|A|$]]|$1|29|3|2A|5|6|7|4B|8|@$M|4C|N|4D|O|P]]|9|@]|A|$]]|$1|2B|3|2C|5|6|7|4E|8|@$M|4F|N|4G|O|P]|$M|4H|N|4I|O|P]]|9|@$M|4J|N|4K|1|4L]]|A|$]]|$1|2D|3|-4|5|6|7|4M|8|@]|9|@]|A|$]]]|2E|$2F|$5|2G|2H|2I|A|$2J|2K]]]]

<h2>Resolution</h2>

<blockquote>
 To work around this problem, use one of the following methods:
 
 <ul>
 <li>For <a href="http://msdn.microsoft.com/en-us/library/ms524629%28v=vs.90%29.aspx" rel="noreferrer">Response.End</a>, call the <a href="http://msdn.microsoft.com/en-us/library/system.web.httpcontext.applicationinstance%28v=vs.110%29.aspx" rel="noreferrer">HttpContext.Current.ApplicationInstance.CompleteRequest()</a>
 method instead of Response.End to bypass the code execution to the
 Application_EndRequest event.</li>
 <li>For <a href="http://msdn.microsoft.com/en-us/library/a8wa7sdt%28v=vs.110%29.aspx" rel="noreferrer">Response.Redirect</a>, use an overload, Response.Redirect(String url, bool endResponse) that passes false for the endResponse parameter to suppress the internal call to Response.End. For example: <code>Response.Redirect
 ("nextpage.aspx", false);</code> If you use this workaround, the code
 that follows Response.Redirect is executed.</li>
 <li>For <a href="http://msdn.microsoft.com/en-us/library/ms525800%28v=vs.90%29.aspx" rel="noreferrer">Server.Transfer</a>, use the <a href="http://msdn.microsoft.com/en-us/library/ms525849%28v=vs.90%29.aspx" rel="noreferrer">Server.Execute</a> method instead.</li>
 </ul>
</blockquote>

<h2>Symptoms</h2>

<blockquote>
 If you use the Response.End, Response.Redirect, or Server.Transfer
 method, a ThreadAbortException exception occurs. You can use a
 try-catch statement to catch this exception.
</blockquote>

<h2>Cause</h2>

<blockquote>
 The Response.End method ends the page execution and shifts the
 execution to the Application_EndRequest event in the application's
 event pipeline. The line of code that follows Response.End is not
 executed.
 
 This problem occurs in the Response.Redirect and Server.Transfer
 methods because both methods call Response.End internally.
</blockquote>

<h2>Status</h2>

<blockquote>
 This behavior is by design.
</blockquote>

<h2>Properties</h2>

<blockquote>
 Article ID: 312629 - Last Review: August 30, 2012 - Revision: 4.0
 
 Applies to
 
 <ul>
 <li>Microsoft ASP.NET 4.5</li>
 <li>Microsoft ASP.NET 4</li>
 <li>Microsoft ASP.NET 3.5</li>
 <li>Microsoft ASP.NET 2.0</li>
 <li>Microsoft ASP.NET 1.1</li>
 <li>Microsoft ASP.NET 1.0</li>
 </ul>
 
 Keywords: kbexcepthandling kbprb KB312629
</blockquote>

Source: <a href="http://support.microsoft.com/kb/312629/en-us" rel="noreferrer">PRB: ThreadAbortException Occurs If You Use Response.End, Response.Redirect, or Server.Transfer</a>

blocks|key|318572|text|使用下面的代码解决这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|318573|string+path+=+AppDomain.CurrentDomain.BaseDirectory.ToString()+%2B+"Uploadfile\\"+%2B+fileName;
System.IO.FileStream+fs+=+new+System.IO.FileStream(path,+System.IO.FileMode.Open,+System.IO.FileAccess.Read);
byte[]+bt+=+new+byte[fs.Length];
fs.Read(bt,+0,+(int)fs.Length);
fs.Close();
Response.ContentType+=+"application/x-unknown/octet-stream";
Response.AppendHeader("Content-Disposition",+"attachment;+filename=\""+%2B+fileName;%2B+"\"");
try
{
++++if+(bt+!=+null)
++++{
++++++++System.IO.MemoryStream+stream1+=+new+System.IO.MemoryStream(bt,+true);
++++++++stream1.Write(bt,+0,+bt.Length);
++++++++Response.BinaryWrite(bt);
++++++++//Response.OutputStream.Write(bt,+0,+(int)stream1.Length);
++++++++Response.Flush();
++++++++//+Response.End();
++++}
}
catch+(Exception+ex)
{
++++Response.Write(ex.Message);
++++throw+ex;
}
finally
{
++++Response.End();
}|code-block|syntax|javascript|318574|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

use this code solve the problem:

<pre><code>string path = AppDomain.CurrentDomain.BaseDirectory.ToString() + "Uploadfile\\" + fileName;
System.IO.FileStream fs = new System.IO.FileStream(path, System.IO.FileMode.Open, System.IO.FileAccess.Read);
byte[] bt = new byte[fs.Length];
fs.Read(bt, 0, (int)fs.Length);
fs.Close();
Response.ContentType = "application/x-unknown/octet-stream";
Response.AppendHeader("Content-Disposition", "attachment; filename=\"" + fileName;+ "\"");
try
{
 if (bt != null)
 {
 System.IO.MemoryStream stream1 = new System.IO.MemoryStream(bt, true);
 stream1.Write(bt, 0, bt.Length);
 Response.BinaryWrite(bt);
 //Response.OutputStream.Write(bt, 0, (int)stream1.Length);
 Response.Flush();
 // Response.End();
 }
}
catch (Exception ex)
{
 Response.Write(ex.Message);
 throw ex;
}
finally
{
 Response.End();
}
</code></pre>

blocks|key|321303|text|就像我在使用Response.End()异步触发器按钮时遇到的问题一样|type|unstyled|depth|inlineStyleRanges|entityRanges|data|321304|<asp:AsyncPostBackTrigger+ControlID="btn_login"+/>|code-block|syntax|javascript|321305|在更新面板中。我换回了普通的帖子，虽然不是最好的，但还是起作用了。|321306|<asp:PostBackTrigger+ControlID="btn_login"+/>.+|321307|因为我只是在页面上重定向，所以这是一个可行的解决方案。|321308|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Just encase someone else ran into the issues I did I was using Response.End() an async trigger button 

<pre><code>&lt;asp:AsyncPostBackTrigger ControlID="btn_login" /&gt;
</code></pre>

in an update panel. I switched to regular post back not the best but it worked. 

<pre><code>&lt;asp:PostBackTrigger ControlID="btn_login" /&gt;. 
</code></pre>

Since I was only redirecting on the page this was a viable solution.

blocks|key|323328|text|如果您正在使用更新面板和链接按钮来下载excel，请在面板内部添加回发触发器|type|unstyled|depth|inlineStyleRanges|entityRanges|data|323329|<asp:PostBackTrigger+ControlID="lnkTemplate"+/>+|code-block|syntax|javascript|323330|和在Code+click单击事件中|323331|string+ServerPath+=+System.Configuration.ConfigurationManager.AppSettings["FilePath"]+%2B+"Template.xlsx";
System.IO.FileInfo+file+=+new+System.IO.FileInfo(Server.MapPath(ServerPath));

HttpContext.Current.Response.Clear();
HttpContext.Current.Response.AddHeader("Content-Disposition",+"attachment;+filename="+%2B+file.Name);
HttpContext.Current.Response.AddHeader("Content-Length",+file.Length.ToString());
++++++++++++HttpContext.Current.Response.ContentType+=+"application/octet-stream";
+HttpContext.Current.Response.TransmitFile(file.FullName);
+HttpContext.Current.Response.Flush();
+HttpContext.Current.ApplicationInstance.CompleteRequest();|323332|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

If you are using Update Panel and link button to download excel is inside the panel than add postback trigger

<pre><code>&lt;asp:PostBackTrigger ControlID="lnkTemplate" /&gt; 
</code></pre>

and in Code behind inside click event

<pre><code>string ServerPath = System.Configuration.ConfigurationManager.AppSettings["FilePath"] + "Template.xlsx";
System.IO.FileInfo file = new System.IO.FileInfo(Server.MapPath(ServerPath));

HttpContext.Current.Response.Clear();
HttpContext.Current.Response.AddHeader("Content-Disposition", "attachment; filename=" + file.Name);
HttpContext.Current.Response.AddHeader("Content-Length", file.Length.ToString());
 HttpContext.Current.Response.ContentType = "application/octet-stream";
 HttpContext.Current.Response.TransmitFile(file.FullName);
 HttpContext.Current.Response.Flush();
 HttpContext.Current.ApplicationInstance.CompleteRequest();
</code></pre>

blocks|key|3282993|text|使用这个，对我来说总是有效的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3282994|Response.Redirect(Request.RawUrl,+false);|code-block|syntax|javascript|3282995|这里，Response.Redirect(Request.RawUrl)只是重定向到当前上下文的url，而第二个参数"false“表示是否为endResponse。|3282996|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|$]]

Use this, works for me always.

<pre><code>Response.Redirect(Request.RawUrl, false);
</code></pre>

Here, Response.Redirect(Request.RawUrl) simply redirects to the url of the current context, while the second parameter "false" indicates to either endResponse or not.

blocks|key|3069813|text|当你在mvc中有一个带有一些验证规则的模型的剃刀页面时，这个问题可能就是一个结果。当您从表单发布时，忘记在某些字段中显示验证错误，则可能会出现此消息。推测:这可能是因为你发布的方法不同，并且被其他来源使用，或者驻留在与服务于原始请求的方法不同的位置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3069814|因此，因为它是不同的，所以它不能返回到原始页面来显示或处理错误，因为执行和模型状态不同(类似于此)。|3069815|发现它可能有点困难，但很容易犯错误。确保你的接收方法确实验证了所有可能的发帖方式。|3069816|例如，即使您的服务器端验证实际上使您无法在表单中写入大于您的验证所允许的最大值的字符串，也可能有其他方式和来源发送到接收方法。|3069817|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

This problem may be a result when you have a razor page in mvc with a model that has some validation rules. When you post from a form and you forget to display validation errors on some field, then this message might come up. Speculation: this could be if the method you are posting to is different and used by other sources or resides in a different place than the method serving the original request.
So because it's different, it can't return to the original page to display or handle the errors because the excecution and model state is not the same (something like that).
It can be slightly difficult to discover, but easy mistake to do. Make sure your recieving method actually validates all possible ways to post to it.
for instance, even if you have serverside validation that actually makes it impossible to write in the form a string that is bigger than the max allowed by your validation, there could be other ways and sources that post to the recieving method.

I am getting the error:

<blockquote>
 Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack.
</blockquote>

I have redirected to a new page in repeater's itemcommand event. The error occurs at the line:

<pre><code>string url = "~/Galleries/AlbumImageList.aspx?UId=" + this.UserId.ToString() + "&amp;AlbumId=" + e.CommandArgument.ToString();
Response.Redirect(url);
</code></pre>

Can anybody please help me? Is anything wrong there?
The <code>_COMPlusExceptionCode</code> is -<code>532459699</code>.

Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack

服务器

调试器

我得到了一个错误：无法计算表达式，因为代码已优化或本机框架位于调用堆栈的顶部。我在repeater的itemcommand事件中重定向到了一个新页面。错误发生在以下行：string url = "~/Galleries/AlbumImageList.aspx?UId=" + this.UserId.ToString()...

问无法计算表达式，因为代码已优化或本机框架位于调用堆栈的顶部
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法计算表达式，因为代码已优化或本机框架位于调用堆栈的顶部EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法计算表达式，因为代码已优化或本机框架位于调用堆栈的顶部
EN