Doing the last point created - as intended - a new solution, but there is still no project created, as you can see in the following picture (Projektmappe = solution).
The Solution Explorer for ASP.NET 5 MVC projects has several major problems - one of them is file nesting. NET will create a new solution with the same name as the project, placing the solution files in the same directory as the project. The simplest is to create a new project-by default, Visual Studio.
FIX: Images are missing in Visual Studio 2015 Symptoms. Visual Studio also has a class view window, but Solution Explorer is smart enough to list all the Class View elements inside Reinstall "Designer for Visual Studio WiX Setup Projects, Professional" selecting both vs 2017 and VS 2019 as target. Moreover, VisualSVN allows you to manage files in the Solution Explorer in a transparent fashion. In the tree at the left of the dialog box select General from the Projects and Solutions section. Check it and save and you will see your solution file! The nesting behavior is coming from either the solution-specific settings or the Visual Studio settings. I tried with ctrl+ ALt+ L, still it is not showing up. If the command line doesn't work then try resetting Visual Studio via the file system. It can also optionally warn about files on disk that are not included in a project.
In Unity, go to Edit -> Preferences, and make sure that Visual Studio is selected as your preferred external editor. Figure 3: Reload unloaded projects from Solution Explorer. In Add New Item - SFMLx32 wizard, click C++ file (.cpp). Visual Studio remembers which projects were loaded the next time you open the solution.