• Community Common Acronyms
• Best Practices

BIS Glossary - Key BIS terms used in the documentation
Digital Twin BIS Abbreviations - Standard Abbreviations, Acronyms, and Naming Rules (BIS, EC, ...)

TIPS

1. Try running both the Product Install and Product (once installed) using Run As Administrator - first. Doing this can often resolve and provide necessary permission an installer requires and may not obtain running other ways. After running the Product once as Admin ensures most post install steps have permission needed to complete and starting the product after as a standard user have the highest chances to succeed.
2. For Microsoft Windows applications having issues Installing or UnInstalling consider running Microsoft's Cleanup Utility (Fix problems that block programs from being installed or removed).

The process of ensuring the closest approximation of completely new/fresh/clean installation of all software and data required; without the presence of any prior user or application installed or induced "traits" or "behaviors"; that can often prevent software applications from performing their expected functions properly otherwise.  A clean install could be installing software on a new operating system distribution.  The more common case of requesting a clean install could also mean to uninstall all suggested/recommended software (often only one application), then confirming that no Program, Application, User Data, or Registry entries remain an interfere and contribute to proper software operation.  Uninstalling an application and deleting Program, Application, and User Data folders is most often sufficient to help verify a clean install helps resolve the prior issue(s).  If the issue(s) persist an additional step may be required to ensure the registry is (further) cleaned and/or if errors prevent installing/uninstalling software, running the Microsoft's Cleanup Utility (Fix problems that block programs from being installed or removed) can also help ensure a "clean install"as well.

Process of stepping through source code, setting breakpoints, or general tracing or troubleshooting techniques to better understand and isolate a given problem.

RELATED: Build and Debug Apps

Custom application code entry points that if present are processed early in the MicroStation startup processing permitting custom applications to provide early non-graphical operations, present custom file open dialogs or custom workflows needed using applicable MicroStation APIs; currently: Native Code C/C++ APIs (via MS_INITAPP variable, or -WA<mdlappname> command line option).  

Related Note: The MicroStation VBA development environment also initializes early in MicroStation's startup processing and provides a convenient startup entry point: OnProjectLoad; that can be considered for similar custom MicroStation VBA startup processing needs.  For more information see: Launching VBA Applications As Initapps Or Dgnapps [CS]