Nested With Statement Crashes - vb.net-2010

Question

After Visual Studio 2010 locked up earlier today, a code segment that contains a nested With statement no longer works, and locks up, and I have to use Task Manager to terminate VS-2010.
I had a block of code as follows:
With cmd ' OleDbCommand object
With .Parameters '<------- locks up when executing this line
.AddWithValue("#Parm1", Parm1Value)
.AddWithValue("#Parm2", Parm2Value)
' Etc.
End With
.ExecuteNonQuery()
End With
This ran fine, until VS locked up earlier. I had to delete the SUO files from the directory so that VS would not complain when trying to open the documents I had opened previously. But then this nested With-statement stopped working.
However, the following two variations of the code work fine:
With cmd
With cmd.Parameters '<--- with cmd explicitly specified
.AddWithValue("#Parm1", Parm1Value)
.AddWithValue("#Parm2", Parm2Value)
' Etc.
End With
.ExecuteNonQuery()
End With
and
cmd.Parameters.AddWithValue("#Parm1", Parm1Value)
cmd.Parameters.AddWithValue("#Parm2", Parm2Value)
cmd.ExecuteNonQuery()
Any nested With statement that leverages the outer With statement fails the same way (i.e. does not have to be in conjunction with OleDb objects) I did a small test project that did a With on the form object, and a nested With on a sub-object ... same results: it locked up.
I ran the VS-2010 installation to do a repair, and it still behaves this way. Rebooting also does not fix the problem.
I can just code that a different way, but I shouldn't have to, and secondly, who knows what else got messed up when VS crashed that first time?!!
I was hoping to not have to do a full uninstall/reinstall of VS-2010.
Has anyone else seen this problem?

Answer 1

Were you working on this solution/project when VS2010 crashed?
Were you confronted with a project file recovery option before and/or after you removed the SUO file?
As a point of interest, test initializing Anonymous objects using the with statement:
Dim cust0 = New With {.Name = "Toni Poe", .City = "Louisville"}
Have your tried a 'Clean' & 'Rebuild' on your solution.
Try creating a new solution/project and testing a nested with statement on a new OleDbCommand object.
Though, you'll probably feel better with a clean install of VS2010. I suspect your solution is corrupt, not vs2010.