Visual Studio 2017 not opening .modelproj

Question

What workload/component needs to be installed in order for Visual Studio 2017 Enterprise to open existing .modelproj (UML-based design projects)?

Answer 1

I also get this error. I explain how I fix;

1. Open Visual Studio Installer
2. Click Modify
3. Go individual components tab
4. Then check all checkboxes inside Code Tools

EDIT 03/03/2018:

This @Ben solution from the comment:

1. Open Visual Studio 2017
2. Tools menu
3. Get tools and Features... selection
4. Individual Components tab
5. Code Tools group, Then check all checkboxes inside

When you restart visual studio 2017, it must be fixed. Hope it will help someone

Answer 2

to open the project you have to do as described above and install the Live Dependency validation in the Code tools BUT...

"UML designers have been removed

The UML designers have been removed from Visual Studio.

UML diagrams are now presented as XML files
The UML Model Explorer no longer exists
Modeling project references are no longer used for dependency validation
The "Layer References" node in Solution Explorer is no longer displayed
The "Validate" build action on a Dependency (Layer) diagram is no longer used - the Build task has been removed
The project structure is maintained for round-tripping between versions
You can still open, create, edit, and save a Dependency (Layer) diagram as XML
TFS work items linked to a Dependency (Layer) diagram are not accessible on the design surface
Back linking from to DSL or a Layer is no longer supported
UML extensibility in the Modeling SDK is no longer supported"

https://docs.microsoft.com/is-is/visualstudio/modeling/what-s-new-for-design-in-visual-studio?view=vs-2017

Answer 3

After selecting the .NET desktop development workload, be sure to add the optional Architecture and analysis tools component to the install list.

Answer 4

The following worked for me in Visual Studio 2017 (version 15.4.2):

1. Open Visual Studio Installer
2. Go to the tab Individual components
3. In the Code tools section tick Live Dependency Validation. Although this is a different feature, it installed the required dependencies for me.