Visual Studio is just giving up!

Apocolypse2005 · December 23rd, 2010, 08:12 AM

Hi all,

My problem is, I have to iterations one inside another!
The iterations are looping through a list of my own classes! both of them!
So basically its comparing one class to all the other classes in the other list and looping through as shown below!

Code:

Dim MyList As List(Of MusicDetail) = MyProperty
Dim MyList2 As List(Of MusicDetail) = MyProperty2

For Each nMusDetail As MusicDetail In MyList
    For Each nMusDetail2 As MusicDetail In MyList2

    Next
Next

Now Regardless of the names and what happens in the middle of the two iterations, VB does not want to go any further than the second "for each" statement! It just exits out of the code with no errors, or message boxes!

Any Ideas?!

Cheers

GeneBuchite · December 28th, 2010, 07:40 AM

I have been Programming in visual basic 6 for some time. when I find a spot like this where visual basic "gives up" I use a work around ie.

Code:

For Each nMusDetail As MusicDetail In MyList
    Do 
          If condition = true Then
               Exit Do
           Else 
               ' Do Something Wonderful'
           End IF
    Loop
Next

Apocolypse2005 · December 29th, 2010, 08:04 AM

But that doesn't quite do the comparison I'm looking for, there should be no reason for visual studio to give up!

I need to do a specific comparison between the two classes and the for each statement nicely grabs each one for me with out having add extra code to get them.

HiTechCoach · December 29th, 2010, 01:09 PM

Quote:

Originally Posted by Apocolypse2005

Hi all,

My problem is, I have to iterations one inside another!
The iterations are looping through a list of my own classes! both of them!
So basically its comparing one class to all the other classes in the other list and looping through as shown below!

Code:

Dim MyList As List(Of MusicDetail) = MyProperty
Dim MyList2 As List(Of MusicDetail) = MyProperty2

For Each nMusDetail As MusicDetail In MyList
    For Each nMusDetail2 As MusicDetail In MyList2

    Next
Next

Now Regardless of the names and what happens in the middle of the two iterations, VB does not want to go any further than the second "for each" statement! It just exits out of the code with no errors, or message boxes!

Any Ideas?!

Cheers

It is possible to nest them.

See: For Each...Next Statement (Visual Basic)
*** scroll down to Nesting Loops

The basic syntax is:

Code:

For Each element [ As datatype ] In group
    [ statements ]
    [ Continue For ]
    [ statements ]
    [ Exit For ]
    [ statements ]
Next [ element ]

Notice how the Next [ element ] has the optional element. I would suggest adding this to make sure that the compiler does not get confused.

Code:

Dim MyList As List(Of MusicDetail) = MyProperty
Dim MyList2 As List(Of MusicDetail) = MyProperty2

For Each nMusDetail As MusicDetail In MyList
    For Each nMusDetail2 As MusicDetail In MyList2

    Next nMusDetail2 
Next nMusDetail

Apocolypse2005 · December 30th, 2010, 09:39 PM

Sorry for taking your time.

It appears that when I last had a break from coding this piece of software, I left it mid debugging when I had found the problem, but I must have been so tired that I couldn't be bothered to work the solution, subsequently I forgot about having ever discovered where the error was coming from.

So once again after debugging step by step the code and analysing the vairables that were getting iterated through, it was bought to my attention that the second iteration was trying to extract the class from an uninstantiated list - which is impossible!

After tracing back to where these variable lists were getting their 'filling' from it was traced back to a dialog and its properties - where inlaid the problem! This solution was upgraded from VS2008 however my coding practices weren't and after much modification using old practices this error arose. It turns out that VS2010 VB.net has this new feature for properties, where unless specifiying the get and set properties they're already done for you! I must have when creating these properties overlooked the fact that I hadn't set or get its information - I must have been rushing as I usually do . . . :)

The fragmented extract below shows my code - the blunder and the solution

Code:

Public MyProperty As List(Of MyVariables)
Private p_myproperty As List(Of MyVariables)

. . . *inside the function

  p_myproperty = theFilling
  Me.Close

. . . 

======================================
' The Correction

Public MyProperty As List(Of MyVariables)

. . . *inside the function

  MyProperty = theFilling
  Me.Close

. . .

If you've understood any of what I've been rambling on about then maybe this can provide some insight if any of your code goes wrong when it comes to assigning properties

However this is a pretty basic mistake which has spawned from a change in coding practices bought on by the upgrading of VS - again my bad for wasting your valuable time

Cheers

Apocolypse2005 · December 30th, 2010, 09:43 PM

Quote:

Originally Posted by Apocolypse2005

It just exits out of the code with no errors, or message boxes!

Any Ideas?!

This does bring up a surprising question - How come VB didn't encounter an error when trying to iterate through - "An Object who's properies or methods havent been . . . . I have forgotton the rest" but you get the picture

Any Ideas?! - don't waste your time by answering that it could just be a 1 off

Cheers

GeneBuchite · January 2nd, 2011, 07:35 AM

There havde been many times when I am coding that VB "Gives up". I look And hunt and use every shred of debugging savy I can muster, but can find NO REASON for VB not to give any results.... sometimes re-booting vs2010 solves the issue. it has gotten to the point when I am programming and my temper starts getting hot & ugly my wife will ask "Do you need to re-boot?"

I've never posted this or mentioned it to microsoft because I can never reproduce the error. thought it was something I was doing/not doing