.NET native DWG/DXF importer without legacy DLLs
A .NET native DWG/DXF importer without the need to link OpenDesign.com DLLs. As a managed code developer, I hate to deal with these old fashioned unmanaged DLLs and associated *.TX and *.TXV files.
Sounds great! Are you going to go and grab the binary layout(headers, offsets, checksums and the like) from the C++ part and create your own objects from that, or are you going to go he Hexinator way? :D
Let's say both, very hard project but vital for our tools. We cannot make any promise yet.
Would be a great feature. Strongly needed.
I was wondering if you will be able to keep uptodate this new importer with new release of DWG and DXF format. You can like ODA or not, but they are doing also this at the moment.
It is not a criticism, just a consideration. I love Eyeshot and what you are doing.
To our knowledge, DWG file format is dead. I mean, it will not get any new features. This is the reason why we embarked on this project
The thing is it still will be windows product. Because GUI WPF is for windows, and lib is still only .net 4 framwork. I rather see this app running on .Net6 with WPF.
As for geometry, it might be that online services could use that for opening files, but may there are C++ lib files that might be deploying for Linux.
Not really. Once resolved the licensing issue (currently not compatible with .NET Core) we will be able to deliver a cross-platform geometric kernel that could read/write DWG files.
Will I able to launch on .Net core GUI part WPF? (On Win PC of course)
We aim to have the same geometric kernel for both cross-platform usage and Windows UI usage.
Alberto, what do you mean when you said DWG file format is dead? To me Autodesk will most likely keep on "innovating" on the file format for DWG ( the latest is 2018) for economical reasons. You can expect DWG version 2xxx that cannot be opened by old version of Autodesk products.
Do you think? In the meantime, from year 2018 there are no news...
If there will be no more new DWG file format, I fail to see how this has anything to do with your decision to write your own native DWG file reader/writer ( though I certainly agree with your decision because I'm also tired of legacy DLLs)...
Salamender, It appears the decision to write their own import tool for DWG is because they don't expect changes in the format. It is no longer a moving target so they don't have to update the tool to support new versions. Developing a tool at this point is a onetime effort.
Please sign in to leave a comment.