Actually, "Processor Devil" has given you a very wise suggestion and I fully concur with his advice (I have expressed my views candidly on the subject, in the past). He did not repeat the answer to your immediate problem because he probably noticed that I had already mentioned it. His advice is a general suggestion to those starting out with programming. All the Scope and other programming principles that could possibly apply in the context of Windows forms also apply in the case of console applications. The advantage in case of Console apps is that nothing is obfuscated from the developer by the IDE. Windows forms require a lot of (non-apparent) background plumbing to run which is all done by the IDE and it is essential to understand that if you want to become proficient.
I myself started my learning of .NET by building console apps games. This kept up my interest while I was learning the language as well as the implementation of OOP principles. On Nov 13, 5:56 pm, Greg <[email protected]> wrote: > Yo PD, > Thanks for the reply! > I get what you are saying, but I respectfully disagree. > If anything, to me coding using windows forms and buttons really > breaks up your code and makes you have to deal with scope, which is > fundamental to everything else. > Also, it never addresses the real issue of scope that I was having. > Slapping me upside the head and saying, your reference to an object is > still a VARIABLE, so quit treating it like an object would have taught > me more than saying I shouldn't being programming in Windows Forms > yet. > But again, I do thank you for taking the time to reply at all and I > welcome your help in the future! >
