Browse Source

VB: Fixed bug in global name lookup when the using scope of the compilation unit is inside a namespace

git-svn-id: svn://svn.sharpdevelop.net/sharpdevelop/branches/3.0@3694 1ccf3a8d-04fe-1044-b7c0-cef0b8235c61
shortcuts
Daniel Grunwald 17 years ago
parent
commit
a9eb814ba3
  1. 9
      src/Main/Base/Test/NRefactoryResolverTests.cs
  2. 1
      src/Main/ICSharpCode.SharpDevelop.Dom/Project/Src/ProjectContent/DefaultProjectContent.cs

9
src/Main/Base/Test/NRefactoryResolverTests.cs

@ -1025,6 +1025,15 @@ End Class @@ -1025,6 +1025,15 @@ End Class
"the full type should be resolved");
}
[Test]
public void GlobalNamelookupVB()
{
// using an import this way IS possible in VB.NET
string program = "Imports System\n";
NamespaceResolveResult nrr = ResolveVB<NamespaceResolveResult>(program, "System", 1);
Assert.AreEqual("System", nrr.Name);
}
[Test]
public void ImportAliasTest()
{

1
src/Main/ICSharpCode.SharpDevelop.Dom/Project/Src/ProjectContent/DefaultProjectContent.cs

@ -791,6 +791,7 @@ namespace ICSharpCode.SharpDevelop.Dom @@ -791,6 +791,7 @@ namespace ICSharpCode.SharpDevelop.Dom
if (string.IsNullOrEmpty(usingScope.NamespaceName)) {
// Try if name is already the full type name
fullname = name;
lookedForFullTypeName = true;
} else {
fullname = usingScope.NamespaceName + "." + name;
}

Loading…
Cancel
Save