M
Mark
Hi...
We've got one vb project in our solution (most of our code is written in
C#). It references 5 other assemblies. For some reason, when we try to
Clean Solution, the VB project throws 43 errors and 1 spurrious warning.
The 43 errors all center around the other referenced assemblies (2 errors
for each assembly saying it can't find the dll, then 33 errors for every
class referenced in the other assemblies).
The warning is also weird. There's a little chunk of code that says
Dim foo As String = Object.GetItem("idstring")
If IsNumeric(foo) Then
....
End If
The warning is on the IsNumeric(foo) saying that it's been used before it
was initialized.
I assume this is a follow-on from the missing dll (and object) error, but it
still seems weird that it would make a Warning out of it. If it finds the
reference, the code clearly initializes the var before using.
Is there any way to get VB to shut up about all this spurrious stuff? Or is
this just another reason to move all the code to C#?
Thanks
Mark
We've got one vb project in our solution (most of our code is written in
C#). It references 5 other assemblies. For some reason, when we try to
Clean Solution, the VB project throws 43 errors and 1 spurrious warning.
The 43 errors all center around the other referenced assemblies (2 errors
for each assembly saying it can't find the dll, then 33 errors for every
class referenced in the other assemblies).
The warning is also weird. There's a little chunk of code that says
Dim foo As String = Object.GetItem("idstring")
If IsNumeric(foo) Then
....
End If
The warning is on the IsNumeric(foo) saying that it's been used before it
was initialized.
I assume this is a follow-on from the missing dll (and object) error, but it
still seems weird that it would make a Warning out of it. If it finds the
reference, the code clearly initializes the var before using.
Is there any way to get VB to shut up about all this spurrious stuff? Or is
this just another reason to move all the code to C#?
Thanks
Mark