force
force
Approach with 0.x version is acceptable (there are some pros for this). But yes, I need to switch it to 1.0.0 I'll try to implement one feature related to dictionary...
It can be problematic on Windows due use of native handles, which are problematic to clone. When you dispose one object, it closes native handle, so, other object stops to...
Every IntPtr is a problem. In dotnet it simply native int (long/int depends on architecture). But it points to some unmanaged resource. And when we clone object - two object...
Will check it later. Thank you.
Thanks for PR. I'll do my best to find time to merge it and publish new package. I'm alive, but really has problems with spare time
@brantburnett I'm really sorry. I'm trying to take some vacation to fix issues and merge PR. Lot of work and other stuff.
Sorry, I still do not have time to merge and review all changes. But I hope, I'll find it.
Currently, there is no such ability. I've received another similar issues and will try to implement related feature.
Not implemented yet. Sorry, I have no time to do this in nearest time. It not simple because code tries to clone object itself in one step (if possible), for...
I have ideas, but do not have enough time to fix it. You can try to do something like ``` var assembly = Assembly.GetAssembly(typeof(DeepClonerExtensions)); var deepClonerSafeTypes = assembly.GetType("Force.DeepCloner.Helpers.DeepClonerSafeTypes"); var knownTypesField...