.NET

Reply
Contributor
h.sezenn
Posts: 18
Registered: ‎03-27-2013
Message 1 of 4 (231 Views)

how can I draw duct with .net?

231 Views, 3 Replies
11-14-2013 10:53 AM

Hello everyone; ı would like to draw and modify my ducts with .net. but I have not any idea about my start idea? please give me some tips about this issue. may I use dynamic block , block or only line and arc while draw my ducts? as you see on picture , ı would like to draw my ducts like them.14-11-13-soru01.jpg

 

 

14-11-13-soru02.jpg

 

 

_____________________________________________________________________________________
Everything For Duct
*Expert Elite*
Keith.Brown
Posts: 1,195
Registered: ‎03-13-2008
Message 2 of 4 (223 Views)

Re: how can I draw duct with .net?

11-14-2013 11:21 AM in reply to: h.sezenn

Are you using AutoCAD MEP (from the picture it looks like it) or do you want to create your own duct package from scratch?  I only mention from scratch because you talk about blocks, lines, arcs, etc which is definately what AutoCAD MEP does not use.


Keith Brown AutoCAD MEP BLOG | RSS Feed
AutoCAD MEP 2014 | Revit 2014 | EastCoast CAD/CAM V6.1 | Visual Studio 2013
────────────────────────────────────
⁞|⁞ Please use Mark Solutions!.Accept as Solution and Give Kudos!Give Kudos as appropriate. Thank you!
Contributor
h.sezenn
Posts: 18
Registered: ‎03-27-2013
Message 3 of 4 (219 Views)

Re: how can I draw duct with .net?

11-14-2013 11:26 AM in reply to: Keith.Brown

No, I wont use autocad MEP.

I ll use Autocad only

actually I would like to make my own programme in autocad with .net.

give some tips about this. how can I draw and modify my ducts ?

_____________________________________________________________________________________
Everything For Duct
*Expert Elite*
dgorsman
Posts: 5,613
Registered: ‎10-12-2006
Message 4 of 4 (186 Views)

Re: how can I draw duct with .net?

11-15-2013 07:54 AM in reply to: h.sezenn

Plan.  Figure out the order of operations, what information you want to store, where it will be stored, what the user needs to enter, what can be looked up automatically.  Figure out how the objects will be implemented, how the user will interact with them.  Mock up user interfaces with sketches, run it past actual users so you aren't assuming anything ("Designed by a programmer for a programmer" syndrome).  Plan for how the program will be extended/improved in the future.

 

Once you have the plan, you can start outlining.  Start getting into details.  Find out what you know you don't know, and what you don't know you don't know.  Adjust the plan when it turns out you can't do what you wanted to.  Break the plan down into workable modules that can be developed and tested easily.

 

Start coding.  Focus on each module in turn.  Once the module is working, try to break it.  Get actual users to try to break it.  Gracefully handle all failures.

 

Put everything together.  Make sure it works as intended.  Trial run with users in non-essential role (ALPHA testing).  Incorporate any needed changes.

 

Trial run with users in semi-essential role (BETA testing).

 

Official roll out.  Gather feedback for improvements, bug fixes, and extensions.

----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
Adopt. Adapt. Overcome. Or be overcome.
A good question will be halfway to a good answer.


Post to the Community

Have questions about Autodesk products? Ask the community.

New Post
Announcements
Are You Going To Be @ AU 2014? Feel free to drop by our AU topic post and share your plans, plug a class that you're teaching, or simply check out who else from the community might be in attendance. Ohh and don't forgot to stop by the Autodesk Help | Learn | Collaborate booths in the Exhibit Hall and meet our community team if you get a chance!