Known Issues for .NET Language Enhancements

If you declare a namespace for a global function in a PowerBuilder .NET application, then call the global function using the namespace prefix, the Error List shows an undefined variable error when you attempt to build the application.

Nonvisual user objects that you inherit from .NET generic types that include angle brackets in their names, such as System.Linq.Lookup<T,U>, open in the source code editor rather than in the object painter.

If you do not provide a value for an enumerated item in a local or global enumeration, text that you enter in the Comments column for that item is not saved.

If you extend a parameterized constructor by adding code to it in a child object, then delete the parameterized constructor in the parent object, the child object source code still contains a hidden system-generated script that calls the deleted parent constructor. This leads to a compile failure.

When you save one interface as another interface, both interfaces have the same members. If you implement both interfaces in a nonvisual user object, then delete the second interface, while keeping one or more of the members of that interface, the members no longer have an interface prefix. The same members of the original interface still have an interface prefix. This leads to a compile failure.

If you open the PB Object Outline window and create a global enumeration object, you can see the name-value pairs that you enter for the enumeration in the PB Object Outline window when you expand the node for the new enumeration object. If you click any of the name-value pairs, the Enumeration painter incorrectly switches to the Declare Namespace view.