We mentioned many times, here and there, that it is strongly recommended to run the MSI installers as Adminstrator for all our .NET Addin Wizards so that good privileges could be offered to both the MSI itself and the Visual Studio Extension (VSIX) deployment that is handled automatically by the MSI. It is designed so to save users' time and confusions.
However, it still seems not so clear. Most of reasons should come from the fact that different Windows and versions behave differently regarding the MSI running. Before Windows 7, the MSI either could be granted the administrator privilege by default, or be provided the option Run As Administrator by the MSI context menu in the Windows Explorer. In Windows 7, the context menu is gone, and it looks the MSI has good privilege judging from the fact that it could write to the Windows registry. But the 'good' privilege is not really the Administrator one, thus not good enough, as we tested out many times and many users experienced. In some other Windows and versions, e.g. Windows 7.1, Windows 8, Windows 8.1, Windows 10 and various flavours, the behavior is weirdly changed back and forth.
So, it looks quite necessary to make it clear how to exactly Run MSI as Administrator. In fact, there are already many sources on web that address the common issue from different perspectives, so we helped put together a few here.
How to Force an MSI Package to Install Using Administrator Mode
How To Run MSI File As Administrator From Command Prompt In Windows
Windows 7: Run as administrator - Add to MSI File Context Menu
The latest build of AutoCAD .NET Addin Wizard 2015 can be downloaded and purchased from the following page:
Recent Comments