Author Topic: Is .NET for CAD dead?  (Read 1179 times)

0 Members and 1 Guest are viewing this topic.

It's Alive!

  • Retired
  • Needs a day job
  • Posts: 7323
  • AKA Daniel
Is .NET for CAD dead?
« on: November 20, 2021, 10:48:40 PM »
I wanted to use the priority_queue class, but itís in .NET core, not framework.
Then I tried to use RBush: R-Tree Implementation for C# on GitHub. But this also requires features newer than whatís in framework.

Just disappointed that Microsoft depreciates stuff people have worked for years on  :crazy2:
Retired

huiz

  • Swamp Rat
  • Posts: 897
  • Certified Prof C3D
Re: Is .NET for CAD dead?
« Reply #1 on: November 21, 2021, 02:36:24 AM »
Framework is dead, not .NET :-)


I assume we move to .NET 5 in a near future AutoCAD version. Or we move to web programming when AutoCAD becomes web only.
The conclusion is justified that the initialization of the development of critical subsystem optimizes the probability of success to the development of the technical behavior over a given period.

MickD

  • King Gator
  • Posts: 3520
  • (x-in)->[process]->(y-out)
Re: Is .NET for CAD dead?
« Reply #2 on: November 21, 2021, 04:08:05 PM »
I'm all for web based app's but CAD is a tricky one. I think they're getting closer with webgl and wasm etc but it's the data that's the bottle neck. Loading and saving gig's of of a drawing db over the net is loaded with problems to solve like speed and data races etc.
It can be done but can AutoDesk keep up? As Daniel noted, they're behind already.


Just disappointed that Microsoft depreciates stuff people have worked for years on  :crazy2:


It's all to do with bring .Net to Linux/Unix for web/cloud services. It would be nice if they at least kept the framework as a wrapper into Core.
Forth is like the Tao: it is a Way, and is realized when followed.
Its fragility is its strength; its simplicity is its direction - Michael Ham

"The E in Javascript stands for 'easy'." ó Florin Pop tweet

CADbloke

  • Bull Frog
  • Posts: 337
  • Crash Test Dummy
Re: Is .NET for CAD dead?
« Reply #3 on: November 26, 2021, 07:19:36 PM »
Just disappointed that Microsoft depreciates stuff people have worked for years on  :crazy2:
Microsoft has always encouraged the vocal crowd to chase the shiny new things, presumably because it is what they make the most money from. There has also always been a silent majority who continue to use the stuff that works because it already works - Windows Forms is still a thing and it "ain't goin' nowhere".

.NET 3.5sp1 is scheduled for demolition in 2029, so 4.8 should last a while. See https://docs.microsoft.com/en-au/lifecycle/products/microsoft-net-framework

The ODA has released SWIG-generated .NET wrappers for for .NET core but not .NET classic which is the "legacy" source-code compatible SDK. Code for the SWIG version looks a lot more like C++ than the "legacy" source code.

But yah, it's annoying when the shiny new things are made from other shiny new things. Somethings you can head down the rabbit-hole and compile them from frameworks you do actually use, sometimes the rabbit-hole just keeps going.

People will abandon on-premise apps and storage to flock to the the cloud when it has no latency, data breaches, outages and bill-shock.
« Last Edit: November 26, 2021, 07:41:02 PM by CADbloke »

d2010

  • Bull Frog
  • Posts: 284
Re: Is .NET for CAD dead?
« Reply #4 on: June 04, 2022, 04:31:10 PM »
If the speed of NET inside Acad is too slow-of speed
--then in the future, Acad+NET may be dead, sure55%
 :woow:=Anyone, the speed of DLL/s are very-important.
Maybe, the VLISP is dead.?
Anyone==The Visual-Lisp was rescued by BrisCAD,ZwCad and GstarCad.

 :knuppel2:
I wanted to use the priority_queue class, but itís in .NET core, not framework.
Then I tried to use RBush: R-Tree Implementation for C# on GitHub. But this also requires features newer than whatís in framework.

Just disappointed that Microsoft depreciates stuff people have worked for years on  :crazy2:
« Last Edit: June 21, 2022, 01:42:23 AM by d2010 »

Rustabout

  • Newt
  • Posts: 114
Re: Is .NET for CAD dead?
« Reply #5 on: June 15, 2022, 12:13:53 AM »
d2010: The speed seems okay. Especially considering that most newer computers are overkill for AutoCAD. I could be wrong though as I'm not too experienced with .NET.

Microsoft absolutely had to improve .NET (and C#) to remain competitive. Short term pain for long term gain. Well... at least that's what I'm hoping for as I've committed a lot of time towards learning it. So hopefully the pain associated with upgrading from Framework is worth it.