Revit Add-In Locations

Question: Where are the appropriate file installation locations for Release and Test/Debug Revit add-in components?

I have noticed a variety of locations where Revit add-in components are deployed for Release and Test/Debug purposes.

For example, the Hello World sample for Revit 2017 recommends installing HelloWorld.addin to C:\ProgramData\Autodesk\Revit\Addins\2017, whereas the Addin Wizard generates a script that automatically loads the *.addin file to C:\UserName\AppData\roaming\AppData\Roaming\Autodesk\Revit\Addins\2017.

I have also noticed that the official release add-in installation programs that I have historically gotten back from the Autodesk Revit team seem to install the *.addin, *.dll, and other supporting files in numerous locations depending on:

Revit version(s) supported

All users vs. current user installation

Roaming profiles vs. non-roaming profiles

Version of Windows (?)

Possibly other criteria

First, is there documentation that describes how this should be done for commercial products?

Second, in the specific example of installing an add-in for Revit 2017 running on Windows 10 for the current user only without roaming, where would I install the production components (myaddin.addin, myaddin.dll, myaddindependent.dll)?

Can I utilize the location for the .addin file for Test and Debug?

I assume that I will need to point the myaddin.addin file to the Debug version of the myaddin.dll file in order to Debug?

Answer: The official documentation for this can be found in the Revit API developer guide; go to: