A new built #18.104.22.168 of Revit .NET Addin Wizard has been released.
It addressed many issues, big or small, from project wizards and item wizards to various coders and widgets. It also improved the Visual Studio extension (.VSIX) deployment strategy so that the coders and widgets could be installed to all applicable Visual Studio editions and versions properly, along with a good uninstall approach.
It also made sure all the four .NET Addin Wizard software products of version 2015 can be installed side by side in the same single computer. Some readers may develop addins for different CAD platforms such as Revit, AutoCAD, Inventor and Navisworks. We provide four wizards to help, Revit .NET Addin Wizard 2015, AutoCAD .NET Addin Wizard 2015, Inventor .NET Addin Wizard 2015, and Navisworks .NET Addin Wizard 2015. Early builds and versions might not support side by side install. Two particular builds of different wizards, or two products regardless of versions might conflict with each other seriously. From now on, please don't worry about that anymore. The latest builds of the 2015 family products are designed to install and run side by side, and well tested about it. If you have any issues in this regard, please feel free to report to us, we will get them addressed as soon as possible.
Another reminder, which is already known to some users and readers, is please install the MSI as administrator. Some Windows versions have a default 'Run as Administrator' context menu in Explorer for MSI files, but some don't have that feature. Some Windows may grant the administrator privilege to the runner automatically if he is an administrator himself, but others do not. When the 'Install' context menu item of an MSI is chosen on some Windows systems, the MSI may be right run as administrator, but do not behave so on others. It's pretty tricky and inconsistent. However, anyway, please right click on the MSI and choose the 'Run as Administrator' or the simple 'Install' and see, rather than click the MSI directly.
If our latest wizard MSI installers do not launch the VSIX Installer at last to double confirm that the extension is deployed to all applicable Visual Studio products and versions properly, it most likely would indicate that you haven't run the MSI with administrator privilege.
In terms of how to run MSI as Administrator, there are a variety of ways, calling the msiexe in a command line window directly, adding/changing some Windows registries, running a script, getting a tool to help, and so on. We will introduce one or two soon later if necessary.