« AutoCAD 2016 Developer Documentation Changes | Main | AutoCAD Developer Documentation Survey - 2016 »

Comments

AlexFielder

Hi Lee,

Great work on all of this; my question is:

Has the same work on Visual Studio Intellisense been carried out for both the Inventor and Vault APIs?

And who would I have to ask to see if it can be completed in future if not?

Thanks,

Alex.

Lee Ambrosius

Hello Alex,

I am not aware of any other efforts involving Intellisense for Autodesk desktop APIs other than the work I have done for the AutoCAD Managed .NET libraries. This work and research has only been done within the last few months, so there hasn't been much time to discuss the process I am using to generate the XML files with other groups yet.

I do plan on sharing the process with the other teams inside Autodesk, but how the content is currently stored and published is the hurdle along with resources. I will pass the request along to the Inventor/Vault tech pub teams for them to support Intellisense in the future.

Sincerely,
Lee

GuillaumePlax

Hi Lee,

Is there anything new in ObjectARX to control point clouds ?
Working with point clouds using C# or VB.NET would be very useful.

Thanks,

Guillaume

Lee Ambrosius

Hello Guillaume,

I am not aware of any changes to the APIs related to point clouds in AutoCAD 2017, only the general graphic system changes which should improve the performance of point clouds.

Thanks,
Lee

Tharwat

Hi Lee,
I downloaded AutoCAD 2017 and I already have VS community 2015 installed on my system , so I also downloaded the ObjectARX for AutoCAD 2017.
I opened one of my simple programs in VS and start the program and of course after setting the Start external program to Cad 2017, so AutoCAD 2017 started as if I running the codes on Autocad 2015 and it did not run in VS environment.

Is there any settings I need to change to have autoCAD running in VS as you have mentioned into your precious article in this page?
Thank you.
Tharwat

Lee Ambrosius

Hello Tharwat,

Are you referring to debugging an application in AutoCAD or accessing the developer documentation/XML documentation from inside Visual Studio?

Thanks,
Lee

Tharwat

Hi,

I am referring to debugging an application in AutoCAD and it didn't run AutoCAD 2017 in VS by default nor after debugging.

Steps;
Hit start in VS to debug then CAD2017 starts/runs then call NETLOAD to select the .dll file then invoke the command name of the program.
Thanks.

Lee Ambrosius

Do you have Update 1 installed for Visual Studio 2015? I do know that we don't support Update 1, but think it is simply related to VC++ though. I will look and see if I can identify the problem, but things should work just like they did when debugging an application in VS2012 for AutoCAD 2016.

Thanks,
Lee

Lee Ambrosius

I was able to compile and debug a .NET application without any problems using VS2015 Pro and AutoCAD 2017. The command paused at the breakpoint as expected while the command was executing. So I am not sure what problem you might be encountering, can you share your project settings with me? I am assuming the project compiled fine for an earlier release, if so what release were you targeting before.

MASSIMO CICOGNANI

A few people are experiencing problems porting their project from VS2013/ACAD2016 to VS2015/ACAD2017.

See .NET forum:
https://forums.autodesk.com/t5/net/first-steps-with-autocad-2017-and-vs2015/td-p/6232024

@Lee, it'd be interesting to see your settings if you say you had no problems. Have you turned on 'Managed Compatibility Mode'?
Were you still able to use Edit&Continue?

Can you join us at that forum argument and share?
Thank you

Lee Ambrosius

I debug my projects without Edit & Continue, mainly because much of what I do is across multiple releases of AutoCAD and versions of VS. I do have the same problem with Edit & Continue though and have reached out to the SWD team.

This problem seems to be similar to what was happening with VS2013 and earlier releases of AutoCAD:
http://through-the-interface.typepad.com/through_the_interface/2013/11/debugging-autocad-using-visual-studio-2013.html

I will post an update when I get any information to share.

Lee Ambrosius

There is a known issue that is currently being looked into that was fixed in a previous release and has since resurfaced in AutoCAD 2017. There are two known workarounds at the moment to allow debugging with Visual Studio:

•Tools > Options > Debug-General > Use Managed Compatibility Mode
•Project > Properties > Debug Enable native code debugging

Both these options do result in the disabling of Edit & Continue.

Hussein

Hi Lee
can you tell me, where I will find the objectarx wizard 2017?

Lee Ambrosius

I inquired about the ObjectARX 2017 Wizard 3-4 weeks ago and there was some talk in updating it, but a technical problem was encountered to my understanding and that is why there was a new version created for Managed .NET and not ObjectARX. The code for the ObjectARX Wizard is on GitHub (https://github.com/Developer-Autodesk/ObjectARX-Wizards) if you want to try and make the changes yourself. I am sure once the new one has been built though, it will be posted with the others at http://www.autodesk.com/developautocad.

I will do some following up on the wizard if the new one hasn't been posted by the time I get back from sabbatical.

Gareth

Hi Lee,

Do you know when Autodesk will release the Map ObjectARX 2017 libraries as they still not available: http://usa.autodesk.com/adsk/servlet/item?siteID=123112&id=868205

We need these to compile our code...

Lee Ambrosius

I am not aware as to why the AutoCAD Map 2017 Object SDK hasn't been posted yet to the site. I did send an email about this issue, but will not hear much other than maybe a reply as to why I am sending emails during my sabbatical. :) If I hear anything, I will add a new comment.

Lee Ambrosius

Hello Gareth,

The AutoCAD Map 2017 ObjectARX SDK has been posted to the URL you mentioned; my understanding is only 64-bit is supported even though the page lists both 32- and 64-bit. I might be wrong as I was parsing the email rather quickly.

Thanks for bringing this to my attention, even though it wasn't doc, I am always happy to communicate issues onto others when I can.

Sincerely,
Lee

The comments to this entry are closed.

My Photo

My Other Accounts

LinkedIn Twitter

Twitter Updates

    follow me on Twitter