Redundant namespaces cannot be resolved

SyntaxEditor .NET Languages Add-on for WPF Forum

Posted 2 years ago by Tobias Lingemann - Software Devolpment Engineer, Vector Informatik GmbH
Version: 22.1.3
Platform: .NET 4.8
Environment: Windows 10 (64-bit)


we noticed a problem with a customer project. after we upgraded from an older WinForms version of the SyntaxEditor to the current WPF version.
The problem is that when a specified namesapce is redundant (e.g. not required), but accepted by the compiler, the types cannot be resolved.
For example we have a file like this:

using System;

namespace CustomNamespace.Common.Types
  public enum Bool

And another file like this:

using System;
using CustomNamespace.Common.Types;

namespace CustomNamespace.Test
  public class Test
    public static void A(Common.Types.Bool value) { }
    public static void B(Bool value) { }

The Type "Bool" is resolved in method "B", but not in "A". In this case "Common.Types" ist not required due to the using statement, but it is still valid. The old WinForms release had no problem with that.

This also applies for the intelli prompt. The namespace "Common" is visible in the intelli prompt, but none of its children.

[Modified 2 years ago]

Best regards, Tobias Lingemann.

Comments (1)

Posted 2 years ago by Actipro Software Support - Cleveland, OH, USA


Thank you for reporting this.  We tracked down the problem and resolved it for the next build.

Actipro Software Support

The latest build of this product (v24.1.2) was released 3 months ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.