blocks|key|131625|text|Application.Run()用于应用程序的启动，而MainForm是应用程序的一部分，MainForm()).ShowDialog()仅用于显示应用程序。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|131626|Application.Run()是应用程序的entry+point。与某些类的Main()方法或WebApplication的ApplicationStart()方法相同|131627|有不同的重载，其中一个重载没有参数。该方法无需初始表单即可启动应用程序。|131628|entityMap^0|0|H|S|8|1A|O|0|0|H|N|B|14|6|1S|I|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|11|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|K|$]]

<code>Application.Run()</code> is for the start of application while <code>MainForm</code> is part of the application and <code>MainForm()).ShowDialog()</code> used to display it only.

<code>Application.Run()</code> is the <code>entry point</code> for your Application. same as <code>Main()</code> method is for some class or <code>ApplicationStart()</code> for a WebApplication

<a href="http://msdn.microsoft.com/en-us/library/system.windows.forms.application.run.aspx" rel="nofollow noreferrer">Application.Run()</a> has different overloads, one of which is without parameters. That Method starts application without an initial form.

blocks|key|1226187|text|来自MSDN：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1226188|1226189|此方法向Closed事件的mainForm参数添加事件处理程序。事件处理程序调用ExitThread来清理应用程序。|blockquote|1226190|1226191|1226192|http://msdn.microsoft.com/en-us/library/ms157902.aspx|offset|length|1226193|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|0|1H|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|U|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@$J|Y|K|Z|1|10]]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|I]]]]

From MSDN:

<blockquote>
 This method adds an event handler to
 the mainForm parameter for the Closed
 event. The event handler calls
 ExitThread to clean up the
 application.
</blockquote>

<a href="http://msdn.microsoft.com/en-us/library/ms157902.aspx" rel="noreferrer">http://msdn.microsoft.com/en-us/library/ms157902.aspx</a>

blocks|key|131687|text|一个关键的区别是ShowDialog通常是一个模式对话框。如果您想创建一个用户友好的工具集，您不希望它由模式对话框组成。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|131688|此外，Application.Run()接受的不仅仅是表单。它有一些重载。|131689|至于你的申请，我认为它并不重要。Application.Run对我来说很有意义，因为它表示实际应用程序的开始。|131690|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

One key difference is that ShowDialog is usually a modal Dialog. If you wanted to create a user-friendly toolset, you would not want it to be comprised of modal dialog boxes.

Also, Application.Run() accepts more than just a form. It has a few overloads. 

As for your application, I do not think it matters much. Application.Run makes sense to me because it denotes the start of your actual Application.

blocks|key|2635789|text|Application.Run(Form)在当前线程上启动消息循环并显示指定的表单。消息循环使窗体能够接收Windows消息(例如，按键、鼠标单击、绘图无效)，以使其显示为响应式并与用户进行交互。当您在Form实例上调用ShowDialog()时，它实际上做了类似的事情，并为调用ShowDialog的表单创建了一个模态消息循环。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2635790|这两个调用之间没有太大区别。Application.Run确实添加了一些额外的事件处理，使您能够在关闭主窗体时对资源进行一些整理(请参阅Application.ThreadExit)。|2635791|启动WinForms应用程序的推荐方式是使用Application.Run，但我怀疑这更像是一种惯例，而不是规则。使用Application.Run的最大原因是您想要打开多个非模式表单。您可以使用以下命令执行此操作：|2635792|new+Form().Show();
new+Form().Show();
Application.Run();|code-block|syntax|javascript|2635793|使用ShowDialog()方法无法实现这一点，因为其中一个表单必须是模态的。|2635794|2635795|至于您的问题，如果登录成功，如何显示登录表单和主表单，我认为您所拥有的已经很好了：|2635796|if+(new+LoginForm().ShowDialog()+==+DialogResult.OK)
{
++++Application.Run(new+MainForm());
}|2635797|另一种方法是自己进行检测，如果登录成功，则在LoginForm的关闭事件中打开MainForm实例。|2635798|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.windows.forms.application.threadexit.aspx^0|0|L|2T|4|32|C|3W|A|0|E|F|1W|M|0|0|M|F|1N|F|0|0|2|C|0|0|0|0|M|9|13|8|0^^$0|@$1|2|3|4|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]|$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1E|8|@$9|1F|A|1G|B|C]]|D|@$9|1H|A|1I|1|1J]]|E|$]]|$1|H|3|I|5|6|7|1K|8|@$9|1L|A|1M|B|C]|$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|1P|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1Q|8|@$9|1R|A|1S|B|C]]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1T|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1U|8|@]|D|@]|E|$]]|$1|T|3|U|5|L|7|1V|8|@]|D|@]|E|$M|N]]|$1|V|3|W|5|6|7|1W|8|@$9|1X|A|1Y|B|C]|$9|1Z|A|20|B|C]]|D|@]|E|$]]|$1|X|3|-4|5|6|7|21|8|@]|D|@]|E|$]]]|Y|$Z|$5|10|11|12|E|$13|14]]]]

<code>Application.Run(Form)</code> starts a message loop on the current thread and displays the specified form. The message loop enables the form to receive Windows messages (eg, key presses, mouse clicks, paint invalidations) to allow it to appear responsive and have interaction with the user. When you call <code>ShowDialog()</code> on a <code>Form</code> instance, it actually does a similar thing and creates a modal message loop for the form on which <code>ShowDialog</code> has been called.

There is not much difference between the two calls. <code>Application.Run</code> does add some extra event handling enabling you to do some tidying up of resources when the main form is closed (see <a href="http://msdn.microsoft.com/en-us/library/system.windows.forms.application.threadexit.aspx" rel="noreferrer">Application.ThreadExit</a>). 

The recommended way to start WinForms applications is using <code>Application.Run</code>, but I suspect this is more of a convention than a rule. The biggest reason to use <code>Application.Run</code> is if you want to open multiple non-modal forms. You can do this using:

<pre><code>new Form().Show();
new Form().Show();
Application.Run();
</code></pre>

You could not achieve this using the <code>ShowDialog()</code> method as one of the forms would have to be modal.

<hr>

As for your question of how to show a login form and then the main form if the login is successful, I think what you have is fine:

<pre><code>if (new LoginForm().ShowDialog() == DialogResult.OK)
{
 Application.Run(new MainForm());
}
</code></pre>

The alternative is to do the plumbing yourself and open an instance of <code>MainForm</code> in the closing event of the <code>LoginForm</code> if the login was successful.

blocks|key|877783|text|从我的测试中，我注意到了以下主要区别：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|877784|当使用Application.Run时，窗体的Close按钮(红色X)返回DialogResult.None；但是，当使用ShowDialog时，Close按钮生成DialogResult.Cancel。|877785|这对你来说很重要吗？在我的代码中，我测试了DialogResult.Cancel以确定应用程序的退出代码。当使用红色的X关闭表单时，它被破坏了。我现在测试DialogResult.OK以指示成功退出。|877786|++++++++return+myForm.DialogResult+==+DialogResult.OK+?+0+:+1;|code-block|syntax|javascript|877787|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|6|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|P|8|@]|9|@]|A|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

From my testing, I noticed this main difference: 

When Application.Run is used, the form's Close button (red X) returns DialogResult.None; however, when ShowDialog is used, the Close button produces DialogResult.Cancel.

Does this matter to you? In my code, I was testing for DialogResult.Cancel to determine the exit code of my application. That was broken when the red X was used to close the form. I now test for DialogResult.OK to indicate a successful exit.

<pre><code> return myForm.DialogResult == DialogResult.OK ? 0 : 1;
</code></pre>

blocks|key|1226343|text|The+documentation+of+the+overload|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1226344|public+static+void+Run(
++++ApplicationContext+context+);|code-block|syntax|javascript|1226345|有一个整洁的例子，它采用了不同的方法，也涉及到两个表单。|1226346|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/ms157901.aspx^0|4|T|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

The <a href="http://msdn.microsoft.com/en-us/library/ms157901.aspx" rel="nofollow">documentation of the overload</a>

<pre><code>public static void Run(
 ApplicationContext context );
</code></pre>

has a neat example with a different approach that involves two forms as well.

blocks|key|2635891|text|有关区别的更具体的示例：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2635892|如果您的主窗体是MDI窗体，则单击“关闭”按钮(右上角的“x”或Alt-F4)时的行为会因显示窗体的方法而异。|2635893|使用Application.Run(mainForm)时，先运行子窗体的关闭事件，然后再运行主窗体的关闭事件。|offset|length|style|CODE|2635894|使用mainForm.ShowDialog时，将运行主窗体的关闭事件，而不运行子窗体的关闭事件。|2635895|entityMap^0|0|0|2|P|0|2|J|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@$F|Q|G|R|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@$F|T|G|U|H|I]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|M|$]]

For a more concerete example of a difference:

If your main form is an MDI form, then the behavior on clicking the close button (the 'x' in the upper right, or Alt-F4) is different depending on which method you use to show the form.

With <code>Application.Run(mainForm)</code>, the closing event of the child forms run, then the main form's closing event runs.

With <code>mainForm.ShowDialog</code>, the closing event of the main form runs, and the closing event of the child forms do not run.

blocks|key|131773|text|从我的测试中，我注意到在DialogResult中使用Application.Run按钮并不会关闭表单(OnFormClosing未被点击)，而在ShowDialog中，带有DialogResult的按钮会点击OnFormClosing，而close则会关闭表单。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|131774|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|$]]

From my testing I notice that using Application.Run buttons with DialogResult does not close the form (OnFormClosing is not hit) compare to ShowDialog in which the buttons with DialogResult hit OnFormClosing and the close the form.

In my application I want to show a login form first and then the main form if the login has been successful. Currently I'm doing it something like this:

<pre><code>var A = new LoginForm();
if ( A.ShowDialog() == DialogResult.OK )
 Application.Run(new MainForm());
</code></pre>

But then I started wondering - what's the point of the <code>Application.Run()</code>? Why not just do <code>(new MainForm()).ShowDialog()</code> as well? What's the difference? And what would be the correct way to achieve what I want?

What's the difference between Application.Run() and Form.ShowDialog()?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在我的应用程序中，如果登录成功，我希望首先显示登录表单，然后显示主表单。目前，我正在做这样的事情：var A = new LoginForm();if ( A.ShowDialog() == DialogResult.OK )    Application.Run(new MainForm());但是后来我开始想-- ...

问Application.Run()和Form.ShowDialog()有什么区别？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Application.Run()和Form.ShowDialog()有什么区别？EN