UPDATE on 2017-05-31:
It seems to be a bug with version 17.1 (build 14.0.61705.170). I uninstalled that version (including some prerequisite and other components from program list), did a repair on Visual Studio 2015, then installed build 14.0.61021.0. I was able to see the ADO components working again (but lost the ability to deploy to SQL 2017, as expected). I will report this to the SSDT team.
ORIGINAL POST:
I set up Visual Studio 2017, but the SSDT for SQL 2016 did not integrate so I am in Visual Studio 2015 Shell. I just created a Foreach Loop Container, and tried to get to the configuration screen and only see blanks (see below, both ADO ones do not work, but the file one works). Anybody else see the same issue?