Put assembly list name first in the window title

[miloush]

Is your feature request related to a problem? Please describe.
I have multiple instances of ILSpy allowed, because I need to use see different set of assemblies at the same time. However, since the word "ILSpy" is shown first in the title, it is not easy to find out which window is the correct one, as the list name gets often cut of (especially if the title also contains the build number).

Describe the solution you'd like
I would suggest the assembly name list is put first and the application name second in the window title, like in all other applications that open documents. If that was too disruptive to users, the title can change this way only when multiple instances are enabled.

Additional context

Happy to implement if there was an agreement.

[christophwille]

IF we build anything like that, obviously it must be a new flag that defaults to the old behavior.

Taking VS for a test drive - it shows either "Visual Studio" when no code, or solution name when one is loaded. VSCode shows the active file name (or folder name when absolutely no file is open at all).

The question I am trying to determine is "What would a user expect to see in the taskbar?" I am not so sure that the assembly list name is the thing (average) users would derive most value from. Taking a page from VSCode would maybe lead to: If no assembly is active (no node from an assembly is selected in the assembly tree) show the assembly list name. If any method, resource or whatever is selected, take the assembly name as in the assembly tree.

Other ideas welcome in terms of what could be useful information in the taskbar.

[miloush]

Just to clarify, the assembly name list is already there, I am suggesting to change "ILSpy - ASP.NET" to "ASP.NET - ILSpy", akin to "Project - Microsoft Visual Studio". I would also expect most users to have taskbar not expanded so impact on those should be minimal, although you can see it in Alt+Tab as well.

IF we build anything like that, obviously it must be a new flag that defaults to the old behavior.

Hence suggesting this is done for when multiple instances are allowed, that should further limit the number of impacted users.

You raise a good point that if I had two instances of the same assembly list looking at different types, that wouldn't help, and adding the type in the title as well could help even for single instances. I would leave that for when someone asks for it, I am happy with assembly list name only.

[christophwille]

Yes, I am one of those "expanded taskbar" users, that is why I had the VS/VSCode samples handy.

[christophwille]

@miloush we had an internal chat, no objections were raised, so please feel free to go ahead.