Known Issues for Miscellaneous PowerBuilder .NET Items

On Windows Vista and Windows 7, standard users and users in the Administrator group cannot publish SmartClient WPF applications.

Workaround: Choose Run as Administrator to launch the PowerBuilder .NET IDE and enable the publication of SmartClient applications.

If the current user does not have write permission for the directory assigned to the TMP environment variable, an error message appears in the Output window after the user attemps to create a PowerBuilder .NET project with a target or project wizard.

Workaround: Set the TMP variable to a directory for which the current user has write permission.

Although you can open a solution or target from a remote computer, on Microsoft Vista and later platforms, a security warning dialog box informs you if the project location is not trusted. Clicking Cancel in this dialog box causes an exception, and the solution appears disabled in the Recent Solutions context menu. If you try to reopen the solution from the Open Solution menu, or add the target from the Add Target context menu item, the exception dialog box reappears. This does not occur in PowerBuilder Classic, or if you initially click OK in the security warning dialog box.

If two users add the same solution from a Perforce 2008 depot, then the first user checks in a new object for the solution, the second user can select Get Latest User (Recursive) to add the new object. However, although the new object is visible in the Solution Explorer of the second user, it is not added to that user's PBL directory.

Workaround: The second user must close and reopen the solution to complete the GetLatestUser action and get all the updates.

Although double-clicking a resource item in the Solution Explorer should open the editor associated with the item's file type, on FDCC-configured Windows XP computers, the Move dialog box opens instead. This does not occur on non-FDCC computers or on FDCC-configured computers using the Windows Vista operating system.

In PowerBuilder .NET, if you create a workspace in the root path of the c: drive, then create a target in the root path, the target does not appear in the Solution Explorer.