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

DependencyResolutionException not deserializable #932

Closed
wkamir opened this issue Sep 4, 2018 · 5 comments
Closed

DependencyResolutionException not deserializable #932

wkamir opened this issue Sep 4, 2018 · 5 comments
Labels

Comments

@wkamir
Copy link

wkamir commented Sep 4, 2018

The DependencyResolutionException is inherited from System.Exception which implements ISerializable.

It needs to implement the following constructor:

public DependencyResolutionException(SerializationInfo info, StreamingContext context) :base ( info, context) { }

Please see:
https://social.msdn.microsoft.com/Forums/en-US/5b411a37-fafb-475f-9eb0-ee82955bf15a/the-constructor-to-deserialize-an-object-of-type-was-not-found

@tillig
Copy link
Member

tillig commented Sep 4, 2018

Duplicate #456.

@tillig tillig closed this as completed Sep 4, 2018
alexmg added a commit that referenced this issue Sep 10, 2018
…endencyResolutionException serializable.
@gclpixel
Copy link

gclpixel commented Mar 6, 2019

The fixes doesn't resolve the problem with the required serialization constructor, this ctor exists also in .NET Standard 2.0.
The missing ctor is really annoying.

public DependencyResolutionException(SerializationInfo info, StreamingContext context) :base ( info, context) { }

@alexmg
Copy link
Member

alexmg commented Mar 6, 2019

@gclpixel It looks like I missed that constructor when enabling .NET Standard 2.0 support.

@alexmg alexmg reopened this Mar 6, 2019
@alexmg alexmg closed this as completed in 8988293 Mar 6, 2019
@alexmg
Copy link
Member

alexmg commented Mar 6, 2019

The fix will be in 4.9.2 or later.

@alexmg alexmg added the bug label Mar 6, 2019
@alexmg
Copy link
Member

alexmg commented Mar 24, 2019

This fix is included in 4.9.2 on NuGet.

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

No branches or pull requests

4 participants