Appendix of commonly used: Abbreviations, Acronyms & Definitions
BIS Glossary - Key BIS terms used in the documentationDigital Twin BIS Abbreviations - Standard Abbreviations, Acronyms, and Naming Rules (BIS, EC, ...)
Definitions (Concise definitions provided with links as-needed to formal definition(s).)
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]
The act of providing all Exact Software and OS Version Numbers and an extremely simplified lowest common denominator stand-alone data set (least: design file(s), element(s), configuration and/or compilable code project, Product and Operating System versions/patch levels) and Steps to Reproduce the Issue; allowing others to quickly and readily reproduce an exact issue with the highest level of success and help provide timely assistance, work-around, or resolution needed. Equally important in the process is to ensure your test case data is clearly demarcated using either a: a.) Good and Bad, or b.) Before and After; naming convention whenever possible. These steps are essential to ensure proper identification of a problem, the best chance to reproduce, recommend, and/or resolve a given (complex) issue.When your test case is ready for review either: a.) Zip and Attach it to your original post, or b.) zip and use the Secure File Upload option when working with technical support.
Acronyms: AcronymFinder.com, Microsoft Acronyms (Preview), Microsoft Acronyms, Microsoft TechnologyDictionaries: Cambridge.org, Dictionary.com, GoogleDictionary, Merriam-Webster, OneLook.com, VisuWords.com, Wiktionary.orgIdioms: UsingEnglish.com, LinguaholicPronunciations: howtopronounce.comPhilosophy: plato.stanford.edu, philosophybasics.comReleases: MicroStation SDK Releases, History of MicroStation, History of MicroStation SDK (Blog: Jon Summers)