The PowerShell hosting inside of AutoCAD

[Anonymous]

Here is the sample (code sources) of PowerShell 4.0 hosting inside of AutoCAD 2016. Here is video. Here is compiled version for AutoCAD 2016.

[Anonymous]

Did this ever get going or do people still use acad lsp? I am wondering because I am an IT at an architecutre firm and powershell would be really helpfull. 

Do you manage autocad at your firm? 

[Anonymous]

>Did this ever get going or do people still use acad lsp?

99% of my users don't know LISP or any other programming language. Practice showed that PowerShell is known by very few programmers and to study this tool they have no desire. It is silly, but it is their problem, but not mine.

In real life I didn't meet the customers which would know PowerShell. This theme is intresting for nobody in my practice (except admins).

>Do you manage autocad at your firm? 

Yes, I am admin of CAD systems also.

[Anonymous]

Thanks for clearning that up for me. I really felt like I was going to see a similar answer to what I was thinking. It seems like none of my users use acad.lsp or powershell. I use both lightly. Thanks for creating this. Do you have a way to batch DWG to PDF in your domain? Im trying to automate that process. It could be useful for users who just need to make PDFs for presentations. 

[Anonymous]

I think it is possible to do through WCF service (and would be very convenient). For example, I use WCF service (on the remote machine) for Resaving DWG newer than 2007 versions to DWG 2007 (my users use AutoCAD 2009). Also I use WCF services for auditing, explode | remove proxy and purging. My WCF service can do it through either Teigha .Net API Classic or through AutoCAD .NET API. I can switch remote API transparently for users when I need it.

If I want to use AutoCAD .net API on remote machine then my service uses `accoreconsole.exe` instead of `acad.exe` because it would be very slowly. It is possible to host WCF services in the AutoCAD 2013-2015, but it doesn't work in AutoCAD 2016. Because accoreconsole.exe of AutoCAD 2016 was done through a_s_s (in my opinion). I don't check it for AutoCAD 2017.


So, my clients [i.e. my client applications on the local machines] haven't new AutoCAD version or Teigha .NET API. That API is located on the remote machine and can be changed | updated when I need. Using of WCF service is very convenient for batch processing also.

I think (and I am sure) that it is possible to write WCF service for PDF publication too.