Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[NBug] Could not load file or assembly 'RestSharp, Version=106.1.0... #8089

Closed
ghost opened this issue May 11, 2020 · 8 comments · Fixed by #8123
Closed

[NBug] Could not load file or assembly 'RestSharp, Version=106.1.0... #8089

ghost opened this issue May 11, 2020 · 8 comments · Fixed by #8123
Labels
📭 needs: author feedback More info/confirmation awaited from OP; issues typically get closed after 30 days of inactivity status: incorrectly filled template
Milestone

Comments

@ghost
Copy link

ghost commented May 11, 2020

⚠️ The sections below must be filled in and this text must be removed or the issue will be closed.

Current behaviour

Expected behaviour

Steps to reproduce

Error Details

System.IO.FileLoadException: Could not load file or assembly 'RestSharp, Version=106.1.0.0, Culture=neutral, PublicKeyToken=598062e77f915f75' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'RestSharp, Version=106.1.0.0, Culture=neutral, PublicKeyToken=598062e77f915f75'
   at Atlassian.Jira.Jira.CreateRestClient(String url, String username, String password, JiraRestClientSettings settings)
   at JiraCommitHintPlugin.JiraCommitHintPlugin.UpdateJiraSettings()
   at JiraCommitHintPlugin.JiraCommitHintPlugin.Register(IGitUICommands gitUiCommands)
   at GitUI.PluginRegistry.<>c__DisplayClass12_0.<Register>b__0(IGitPlugin p)
   at System.Linq.LinqExtensions.ForEach[T](IEnumerable`1 enumerable, Action`1 action)
   at GitUI.PluginRegistry.Register(IGitUICommands gitUiCommands)
   at GitUI.CommandsDialogs.FormBrowse.RegisterPlugins()
   at GitUI.CommandsDialogs.FormBrowse.<<-ctor>b__43_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at GitUI.ThreadHelper.<>c__DisplayClass13_0.<<FileAndForget>b__0>d.MoveNext()

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Additional information

I've just started GitExtensions via the Explorer context menu "GitExt open repository". I did it on a directory 1-leve into the repository.

Environment

  • Git Extensions 3.4.0.9381
  • Build 096b4d5
  • Git 2.26.2.windows.1
  • Microsoft Windows NT 6.2.9200.0
  • .NET Framework 4.7.3610.0
  • DPI 96dpi (no scaling)
@archivarius-bot
Copy link

Thank you for the bug report 👍

Sadly, it appears some important information is still missing, which you may have overlooked while submitting the bug.
Without this information we may not be able to assist you in resolving the issue.

Please review your submission, fill the missing information in and post a new comment to ping us back to re-open the issue.
Thanks again

@duplicates-detector-bot
Copy link

Potential duplicates:

  • #7606

@RussKie RussKie reopened this May 19, 2020
@RussKie
Copy link
Member

RussKie commented May 19, 2020

Is this from a portable version or an msi?

@RussKie RussKie added 📭 needs: author feedback More info/confirmation awaited from OP; issues typically get closed after 30 days of inactivity and removed potential-duplicate labels May 19, 2020
@RussKie RussKie added this to the 3.4 milestone May 19, 2020
@pmiossec
Copy link
Member

I wonder if using restsharp for one api call is not overkill and this dependency being removed to prevent this kind of errors and problems of dependency management...

@haldyr
Copy link

haldyr commented May 19, 2020

I wonder if using restsharp for one api call is not overkill and this dependency being removed to prevent this kind of errors and problems of dependency management...

RestSharp is dependency of Atlassian.SDK package so it is not probably going away any time soon.

@ghost ghost removed the 🚧 status: in progress Issues which have associated PRs label May 21, 2020
@ghost ghost added the 🚧 status: in progress Issues which have associated PRs label May 27, 2020
@TiTime
Copy link

TiTime commented Jun 2, 2020

was about to file issue and discovered this unresolved issue

Current behaviour

Opening git extension causes this an error report

Expected behaviour

No error is thrown, so jira hint integration works as expected

Steps to reproduce

Enable Jira hint plugin.

Error Details

System.IO.FileLoadException: Could not load file or assembly 'RestSharp, Version=106.1.0.0, Culture=neutral, PublicKeyToken=598062e77f915f75' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'RestSharp, Version=106.1.0.0, Culture=neutral, PublicKeyToken=598062e77f915f75'
   at Atlassian.Jira.Jira.CreateRestClient(String url, String username, String password, JiraRestClientSettings settings)
   at JiraCommitHintPlugin.JiraCommitHintPlugin.UpdateJiraSettings()
   at JiraCommitHintPlugin.JiraCommitHintPlugin.gitUiCommands_PostSettings(Object sender, GitUIPostActionEventArgs e)
   at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
   at GitUI.GitUICommands.InvokePostEvent(IWin32Window ownerForm, Boolean actionDone, EventHandler`1 gitUIEventHandler)
   at GitUI.GitUICommands.DoActionOnRepo(IWin32Window owner, Boolean requiresValidWorkingDir, Boolean changesRepo, EventHandler`1 preEvent, EventHandler`1 postEvent, Func`1 action)
   at GitUI.GitUICommands.StartSettingsDialog(IWin32Window owner, SettingsPageReference initialPage)
   at GitUI.CommandsDialogs.FormBrowse.PluginSettingsToolStripMenuItemClick(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Environment

  • Git Extensions 3.4.0.9381
  • Build 096b4d5
  • Git 2.27.0.windows.1
  • Microsoft Windows NT 6.2.9200.0
  • .NET Framework 4.8.4180.0
  • DPI 96dpi (no scaling)

@pmiossec
Copy link
Member

pmiossec commented Jun 2, 2020

As you probably see it,#8123 is expected to fix it but requires some adjustments before merging it...

@RussKie RussKie closed this as completed Jun 2, 2020
@ghost ghost added 🚧 status: in progress Issues which have associated PRs and removed 🚧 status: in progress Issues which have associated PRs labels Jun 2, 2020
@pmiossec
Copy link
Member

pmiossec commented Jun 2, 2020

@TiTime you could now test the result of the CI build and reports if it solves your problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📭 needs: author feedback More info/confirmation awaited from OP; issues typically get closed after 30 days of inactivity status: incorrectly filled template
Projects
None yet
4 participants