Welcome back! If you missed Part 1, you can check it out here.
Toolset
It was obvious that updating the toolset would be the most difficult part. At least that’s what it looked like in the beginning, but now I tend to think that support of the plugin was the most difficult part. For one thing, we already had a toolset and a mechanism for evaluating MSBuild projects, which was good as it was even though it had yet to be extended. The fact that we didn’t have to write the algorithms from scratch made it way easier. The strategy of relying on “our” toolset, which we preferred to stick to when supporting Visual Studio 2017, once again proved right.
Welcome back! If you missed Part 1, you can check it out here.
Toolset
It was obvious that updating the toolset would be the most difficult part. At least that’s what it looked like in the beginning, but now I tend to think that support of the plugin was the most difficult part. For one thing, we already had a toolset and a mechanism for evaluating MSBuild projects, which was good as it was even though it had yet to be extended. The fact that we didn’t have to write the algorithms from scratch made it way easier. The strategy of relying on “our” toolset, which we preferred to stick to when supporting Visual Studio 2017, once again proved right. […]