Why are types found on an imported namepace but not on a fully qualified namespace after retargeting the framework?
Posted
by
Paul Ferguson
on Stack Overflow
See other posts from Stack Overflow
or by Paul Ferguson
Published on 2012-03-27T11:25:57Z
Indexed on
2012/03/27
11:29 UTC
Read the original article
Hit count: 190
We've just re-targeted a VB.NET project from .Net 2.0 to 3.5.
Various framework types are now missing from our project. Wherever the type is referenced using a fully qualified namespace it's missing. If the relevant namespace is imported for the type; it's found.
For example, this doesn't find the type Object, with compiler error "System.Object is not defined.":
Public Class Foo
Inherits System.Object
End Class
However, this works ok:
Imports System
Public Class Foo
Inherits [Object]
End Class
I've already tried re-opening the solution with no success.
© Stack Overflow or respective owner
