Handle possible problem with assembly.GetName() call made for all as…

[van800]

…semblies in the appdomain

The issue was submitted to https://youtrack.jetbrains.com/issue/RIDER-112939.

Here are some of the common reasons why Assembly.GetName() could fail:

• Assembly is not Loaded Properly: If the assembly has not been loaded correctly into the application domain, attempting to get its name might result in an error. This could happen if there’s an issue with the assembly's path or if the assembly file is corrupted.
• Code Access Security: If the code does not have the required permissions to access assembly information, Assembly.GetName() can throw a SecurityException. This is more common in environments with restricted permissions, like sandboxed environments or certain enterprise settings.
• File Not Found: If the method attempts to load the assembly for getting the name and the assembly file is not found, it can throw a FileNotFoundException. This could occur in dynamically loaded assemblies where the path or reference is incorrect.
• Bad Image Format Exception: If the assembly is not a valid .NET assembly or is corrupted, a BadImageFormatException may be thrown. This might happen if the assembly was built for a different architecture (e.g., x86 versus x64) or if the file is not an assembly at all.
• IO Exceptions: General IO exceptions can occur if there are issues with reading the file from disk, such as hardware errors, lack of file access permissions, or if the disk is full.

If GetName call fails it is most likely not the GraphView assembly.