Adding [Serializable] attribute to geometry3Sharp objects to allow Bi… #172
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…naryFormatter serialization
geometry3Sharp is popular and been used in many projects. most projects has their own objects where geometry3Sharp objects are being used and in modern applications cloning/caching/serialization is very common. C#.Net's native BinaryFormatter is fastest way of serializing big objects which you can only do with the objects decorated using [Serializable] attribute. And also the own project classes are not BinaryFormatter serializable if geometry3Sharp objects are used in it. This change will help many projects.