blocks|key|2048672|text|我相信您必须关闭/停止本地调试服务器才能再次触发Application_Start()事件……你应该能够在系统托盘中右击它，然后选择“停止”。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2048673|entityMap^0|O|J|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I believe you have to shutdown/stop the local debugging server in order for the <code>Application_Start()</code> event to fire again... you should be able to right click on it in the system tray and choose "Stop".

blocks|key|2048699|text|我发现了问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2048700|这个MVC应用程序是一个更大的解决方案的一部分，在这个解决方案中，我曾经为一个x86环境(我正在运行x64)设置了另一个项目。当我这样做的时候，显然所有其他项目-即使是那些后来添加的项目-都被设置为不在Ctrl%2BShift%2BB上构建，我想这就是调试器没有命中我的断点的原因。|offset|length|style|CODE|2048701|解决方案：|2048702|进入解决方案生成属性(右键单击Solution，选择属性，然后在左侧菜单上选择build+)，并选中列表中项目名称旁边的Build复选框。|2048703|entityMap^0|0|2T|C|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

I found the problem:

This MVC application was part of a larger solution, in which I had at one point set another project to build for an x86 environment (I'm running x64). When I did that, apparently all other projects - even those added later - were set not to build on <code>Ctrl+Shift+B</code>, and I suppose that's why the debugger didn't hit my breakpoint.

Solution:

Go into the solution build properties (right-click Solution, select properties, and select Build on the menu on the left), and put a check in the Build checkbox next to the project name in the list.

blocks|key|1834588|text|向Application_Start()添加System.Diagnostics.Debugger.Break();。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1834589|这将强制使用断点。|1834590|这一行应该被注释掉，以避免断点的发生和#ifdef+debug，以确保永远不会进入生产环境。|1834591|注意:这是IIS的问题。自从我写了这个答案以来，事情已经发生了变化，您可以通过使用其他服务器来避免这样做，例如IIS+Express。|1834592|entityMap^0|1|J|M|10|0|0|J|C|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|W|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|M|$]]

Add a <code>System.Diagnostics.Debugger.Break();</code> to <code>Application_Start()</code>.
 This will force a breakpoint.
This line should be commented out to avoid the breakpoint to happen and <code>#ifdef debug</code> to get sure never gets to production.
NOTE: this is a problem with IIS. Since I wrote this answer, things have changed, and you can avoid doing this by using other servers, like IIS Express.

blocks|key|1834602|text|在我的例子中，问题出在椅子和键盘之间--重命名mvc项目程序集后，我忘记更新Global.asax以指向正确的类。因此，在Global.asax中检查“继承”(在visual+studio中，右键单击Global.asax+->视图标记)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1834603|<%25@+Application+Codebehind="Global.asax.cs"+
++Inherits="Monster.MgsMvc.Web.MvcApplication"+
++Language="C#"+%25>|code-block|syntax|javascript|1834604|如果它确实与您的Global.asax.cs类/名称空间声明相匹配|1834605|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|$]]

In my case the problem was between chair and keyboard - after renaming mvc project assembly, I forgot to update Global.asax to point to the correct class. So check the "Inherits" in Global.asax (in visual studio right-click on Global.asax -> View Markup)

<pre><code>&lt;%@ Application Codebehind="Global.asax.cs" 
 Inherits="Monster.MgsMvc.Web.MvcApplication" 
 Language="C#" %&gt;
</code></pre>

if it really matches your Global.asax.cs class/namespace declaration

blocks|key|2048776|text|下面的技巧对我很有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2048777|简单的解决方法是在附加调试器后触摸global.asax，以强制回收应用程序。然后，在下一次请求期间，将命中您在Application_Start上设置的断点。|2048778|我在这里找到了这个：|2048779|http://connect.microsoft.com/VisualStudio/feedback/details/634919/cannot-debug-application-start-event-in-global-asax|offset|length|2048780|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|39|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@$H|U|I|V|1|W]]|A|$]]|$1|J|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|G]]]]

Below technique worked for me: 
Simple workaround is to touch global.asax after the debugger is attached in order to force an application recycle. Then during the next request, the break point that you set on Application_Start will be hit.

I found this here: <a href="http://connect.microsoft.com/VisualStudio/feedback/details/634919/cannot-debug-application-start-event-in-global-asax" rel="nofollow">http://connect.microsoft.com/VisualStudio/feedback/details/634919/cannot-debug-application-start-event-in-global-asax</a>

blocks|key|1834641|text|我今天遇到了同样的问题，正在使用Local+IIS。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1834642|我相信这是因为页面加载的方式。您所需要做的就是在Application_Start中设置一个断点。运行应用程序(在我的例子中，它进入登录屏幕)，然后转到web.config。编辑它-通过添加一些空格。然后，Browser.that中的刷新将命中Application_Start上的断点。|1834643|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 hit with the same problem today and was using Local IIS.

I believe this arises because because of the way page is loaded. 
All you need to do is, put a breakpoint in Application_Start. Run the application(In my case, it took to Login Screen ) and then go to web.config. Edit it - by adding some spaces. and then refresh in Browser.that will hit the breakpoint on Application_Start.

blocks|key|2048817|text|问题是Application_Start()首先触发，然后再附加调试器。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2048818|因此，我们的目标是做一些事情，使Application_Start()在其仍在运行时再次触发。出于调试目的，只需像往常一样运行调试器，然后编辑(例如添加新行)并保存web.config文件。|2048819|entityMap^0|3|J|0|G|J|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

The problem is <code>Application_Start()</code> triggers first then the debugger attaches.

So the goal is to do something that would cause <code>Application_Start()</code> to trigger again while its still running. For debugging purposes, just run the debugger like you normally do then edit (eg add a newline) and save the web.config file.

blocks|key|2048827|text|我刚刚遇到了这个问题，并在项目属性->+web中从Local+IIS切换到IIS+Express来解决这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2048828|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've just had this problem and swapped from Local IIS to IIS Express in project properties -> web to sort it out

blocks|key|2048943|text|project+->属性->+web|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2048944|勾选“本地代码”。|2048945|​|2048946|📷|atomic|offset|length|2048947|2048948|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/9a01410a601c7ebfe0cefca932301562.png|imageAlt^0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@$I|Y|J|Z|1|10]]|A|$]]|$1|K|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

project -> property -> web 

check "Native code".

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

I currently have the following routines in my <code>Global.asax.cs</code> file:

<pre><code>public static void RegisterRoutes(RouteCollection routes)
{
 routes.IgnoreRoute("{resource}.axd/{*pathInfo}");
 routes.MapRoute(
 "Default", 
 "{controller}/{action}/{id}", 
 new { controller = "Arrangement", action = "Index", id = "" }
 );
}

protected void Application_Start()
{
 RegisterRoutes(RouteTable.Routes);
 // Debugs the routes with Phil Haacks routing debugger (link below)
 RouteDebug.RouteDebugger.RewriteRoutesForTesting(RouteTable.Routes);
}
</code></pre>

<a href="http://haacked.com/archive/2008/03/13/url-routing-debugger.aspx" rel="noreferrer">Routing debugger</a>...

When I hit <code>F5</code>, the application fires up and unless I have a view named <code>Index.aspx</code> in the <code>~/Views/Home/</code> folder, I get the "View missing" error message, although I have re-defined the default route and removed the <code>HomeController</code>. I would expect to get the routing debugger, and if not that at least a request for <code>~/Views/Arrangement/Index.aspx</code>. 
A breakpoint on <code>RegisterRoutes(Routetable.Routes);</code> is never hit when debugging.

I have tried building, rebuilding, restarting VS, cleaning, rebuilding again etc, but nothing seems to work. Why doesn't the application run the current version of the code?

Why does not the Application_Start() event fire when I debug my ASP.NET MVC app?

服务器

调试器

路由

目前，我的Global.asax.cs文件中有以下例程：public static void RegisterRoutes(RouteCollection routes){    routes.IgnoreRoute("{resource}.axd/{*pathInfo}");    routes.MapRoute( ...

问当我调试我的ASP.NET MVC应用程序时，为什么Application_Start()事件不触发？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问当我调试我的ASP.NET MVC应用程序时，为什么Application_Start()事件不触发？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问当我调试我的ASP.NET MVC应用程序时，为什么Application_Start()事件不触发？
EN