I have tried out SlickEdit v23 beta 1 and the .NET Core project works much better now, thank you! I have some questions and comments:
Visual Studio automatically detects file changes (new/deleted files), but in SlickEdit I need to do "Project -> Refresh" for the changes to get picked up. Are there any plans to make this happen automatically in SlickEdit as well?
After creating a new file and doing Refresh, the new file always show up at the end of the list of files for a given folder in the Projects tree view. After closing and opening up the project again it will be displayed in the correct order. Another oddity is that the SlickEdit .vpj files show up in the Projects tree view (and of course also in Visual Studio).
As for the tagging, I must admit that I do not have much experience using SlickEdit with C#. However, there are some things that I have observed.
If I open up the ErrorViewModel.cs file in the project that I originally attached in this thread, place the cursor on "IsNullOrEmpty", and hit Ctrl+. (push-tag), then I get up a lot of alternatives.. See attached screen shot "IsNullOrEmpty.png".
If I do the same in Visual Studio and hit F12 (Go to definition), then it takes me directly to the correct declaration (in a file "C:\Users\VikS\AppData\Local\Temp\MetadataAsSource\2e8756db150b472686a876f6897f483b\7b74f2366ab74cd3889be6547adfba0f\String.cs").
Is there anything I can do in SlickEdit to get the same behavior as in Visual Studio?
Also, when hitting "." after "!string", Visual Studio's dialog comes up quicker and is more helpful than the corresponding dialog in SlickEdit. See attachments "VisualStudio_CodeCompletion.png", "SlickEdit_CodeCompletion.png", and "SlickEdit_CodeCompletion2.png".
In SlickEdit I have to type ".IsNu" (or scroll through a long list) before finding the function I am looking for. And even after finding it I have to select a second (but seemingly identical) overload before any useful function documentation gets shown.
The reason Visual Studio displays "IsNullOrEmpty" at the top is due to IntelliCode:
https://blogs.msdn.microsoft.com/visualstudio/2018/05/07/introducing-visual-studio-intellicode/But even without IntelliCode the function (and especially its documentation) is much easier to find in Visual Studio.