Re: Visual Basic 2010 SUX!!!!
Posted: Fri Nov 18, 2011 2:27 pm
MrAksel wrote:Nothing sucks, its a coding error. When a type or namespace is ambigious, it means that that type/namespace has the same name as another type/namespace in an imported namespace. For example 'Text' will be ambiguous if you import System and System.Drawing, because both those namespaces contains a namespace named 'Text'. This makes a conflict that is not solved by VB10
Scottie1972 wrote:none of these ideas have anything todo with what i was doing.Emm? Thats the solution ^^ The type is inside two imported namespaces that causes the error.
all i have is a blank form with an AxWindowsMediaPlayer control on it.