[NBug] Could not load file or assembly 'mscorlib, Version=4.0.0.0,...

[drewnoakes]

Environment

• Git Extensions 4.2.1.17611
• Build b0c0b28
• Git 2.44.0.windows.1
• Microsoft Windows NT 10.0.22631.0
• .NET 6.0.28
• DPI 144dpi (150% scaling)
• Portable: False

Issue description

System.IO.FileNotFoundException: Could not load file or assembly 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. The system cannot find the file specified.
File name: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   at async Task<bool> GitUI.VisualStudioIntegration.TryOpenFileInRunningInstanceAsync(string filePath)
   at void System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start<TStateMachine>(ref TStateMachine stateMachine)
   at Task<bool> GitUI.VisualStudioIntegration.TryOpenFileInRunningInstanceAsync(string filePath)
   at async void GitUI.VisualStudioIntegration.OpenFile(string filePath)+(?) => { } in C:/projects/gitextensions/GitUI/VisualStudioIntegration.cs:line 42
   at async Task GitUI.TaskManager.HandleExceptionsAsync(Func<Task> asyncAction, Func<Exception, Task> handleExceptionAsync) in C:/projects/gitextensions/GitExtUtils/GitUI/TaskManager.cs:line 38

Steps to reproduce

Right-clicked an unstaged file in FormCommit and selected "Open in Visual Studio".

Did this work in previous version of GitExtensions?

I haven't seen this before, and I used the feature from time-to-time.

It's possible I was running the VS installer during this time.

Diagnostics

No response

[duplicates-detector-bot]

💡 The issue has been fixed in v4.2-rc1. Please update your version.

[duplicates-detector-bot]

Potential duplicates:

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

[drewnoakes]

Actually, based on the variety of these issues, I'm going to reopen. Someone who knows this bot and the issue tracker a bit will know better whether to close it.

[pmiossec]

It's possible I was running the VS installer during this time.

All the "Could not load" issue reports on "features that were working well before" that we got at the moment are linked to assemblies updated by Windows update.

So restarting GE is enough.

[drewnoakes]

Thanks, I'll close this then.

Wonder if there's a better experience we can offer here though.

[mstv]

Wonder if there's a better experience we can offer here though.

It is caused by Windows updating .NET...
A workaround might be that GE should asynchronously load all DLLs which it might ever use.
I doubt GE is the only affected app.

[RussKie]

We can hardlock all the assemblies. Or block the Windows Update 😈😈😈😈

[mstv]

We can hardlock all the assemblies. Or block the Windows Update

🤔 A reboot is anyway required after a .NET update. So the assemblies should rather be replaced during that reboot.