R
rn5a
Consider the following code in a VB class file:
Namespace LoginUserFetchDB
Public Class ZForZebra : Inherits SoapHeader
Public UserName As String
Public Password As String
End Class
Public Class GetDBRecords : Inherits WebService
Private sqlCmd As SqlCommand
Private sqlConn As SqlConnection
Public sHeader As ZForZebra
...............
...............
End Class
End Namespace
Using VBC. I compiled the above in LoginUserFetchDB.dll which resides
in the folder C:\inetpub\wwwroot\ASPX\bin
Have a look at the line
Public sHeader As ZForZebra
Though the above code & the ASPX page which uses the above DLL works
without any problems, what I find is Visual Web Developer 2005 Express
Edition underlines the word 'ZForZebra' saying that
'ZForZebra' is ambiguous in the namespace 'LoginUserFetchDB'.
That's the reason why I used such an absurd class name 'ZForZebra'
since I am pretty sure that the .NET Framework won't be having any such
class name. Neither have I used such a class name in any of my class
files (or any other .NET related files) any time. I also tried using
Public sHeader As LoginUserFetchDB.ZForZebra
but that didn't make any difference.
After a lot of research, using the Object Browser, I concluded that
LoginUserFetchDB.dll not only exists in the above-mentioned bin
directory, it also exists at 2 more places:
C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
Files\aspx\98099ba2\_shadow\695771b\bin\2\
&
C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
Files\aspx\443e485a\_shadow\ff53954a\bin\2\
It was only when I deleted LoginUserFetchDB.dll from the above 2
folders did VWD 2005 stop highlighting this ambiguous name error.
Though I don't think that's could be the reason why VWD is highlighting
that error since in other VB class files using similar code, VWD
doesn't highlight the error. So how do I avoid the ambiguous name error
in VWD?
I don't understand what's causing the ambiguous error since I am more
than 100% sure that I am/have not used a class with the name
'ZForZebra' anytime anywhere!
Namespace LoginUserFetchDB
Public Class ZForZebra : Inherits SoapHeader
Public UserName As String
Public Password As String
End Class
Public Class GetDBRecords : Inherits WebService
Private sqlCmd As SqlCommand
Private sqlConn As SqlConnection
Public sHeader As ZForZebra
...............
...............
End Class
End Namespace
Using VBC. I compiled the above in LoginUserFetchDB.dll which resides
in the folder C:\inetpub\wwwroot\ASPX\bin
Have a look at the line
Public sHeader As ZForZebra
Though the above code & the ASPX page which uses the above DLL works
without any problems, what I find is Visual Web Developer 2005 Express
Edition underlines the word 'ZForZebra' saying that
'ZForZebra' is ambiguous in the namespace 'LoginUserFetchDB'.
That's the reason why I used such an absurd class name 'ZForZebra'
since I am pretty sure that the .NET Framework won't be having any such
class name. Neither have I used such a class name in any of my class
files (or any other .NET related files) any time. I also tried using
Public sHeader As LoginUserFetchDB.ZForZebra
but that didn't make any difference.
After a lot of research, using the Object Browser, I concluded that
LoginUserFetchDB.dll not only exists in the above-mentioned bin
directory, it also exists at 2 more places:
C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
Files\aspx\98099ba2\_shadow\695771b\bin\2\
&
C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
Files\aspx\443e485a\_shadow\ff53954a\bin\2\
It was only when I deleted LoginUserFetchDB.dll from the above 2
folders did VWD 2005 stop highlighting this ambiguous name error.
Though I don't think that's could be the reason why VWD is highlighting
that error since in other VB class files using similar code, VWD
doesn't highlight the error. So how do I avoid the ambiguous name error
in VWD?
I don't understand what's causing the ambiguous error since I am more
than 100% sure that I am/have not used a class with the name
'ZForZebra' anytime anywhere!