我的Windows表单应用程序构建没有错误，但没有运行 [英] My windows forms application builds with no errors but doesnt run

问题描述

我有一个Windows项目，可以构建并报告没有错误，但是当按下它时它没有打开或运行应用程序并退出



我有什么试过：



我试图清理解决方案，但它没有解决问题

解决方案

< blockquote>然后你需要查看代码！



编译并不意味着你的代码是正确的！ ：笑：

将开发过程想象成编写电子邮件：成功编译意味着您使用正确的语言编写电子邮件 - 例如英语而不是德语 - 而不是电子邮件包含您的邮件想发送。



所以现在你进入第二阶段的发展（实际上它是第四或第五阶段，但你将在之后的阶段进入）：测试和调试。



首先查看它的作用，以及它与你想要的有何不同。这很重要，因为它可以为您提供有关其原因的信息。例如，如果程序旨在让用户输入一个数字并将其翻倍并打印答案，那么如果输入/输出是这样的：

输入预期输出实际输出
 1 2 1 
 2 4 4 
 3 6 9 
 4 8 16 

然后很明显问题出在将它加倍的位 - 它不会将自身加到自身上，或者将它乘以2，它会将它自身相乘并返回输入的平方。

所以，你可以查看代码和很明显，它在某处：

  private   int   Double （ int   value ） 
 {
  return   value  *  value ; 
} 

一旦你知道可能出现的问题，就开始使用teh调试器找出原因。



从Program.cs开始，在Main方法的第一行放置一个断点。

在调试器中运行你的应用程序它应该立即停在断点处，让你开始查看正在发生的事情。



想一想在执行代码之前代码中应该做什么，并将其与使用Step over按钮依次执行每一行时的实际情况进行比较。它符合您的期望吗？如果是这样，请转到下一行。

如果没有，为什么不呢？它有何不同？



这是一项非常值得开发的技能，因为它可以帮助你在现实世界和发展中。和所有技能一样，它只能通过使用改进！

引用：

当按下它开始时它不会打开或运行应用程序并退出

否则您无法快速了解发生了什么。所有你都知道，因为显示了一些结果，所以发生了一些事情。

只有一种方法可以知道发生了什么，使用调试器并逐行执行你的代码。 />


有一个工具可以让你看到你的代码在做什么，它的名字是调试器。它也是一个很好的学习工具，因为它向你展示了现实，你可以看到哪种期望与现实相符。

当你不明白你的代码在做什么或为什么它做它做的时候，答案就是答案是调试器。

使用调试器查看代码正在执行的操作。只需设置断点并查看代码执行情况，调试器允许您逐行执行第1行并在执行时检查变量。



调试器 - 维基百科，免费的百科全书 [ ^ ]

在Visual中调试C＃代码工作室 - YouTube [ ^ ]

调试器在这里向您展示您的代码正在做什么，您的任务是与它应该做什么进行比较。

调试器中没有魔法，它不是'找到错误，它只是帮助你。当代码没有达到预期的效果时，你就会接近一个错误。

I have a windows project that builds and reports no errors but when a press start it doesnt open or run the application and exits

What I have tried:

I have tried to clean the solution but it doesnt solve the problem

解决方案

Then you need to look at the code!

Compiling does not mean your code is right! :laugh:
Think of the development process as writing an email: compiling successfully means that you wrote the email in the right language - English, rather than German for example - not that the email contained the message you wanted to send.

So now you enter the second stage of development (in reality it's the fourth or fifth, but you'll come to the earlier stages later): Testing and Debugging.

Start by looking at what it does do, and how that differs from what you wanted. This is important, because it give you information as to why it's doing it. For example, if a program is intended to let the user enter a number and it doubles it and prints the answer, then if the input / output was like this:

Input   Expected output    Actual output
  1            2                 1
  2            4                 4
  3            6                 9
  4            8                16

Then it's fairly obvious that the problem is with the bit which doubles it - it's not adding itself to itself, or multiplying it by 2, it's multiplying it by itself and returning the square of the input.
So with that, you can look at the code and it's obvious that it's somewhere here:

private int Double(int value)
   {
   return value * value;
   }

Once you have an idea what might be going wrong, start using teh debugger to find out why.

Start with Program.cs, and put a breakpoint on the first line of the Main method.
Run your app in the debugger and it should immediately stop at the breakpoint, allowing you to start looking at what is going on.

Think about what each line in the code should do before you execute it, and compare that to what it actually did when you use the "Step over" button to execute each line in turn. Did it do what you expect? If so, move on to the next line.
If not, why not? How does it differ?

This is a skill, and it's one which is well worth developing as it helps you in the real world as well as in development. And like all skills, it only improves by use!

Quote:

when a press start it doesnt open or run the application and exits

No you are able to see fast enough to know what happen or not. All you can know, it is that something have happened because a result is displayed.
There is only 1 way to know what is going on, use the debugger and execute your code line by line.

There is a tool that allow you to see what your code is doing, its name is debugger. It is also a great learning tool because it show you reality and you can see which expectation match reality.
When you don't understand what your code is doing or why it does what it does, the answer is debugger.
Use the debugger to see what your code is doing. Just set a breakpoint and see your code performing, the debugger allow you to execute lines 1 by 1 and to inspect variables as it execute.

Debugger - Wikipedia, the free encyclopedia[^]
Debugging C# Code in Visual Studio - YouTube[^]
The debugger is here to show you what your code is doing and your task is to compare with what it should do.
There is no magic in the debugger, it don't find bugs, it just help you to. When the code don't do what is expected, you are close to a bug.

这篇关于我的Windows表单应用程序构建没有错误，但没有运行的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！