Partager via

Appendix C: Development Tools

  • Article

 

Development tools are products such as languages and compilers that create executable files or interpreted code modules that mimic the action of executable files when used with a run-time engine of the developing application.

Development tools must meet all of the requirements defined in this Desktop Specification, with the following modifications:

  • Development tools are exempt from the OnNow requirements (defined in "Chapter 6: OnNow/ACPi Support").
  • Development tools are exempt from adhering to this system level group policy setting, as this policy would inhibit the ability of the developer to run the created applications.
Policy Setting Run only allowed Windows Applications
Description When this policy is enabled, users can only run
applications that are listed under the following
key:
Software\Microsoft\Windows\Current\Version\
Policies\Explorer\RestrictRun
Application
Action		 Your application must not start any application
that is not on this list (if you use ShellExecuteEx,
Windows 2000 will handle this for you
automatically)
Registry
information		 Key:
HKCY\Software\Microsoft\Windows\Current\
Version\Policies\Explorer

Value Name: RestrictRun

Best Practice for Development Tools

A development tool targeting Windows should be capable of creating applications that pass certification. However, this is not a formal requirement, primarily because it is not clear how to apply this guideline in such a way that it can be tested in a fair and consistent manner across all development tools.

The following guidelines are recommended:

  • Any installers or install wizards provided to aid in redistribution should be based on Microsoft Installer technologies
  • Any app wizards should create components that follow the desktop spec for UI
  • Any run-times should be compliant, for example they should be capable of installation and use side-by-side, handle long file names, etc.