Quote:I would highly appreciate if someone can point me to right direction to understand this "prime numbers" logic.
This prime checking logic is extremely slow.
Think about it, when you check if 97 is a prime, by hand (with just a calculator), once you know that 2 is not a factor, will you check 4, 6, 8, 10, 12 ... ?
When will you stop ? Why ? will you check 95 ? 93 ? 91 ? 89 ? ...
Advice: make a function 'isprime', it will simplify code.
Quote:Could you please tell me how second loop or the if statement breaks here?
How about watching the code as it performs ?
Your code do not behave the way you expect, or you don't understand why !
There is an almost universal solution: Run your code on debugger step by step, inspect variables.
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 know what your cpde is supposed to do, it don't find bugs, it just help you to by showing you what is going on. When the code don't do what is expected, you are close to a bug.
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
Mastering Debugging in Visual Studio 2010 - A Beginner's Guide
Basic Debugging with Visual Studio 2010 - YouTube
Debugging C# Code in Visual Studio - YouTube
The debugger is here to only show you what your code is doing and your task is to compare with what it should do.