Does anybody else go a little crazy when testing changes to an addin but also needing to just use SW with the released version of the addin for non-testing purposes? Currently we have an addin I created that is pretty extensively used in all our models and of course the addin is always being updated. There are weeks where I bounce back forth between just using SW for well... modeling, and testing changes to the addin. Because of this I have to be really careful about which dlls are resisted with SW and always checking which ones are being used depending on what I am doing. It also means there is now quickly switching between just using SW and testing the addin.

So, has anybody come up with a good solution? My only idea so far is to have Visual Studios run a batch file that unregisters the released version and registers the testing version​ on starting debug, and un-registering the testing version and re-registering the released version when ending.