A dialog box will appear with a list of your installed indicators. Select the indicator that you want to remove from NinjaTrader, and then select the Remove button, as shown here:
NinjaTrader will remove that indicator and its associated code. You’ll see a confirmation dialog, which you can close, and then you may close the Remove NinjaScript Assembly window. You can now install the new update or new indicator.
Note that when you do this, you may affect any indicator-specific templates that were added for the old indicator, so you may need to define those again. Sometimes the order of plots change in an indicator update, and in that case, the old template won’t work properly with the new version. So if the new version looks like something is amiss, use the "reset" function of the template to have it reset back to default, then adjust it as needed.
If removing the indicator and reinstalling doesn't work
If you removed the indicator and then reinstalled it and you're still getting a duplicate name error, then it's likely related to internal coding issues. This can occur when you're installing a number of indicators contained in a single .zip file, sometimes called a bundle. If you install the individual versions of your indicator(s) rather than using a bundle, the error may be avoided. The solution for this usually involves identifying and removing the indicators that are creating the conflict, usually in the custom indicator directories within the NinjaTrader user directory. Contact BCT support at firstname.lastname@example.org and we'll provide further assistance to correct the issue.
If you would prefer to try to resolve this yourself, you can follow the steps in the following link. The approach would be to move all of your 3rd-party .cs and .dll files into a separate folder, then recompiling one of NinjaTrader's provided indicators. If you don't get an error, add in one of the indicators you temporarily removed by putting it back in the original directory, and then recompiling the same indicator you compiled the first time (NT checks all indicators when you compile any one of them). If there's no error, then move on to the next one, etc., until you find one that fails. The one that fails may be the culprit. These steps are detailed at this link: