Yes, it's a bit confusing that Microsoft uses Console.WriteLine to write to the Output window.
Writing there is useful for displaying debugging messages but I hardly ever make console applications. They're just not that interesting. Some authors have you start by making them because that lets them ignore the user interface so they can just cover things like variables and loops, but I think that approach is backward. The large majority of Windows applications use a user interface not a console window so why should you start by learning something you'll hardly ever use again? My opinion, anyway ;-)
Quote:
The scenario that I thought you meant for the exercise was to have a console application pop-up from the windows form application when the "List Items" button is pressed.
|
The point of that exercise was really to just let you loop through the items in a list. A more realistic example would create a printout showing the items in a bill of sale, but printing isn't until Lesson 33.
Quote:
I was now just wondering if you could tell me if that code only contains what is necessary to "enable" or "disable" the console application.
|
I'm actually not sure what you could do with that code. It's mainly a declaration of methods provided in external libraries and doesn't actually contain code to do anything with them. My guess is you could use it to create a new console window. It's pretty low-level stuff. It might be the sort of thing that a console application does automatically for you.
Quote:
Thanks again for the quick reply. (do you want me to post a review on here or where I bought it?)
|
Feel free to ask any questions you have and I'll try to answer as quickly as I can.
The best places to post reviews are places like Amazon where lots of people can see them.
Thanks!