It looks a bit odd and it is not seamlessly upgradable. On the other hand, it gives Microsoft more freedom to move things around or even apply a full redesign for any next version.
If depends on the problem domain whether one approach or the other is appropriate. In this case it seems smart. Your build environment is very much technology- or even fashion-bound. If they come up with some new deploy model, substantial changes will have to be made to the build tools. It would basically be a new product. And it would be unthinkable you could or would even want to use your old build tools anyway. They do not fit anymore, the target would be new applications that do fit the new usage model.
You may regard it not so much to be a version upgrade, it is more like a new generation that should be set apart from the prior one.