Manifest Files
\The Sandbox \PB History & Future \New in PB 11 \New in PB 11.1 \Vista support \Manifest Files
User Accounts &
Admin Privileges
Installing PB
Running PB
Manifest Files
Signed DLLs
Web Forms
Application Pool
Permissions for
Web Forms
Help Files
EAServer Support
Vista Limitations

Manifest files

If you want to deploy an application to the Windows Vista operating system that meets the certification requirements of the Windows Vista Logo program, you must follow User Account Control (UAC) guidelines. The executable file must have an embedded manifest that defines the execution level and specifies whether access to the user interface of another window is required. The Vista Application Information Service (AIS) checks the manifest file to determine the privileges with which to launch the process. Use the Security tab page in the Application and .NET Windows Forms Project painters to specify those properties.

Generate options

Select Embedded manifest if your application needs to be certified for Vista. A manifest file with the execution level you select is embedded in the application's executable file.

You can also select External manifest to generate a standalone manifest file in XML format that you ship with your application's executable file, or No manifest if you do not need to distribute a manifest file.

.NET 2.0 SDK required for embedded manifest  If you select Embedded manifest for a Windows Forms target, you must have the .NET 2.0 SDK installed on your system, because the process that embeds the manifest in the executable file uses the mt.exe tool that is distributed with the SDK.

Execution level

Select As Invoker if the application does not need elevated or administrative privileges. Selecting a different execution level will probably require that you modify your application to isolate administrative features in a separate process to receive Vista certification.

Select Require Administrator if the application process must be created by a member of the Administrators group. If the user did not start the process as an administrator, a message box displays so that the user can enter the appropriate credentials.

Select Highest Available to have the AIS retrieve the highest available access privileges for the user who started the process.

UI access

If the application needs to drive input to higher privilege windows on the desktop, such as an on-screen keyboard, select the Allow access to protected system UI check box. For most applications you should not select this check box. Microsoft provides this setting for user interface Assistive Technology (Section 508) applications.

Authenticode signing required   If you check the Allow access to protected system UI box, the application must be Authenticode signed and must reside in a protected location, such as Program Files or Windows\system32.

Warning - Vista manifest files may crash XP  If you add a manifest file that contains Vista extensions to an executable or DLL file on Windows XP with Service Pack 2, memory may be corrupted, causing the operating system to crash or restart. This is a known Microsoft issue described on the Microsoft support site at .

To resolve this issue on Windows XP, Microsoft has provided a patch that can be downloaded from the Microsoft Web site at . You should install this patch before running PowerBuilder on XP.

PBL Peeper PB Help PB History
& Future About Us Feedback Site Map