Closed rprouse closed 1 year ago
As written in the link you point to, we can create two installation targets for this extension so that it continues to work for VS2017/19. I believe that VS2017/19 will complain if we release this for VS2022 - they might say it can be updated since it is already installed, although it will not work since this new one will be for x64. So if we continue backward compatibility with 2017/19 we should have two installation targets. Not sure how that will affect the other changes though.
UPDATE: Just noticed you had given the extension a new identifier, so then it will not crash. That is probably for the best, but means we don't expect any support to the older ones.
@rprouse
@OsirisTerje I am going to merge this and remove NUnit2 in another PR to keep them separate.
Continuing work on #43 properly updating the references and updating to the newer framework and adapter releases. Still needs testing. We may need to release a new version just for 2022 now that it is x64?