Author Topic: Visual Studio 2017 C# solution opens up with no files and no configuration  (Read 124 times)


  • Community Member
  • Posts: 37
  • Hero Points: 2
When I open up a Visual Studio 2017 C# solution in SlickEdit, then the workspace contains no files and no configurations.

This has been the case for all Visual Studio 2017 C# solutions I have tried so far.

I have attached an example solution, see "".  This example was generated in Visual Studio by selecting "File -> New -> Project", and then chose "Installed -> Visual C# -> .NET Core -> ASP .NET Core Web Application", and then "Web Application (Model-View-Controller)".

See the attached image "VisualStudio2017.png" for how this solution looks when loaded in Visual Studio, and the images "SlickEdit2017_1.png" and ""SlickEdit2017_2.png" for how the solution looks when loaded in SlickEdit.

I found this topic when searching the forum for similar issues:,11589.msg49012.html#msg49012

However, the .sln file in the zip attached to that topic opens up fine (with one file, "SlickEditTest.cs").

Here is my "About SlickEdit" output:
Code: [Select]
SlickEdit Pro 2017 (v22.0.2.1 64-bit)

Serial number: WB943076
Licensed number of users: Single user
License file: C:\ProgramData\slickedit\22\slickedit.lic

Build Date: May 22, 2018
Emulation: CUA

OS: Windows 10 x64
OS Version: 10.00.0 
Memory: 37% Load, 12242MB/32648MB Physical, 14372MB/37512MB Page File, 894MB/134217727MB Virtual
Shell Information: C:\tools\JPSoft\TCMD22\tcc.exe /LD /LH
Screen Size: 1920 x 1080, 1920 x 1080

Project Type: Microsoft Visual Studio Csharp
Language: .txt (Plain Text)
Encoding: Automatic

Installation Directory: C:\Program Files\SlickEdit Pro 22.0.2\ (non-removable drive,NTFS,324586MB free)
Configuration Directory: C:\Users\VikS\Documents\My SlickEdit Config\22.0.2\ (non-removable drive,NTFS,324586MB free)

C:\Users\VikS\Documents\My SlickEdit Config\22.0.2\hotfixes\ (Revision: 6)


  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1150
  • Hero Points: 107
Thanks for the report.  I am able to reproduce the issues you are reporting.  I took a look at .csproj you included and this is not like any msbuild type project file we have seen before.  There are no file, directory wildcard, or configurations to parse from in the project file.  Looking at it in Visual Studio, files are implicitly included, but not all folders are automatically included in the Solution Explorer view.  I am going to file a defect report on this and try to figure out if there is any additional meta-data that we need to parse to create a project view.


  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1150
  • Hero Points: 107
Thanks for that, exactly the pages I needed.