Your product must be relevant to (and usable with) AutoCAD 2020 or any of these AutoCAD 2020 vertical products: AutoCAD Architecture, AutoCAD Electrical, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Civil 3D and must run on all Windows operating system supported by the AutoCAD 2020product (including both 32-bit and 64-bit versions). If you indicate compatibility with one or more vertical products, you are responsible for testing your App with that product. You can also indicate the compatibility with AutoCAD 2019/2018/2017 (or its vertical listed above). We strongly recommend you make use of the standard Autodesk App Store installer we create for you.
The default user privilege for the store apps is Windows 7/Windows 8.1/Windows 10 Admin User. The installer we create for your app will require elevated user privileges to install. If you don’t use our standard installer template to install or if you do not wish to have elevated user privileges for your app installer, then this must be very clearly documented in the description of your product displayed on the store.
We strongly encourage you to make use of the autoloader mechanism to deploy your plug-in. Information on the required format for autoloader bundles is included in the AutoCAD 2020 help files. Search for Install and Uninstall Plug-in Applications or search the help for “appautoloader” and the video walks through some simple examples for.NET, ObjectARX, LISP, and CUIX plug-ins.You can also download some of the free plug-ins already available on the Autodesk App Store and study their format (for example, OffsetInXref Trial, DimensionPatrol Trial, or ClipboardManager). There are many ways to ensure your plug-in will work well with other plug-ins a user may install. These are described in detail in the ObjectARX Application Interoperability Guidelines—part of the helpfiles in the ObjectARX SDK (downloadable from ).
Although the Interoperabilty Guidelines is part of the ObjectARX SDK, many of these guidelines apply to all plug-in types. Don’t worry if you’ve designed your application without reading these guidelines—they are guidelines and not requirements. However, we recommend you consider them when designing your next project or when updating existing ones. Using a partial CUIX file to add ribbon bar elements for your application is required, but how you do this will depend on your plug-in design. As a minimum, every plug-in or block library must add a panel to the Plug-Ins tab that either invokes the main command defined by the plug-in or displays a helpfile explaining how to use the block library. The video posted with these guidelines shows how to setup a partial CUIX file to add a panel to a tab already defined in the main CUIX.Plug-ins that install a single panel should normally add that panel to the Plug-Ins tab.Plug-ins that create several ribbon bar panels may prefer to create a new tab specific to that plug-in (and normally with the tab name being the name of the plug-in).You can add any other UI elements to your partial CUIX (for example, menubars and toolbars) as well, but you must still include a basic ribbon bar UI.
Revit 2016 has added two properties to help exchange store app publishers to check if the current user has purchased the given app or not. Those two properties are: Application.IsLoggedIn Application.LoginUserId IsLoggedIn checks if the user is logged in to his/her Autodesk account from the current Revit session. LoginUserId returns. When the Autodesk desktop app is installed, it collects information about the product download and install success. It also collects information on how you interact with the app to help us improve your experience.