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 type 'GitCommands.ArgumentString' from assem... #10476

Closed
BBzzz opened this issue Nov 30, 2022 · 10 comments
Closed

[NBug] Could not load type 'GitCommands.ArgumentString' from assem... #10476

BBzzz opened this issue Nov 30, 2022 · 10 comments

Comments

@BBzzz
Copy link

BBzzz commented Nov 30, 2022

Environment

  • Git Extensions 4.0.0.15569
  • Build cba315d
  • Git 2.38.1.windows.1
  • Microsoft Windows NT 10.0.19042.0
  • .NET 6.0.11
  • DPI 96dpi (no scaling)

Issue description

System.TypeLoadException: Could not load type 'GitCommands.ArgumentString' from assembly 'GitExtUtils, Version=4.0.0.15569, Culture=neutral, PublicKeyToken=null'.
   at GitExtensions.GerritPlugin.FormGerritPublish.PublishChange(IWin32Window owner)
   at GitExtensions.GerritPlugin.FormGerritPublish.PublishClick(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, WM msg, IntPtr wparam, IntPtr lparam)

Wanted to publish my review and this error occured
Pageant is running...

Steps to reproduce

I installed the new Git Extensions 4.0 and the new git 2.38, (after removing the previously existing ones) and after that, I can't publish any new content to my review

Did this work in previous version of GitExtensions?

No response

Diagnostics

No response

@duplicates-detector-bot
Copy link

Potential duplicates:

  • #7606
  • #8089
  • #8187
  • #9920
  • #10363
  • #10367
  • #10368
  • #10376
  • #10381
  • #10412
  • #10413

@RussKie
Copy link
Member

RussKie commented Nov 30, 2022 via email

@BBzzz
Copy link
Author

BBzzz commented Nov 30, 2022

Sorry, which plugin are you talking about?
The problem is not that: "PublicKeyToken=null'?

@pmiossec
Copy link
Member

Sorry, which plugin are you talking about?

The Gerrit feature is provided through an external plugin and should be updated to v2.0.1 (using the plugin manager)
See https://github.com/gitextensions/GitExtensions.GerritPlugin/releases/tag/v2.0.1

@RussKie RussKie closed this as not planned Won't fix, can't repro, duplicate, stale Nov 30, 2022
@RussKie
Copy link
Member

RussKie commented Nov 30, 2022

I stand corrected (thank you @pmiossec) - it's "our" plugin, but it's no longer maintained by the core team nor bundled with the app.

@BBzzz
Copy link
Author

BBzzz commented Dec 1, 2022

Unfortunately, it doesn't solve my problem @pmiossec , @RussKie ...
My GerritPlugin has already v2.0.1 version... :(

@pmiossec
Copy link
Member

pmiossec commented Dec 1, 2022

I don't know if @lekhmanrus can help on that?
@lekhmanrus Are you still using the plugin? Does it works well for you with the last version of GitExtensions released?
Maybe the plugin need to be updated to use the v0.3 of GitExtensions.Extensibility? https://www.nuget.org/packages/GitExtensions.Extensibility

@BBzzz
Copy link
Author

BBzzz commented Dec 1, 2022

Sorry, my bad: the GitExtensions.GerritPlugin helped!
Thank you very much!

@lekhmanrus
Copy link
Contributor

@pmiossec, yep we use Git Extensions v4 and Gerrit Plugin v2.0.1 in our company. Works well. 🙂
I'll try to fit some updates for the Gerrit plugin into my schedule.

@pmiossec
Copy link
Member

pmiossec commented Dec 1, 2022

I'll try to fit some updates for the Gerrit plugin into my schedule.

No hurry. It was just because the first answer of @BBzzz said that he still has problem. But if I understand well, it's working now...
So the reason was NOT that the v2.0.1 is not compatible with v4..0 ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants