Visual Basic & VBA
-
Over the weekend I received an email from Jürgen Becker. It came with this image, which certainly brought back memories. The email referred to our recent trip down memory lane… I read your last post and remembered a poster. Do you remember that release, it was terrible? This is one of my favourite "chat over a beer" topics, and one that seems relevant to where we are today with Fabric, so I wrote Jürgen a quick note to say that I'd reply via my blog. Here is that reply. R13 was bad, but it had to happen I joined Autodesk…
-
The AutoCAD team is running their annual survey to better understand developers' needs relating to documentation. Access the survey here before the end of May. Lee Ambrosius provides more information over on his blog, including some interesting data-points from last year's survey as well as areas of the documentation that were influenced by it.
-
This series of posts is one I've been meaning to write since AutoCAD 2016 started shipping. Thankfully a number of other people have filled the void, in the meantime, so I've created an appendix of related posts that you can find at the bottom of each post in this series. The series is about how we're working to improve security inside AutoCAD, and what this means for application developers. Dieter's posts on Lynn's blog help explain some of the background to this work, much as I've posted here in the past, too. Perhaps the biggest security change in AutoCAD 2016…
-
photo credit: Marcin Wichary via photopin cc As mentioned in the last post, fibers are now inactive in AutoCAD 2015 (the code paths are still there, largely for testing purposes, but should not need to be enabled for typical usage of the product). Fibers were a technology that Microsoft introduced way back when to help single document (and typically single-threaded) applications adapt more easily to the brave new world of MDI. At least that's my recollection and understanding. They were basically a mechanism by which applications such as AutoCAD could manage their per-document state, making the relevant data current depending…
-
Viru Aithal from the ADN team posted a link to this survey on the ADN DevBlog and asked that I post it here, too. The survey will help us determine your priorities for developer-oriented documentation, so we definitely appreciate the time you take to fill it out. [You might even find out about documentation resources of which you were previously unaware – there's quite a list in there.] My inbox is nearly back under control after my week of holiday, so I'll certainly be posting more during the course of the week. photo credit: splorp via photopin cc
-
As reported by Tom Stoeckel over on Without a Net, AutoCAD 2013 Service Pack 1 is now available for download. I've been waiting for this release with some impatience… in my new role I've been increasingly involved in discussions around the security of AutoCAD and our customers' data, and this Service Pack makes significant progress in this area. As Tom notes, malware attacks in AutoCAD typically† take advantage of the fact that when a drawing is loaded, AutoCAD tries automatically to load various types of acad.* files (acad.dvb, acad.lsp, acad.fas, acad.vlx, …) from the drawing's folder. Which means that when…
-
As mentioned in this previous post, the following API wishlist surveys are currently live: AutoCAD® AutoCAD® Civil 3D® AutoCAD® Map 3D® Revit® Autodesk Inventor® Autodesk Navisworks® We've had around 500 responses across the various surveys, but to give a few more people the chance to respond, we've extended the deadline until June 11th, 2010. To give you an idea of how the voting is looking so far, here's a summary of the responses against the survey's "money" question (5. From the following list of possible AutoCAD API enhancements, please choose three areas that you recommend we make our top priority…
-
In this previous post I mentioned a couple of additional translations of the VBA migration DevTV that were in progress. Here is an updated list of the various ones we now have available, including links to German, Spanish and Japanese versions: English view download (44.7 MB) Chinese view download (88.9 MB) French view download (39 MB) Portuguese view download (80.3 MB) Russian view download (39.3 MB) German view download (42.4 MB) Spanish view download (52.9 MB) Japanese MP4 download (66.9 MB) WMV download (78.5 MB) A big thanks to Augusto Gonçalves, Jeremy Tammik, Shigekazu Saito and Katsuaki Takamizawa for…
-
To help people who don't master English with their efforts to migrate their code from VBA to VB.NET, my team has been busy translating our existing AutoCAD VBA to VB.NET Migration Basics DevTV session into other languages. Here are the languages we have, so far (including an updated English version): English view download (44.7 MB) Chinese view download (88.9 MB) French view download (39 MB) Portuguese view download (80.3 MB) Russian view download (39.3 MB) A big thanks to Augusto Gonçalves, Xiaodong Liang, Philippe Leefsma and Marat Mirgaleev for their hard work on these sessions. German and Spanish versions should…
-
We've had a few reports from people implementing external .NET applications to drive AutoCAD – as shown in this previous post – experiencing intermittent failures once AutoCAD 2010 Update 1 has been applied. Here's a typical error message: It contains the text "Problem executing component: Call was rejected by callee. (Exception from HRESULT: 0x80010001 (RPC_E_CALL_REJECTED))" (to help people Googling this error message :-). This "problem" was introduced as we addressed an issue with the way our WPF components in AutoCAD handle inbound messages, largely due to Microsoft's decision not to support nested message loops in WPF. If WPF is in…