The first example demonstrates creating an app which displays the Favorites folder.This makes for an excellent examples since it extensively uses classes. However, when I typed the code word for word I recieved an error msg in the section on page 405 where I am creating an instance of the favorites object.
The line: "Dim Item As New ListViewItem"
generates a red line underneath ListViewItem
Highlighting ListViewItem yields "Type ListViewItem Not defined"
When I downloaded the code off the web I found the working code does not use the code from page 405. It refers to the same example AFTER more modifications have been added a few pages further down. Can ANYONE offer any assistance so I can pick up where I left off. I HATE abandoning a project just because I could'nt figure it out.

It looks as though you are using Beginning VB.Net, 2nd Edition and the code you are referring to is in Step 1 on page 405. Make sure you are adding this code to Form1 and that you followed the steps for creating the form starting on page 399.

Thearon

Ok Thearon, I got thru that problem a while ago simply by realizing all the code was correct and therefore I should unwillingly delete my code and start from scratch. You see sir, the problem was somewhat fundamental. The line "Dim Item As New ListViewItem" simply could not be typed without that annoying red line popping up. I realized it must have something to do with the listview control and nothing more.
I picked apart the downloaded version to make the code exactly as the code I typed and , of course, your code still worked. That's when I decided to delete my solution and simply begin again. This time, however, I put the listview object on the form first, I then went to the code behind and typed the line "Dim Item As New ListViewItem". Long behold; NO RED LINE !!! It was obviously a quirky situation with VB.Net.Wait, did I say 'obviously' ? Anyhow I was able to move on. Thanx for the inspiration. On to more convoluting questions. I'd like to ask sir:Why do you elect to use three classes to address this solution.Could'nt some of thes classes have been designed as methods. It left me wondering when do I need to create a class vs when do I create a method to achieve an objective. Any suggestions ???

As I was not the original author of this particular chapter I can't speak to the reasons behind the design choices. However, you always want to keep code reuse in mind and try to avoid writing the same code twice. Sometimes it makes sense to place code in a method to share it and then sometimes it makes sense to place that method in a separate class in order to have that code available to the entire project or solution.

I hope this helps.

Thearon