Hi Pablo you’re right about having unnecessary references in SpeckleStructuralClasses.
I’ve cleared out the Revit ones (and others) on my SpeckleStructural nic/multithread branch, which I’m hoping to be able to merge back and release in the next week.
The only use for Presentation.Core is for some vector and matrix methods, which I’m currently planning to phase out in favour of MathNET.Spatial. So stay tuned on that one.
In terms of SpeckleStructural as a whole:
I was working to the recommendation that the conversion code should stay within the kit, which would mean these references (like Revit’s) remain in the conversion-related projects within the solution. If you guys have arrived at a different resolution then let me know! Happy to discuss further.