These functions are not currently required but are strongly recommended. Some may become requirements in future versions of this program.
| Recommendation | Met (Yes/No) | Description |
|---|---|---|
| Digital signatures | No | Helps to ensure that only safe code is downloaded from the Internet and intranets. |
| Support for the Microsoft Virtual Machine (VM) | No | Java applications should be tested against the Microsoft VM to ensure highest customer satisfaction. |
| Diagnostic logging | No | Administrators should be able to control the level of logging through a registry key set via policy or user interface. This includes configuration changes, starting/stopping of services, and so on. |
| Support for Unicode | Yes, because the BDG sample applications are built with Microsoft Internet Explorer and Microsoft Visual Basic components, which natively support Unicode. | Converting to Unicode will make your application more portable and enable it to run faster. |
| Support for Microsoft Windows Foundation Classes | No | Applies to Java applications and applets only. |
| Java applications use ADSI | No | ADSI has a Java implementation to make it easy for Java developers to exploit Active Directory™ services. |
| Expose a scripting model | Yes. See COM Components and Objects. | Application provides COM interfaces for programmatic control of application functionality and/or configuration. |
| Year 2000 guidelines | Yes. All dates in BDG applications are stored as "date" type fields in the application's SQL Server database. Dates are manipulated using VBScript and JScript library functions. | Application will not produce errors processing date data in connection with the year change from the 20th to 21st centuries. |
| Symbol files | No | Vendor should provide symbol file(s) available for debug. |
| Applications should be recoverable | No | Server applications must be written so they can be backed up and recovered. |
| Test an application using pool tagging | No | Pool tagging will increase the quality of your application code and help to decrease the possibility that your application will crash the client's operating system. |
| Supply baseline data for configuration management | No | The application should include a complete list of all the files that the service installs and creates, plus a list of all the registry keys created by its installation and those keys it creates while running. |
| Operates in a stressed Windows 2000 Server environment as a high-performance application | No | Applications must meet or surpass customers' expectations in terms of application quality and robustness. Free performance and tuning tools are provided to identify and correct application inefficiencies. |
| Office 2000-specific | ||
| Support for worldwide architecture | No | Stand-alone client applications should support new worldwide EXE and global interface architecture introduced by Microsoft Office 2000. |
| Document publishing, annotation, and subscription services | No | Stand-alone client applications should support publishing documents or HTML to a FrontPage® or WebDAV server; enable navigation and viewing of documents through Windows Name Space Extension (NSE). |
| Web Management | No | Stand-alone client applications should support using Microsoft FrontPage as their main intranet Web management tool for link fixing, reporting, and document object model (DOM) integration with Office 2000 publishing. |