Running custom .NET code in the cloud using AutoCAD I/O

Running custom .NET code in the cloud using AutoCAD I/O – Part 1

Jun 11, 2015

Over the coming weeks I'm going to be exploring – and blogging about – the ability to run custom .NET code inside AutoCAD I/O. After all, I've submitted an AU class on the topic, so I really do need to get my head around it. 🙂

I see this series being made up of the following high-level tasks, although each of these may end up requiring multiple posts to cover (and conversely there may be some that can be covered in a single post):

Writing a CRX module that's I/O-ready
Building an Autoloader bundle for the CRX module
Defining an Activity in AutoCAD I/O that uses a custom AppPackage
Implementing a web-service (in our case using Node.js) that creates and executes WorkItems using our custom Activity

As mentioned previously, the plan is to use AutoCAD I/O to power Jigsawify.com, a web-site that lets you upload images and create custom, laser-cut jigsaw puzzles. We'll start with the C# code in this post, but it will certainly need extending with additional capabilities (irrespective of any plumbing-related changes it needs to work with AutoCAD I/O).

I haven't yet tackled all of the above bullets, so the list may end up morphing over the course of the series. So I'd say the above is really a "statement of intent", for now.

In the next post we'll start by looking at the changes needed to an existing CRX module – in our case one implemented using .NET – to make it useable with AutoCAD I/O.

photo credit: Undulatus - 01 via photopin (license)

7 responses to “Running custom .NET code in the cloud using AutoCAD I/O – Part 1”

James Maeding

June 11, 2015 at 6:12 pm

Kean, there are many of us that write tools for a company, and do not put in the app store, write autoloaders for, and anything but the .net dll that some menu loads and commands become available. Can you explain what will be the minimum additional stuff we must learn? to use with I/O?
You can imagine, companies looking to use I/O to supplement their workflows, have a different use sceario than a web page anyone can go to. Sorry if you have gone over this before, I need some kind of summary of where we are at currently though. thanks

Reply
1. Kean Walmsley
  
  June 11, 2015 at 7:00 pm
  
  James,
  
  No worries - we'll definitely cover this. The main task is actually going to be ripping out any UI capability (other than some limited command-line interaction). Most of the input is going to come from a JSON file... but we'll see that in the next post.
  
  Cheers,
  
  Kean
  
  Reply
Kerry Brown

June 12, 2015 at 3:34 am

Hi Kean,
I'm looking forward to this series. Should be a good reference ... so I offer a premature thanks.

BTW: (do I need to say 'Personal Opinion' ) The new site layout is a great improvement.
Looks like you have a bit more width available for your code pane ... does this make it easier for your code formatting ??

Regards,
Stay well,
Kerry

Reply
1. Kean Walmsley
  
  June 12, 2015 at 4:39 am
  
  Hi Kerry,
  
  I'll do my best to deserve those thanks. 😉
  
  Thanks for the feedback - glad to hear you like it. It will make code formatting easier, in time - I just have to get over my 9-year inertia of ending lines at 70 characters.
  
  Cheers,
  
  Kean
  
  Reply
Garrett Fulghum

June 12, 2015 at 6:46 am

Hi Kean,
Ive been searching for some way to implement the Microsoft kinect sensor into a cad Application such as Autodesk Inventor... I know you are mainly working in AutoCAD but I was wondering if this could somehow be implented... I think its a long shot at best as there will be complications. However if you could suggest some other way of doing it I would greatly appreciate it. If you can't help I totally understand... Thanks!

Reply
1. Garrett Fulghum
  
  June 12, 2015 at 6:47 am
  
  whoops wrong post sorry...
  
  Reply
  1. Kean Walmsley
    
    June 12, 2015 at 2:11 pm
    
    Hi Garrett,
    
    Not to worry - it happens. 🙂
    
    I don't know enough about the integration you have with Inventor via its API, but at least part of the integration I developed for AutoCAD should work there, too. The more logical step is for it to be integrated with ReCap Studio or Memento and have those products feed Inventor, though. Not that I know of any work in that area.
    
    Regards,
    
    Kean
    
    Reply