Mod the Machine

Switch to latest VS Code Python extension

In the past, you had to stick to a given version of the Python extension in Visual Studio Code in order to edit and/or debug Fusion 360 add-ins with it.

Now I've just run into the opposite problem in case of the latest update of Fusion 360: when using that version of the extension (i.e. version 2019.9.34911) the "Debug" and "Edit" buttons inside the "Scripts and Add-Ins" dialog of Fusion 360 stopped working.

The engineering team confirmed that now developers should be using the latest version of the Python extension in VS Code.
And indeed, that does work for me too 🎉

Stricter call checks in Fusion 360 API

Last time it was the Python compiler that got stricter, in the latest update it's Fusion 360 that got stricter on API calls.

Previously, you could get away with trying to set a read-only property - it had no effect but did not cause an error either.

This change is good because now you'll get an error and will be notified as you're developing your add-in when you're trying to do something that does not make sense.

The only problem is if you happen to have a published add-in that includes such a call 🙄

If your add-in stopped working (like mine 🤫 ) in the latest Fusion 360 update then this might be it. 

-Adam