Looks like I missed to publish this for Inventor 2024 but some people do need it, so here it goes.
If you are using any of them from your add-in then the best is to make sure you are using the same version to avoid version conflict:
|
Component Name |
Version |
|
DevExpress |
21.1.5 |
|
7z |
22.00.0.0 |
|
SQLite |
3.30.1 |
|
QtTK |
6.2.40 |
|
QtMFCBridge |
620.280.2 |
|
TBB |
6.1.30 |
|
NLog |
4.7.10 |
|
WebView2 |
1.0.1210.39 |
| |
|
Are you a huge fan of Autodesk Fusion 360? Do you have a robust community or following that trusts your opinion on software (and other things)? The Fusion 360 Marketing Team has a lucrative proposal for you: join our affiliate program!
Affiliate marketing is a process by which an affiliate earns a commission for selling another company’s products. At Autodesk, potential affiliates apply to our program and, once approved, are given unique links and visuals to use when mentioning our products on their channels. Members receive a commission on every verified sale made through their unique link.
What’s in it for me?
The team at Fusion 360 is looking for passionate community members with a following that would respect their opinion on design and manufacturing software solutions. We think such valuable voices deserve compensation for any sales they help make happen, so we offer a starting commission of 7% on verified digital sales.
The Fusion 360 team is really excited to launch a program that recognizes and rewards our community members in everyone’s favorite way: cash! If you’re interested, please reach out to the Fusion 360 social media manager at [email protected], or simply DM us on social media to get in touch.
-Muna Idriss
| |
|
Fusion 360 is migrating to a newer engine of Python and it will make your add-in fail if it's relying on compiled Python files (*.pyc)
For more info see https://help.autodesk.com/view/fusion360/ENU/?guid=GUID-36B1FFB5-5291-4532-8F11-90E912769B34
-Adam
| |
|
Our yearly webinars about the new product API features (both cloud and desktop) are coming up at the beginning of March.
You can find all the details here if you are interested in joining us:
https://adndevblog.typepad.com/autocad/2021/01/join-us-for-our-devdays-online-webinars.html
| |
|
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 🎉
| |
|
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
| |
|
We stopped fully supporting the JavaScript API a few years ago, but your existing add-ins using it kept running.
Not anymore. In December they will stop running, and you need to migrate your add-ins to another programming language: either C++ or Python.
See post from product management: Notice: Javascript API is being fully retired
Edit: looks like now there is also a pop-up dialog warning you if you have a JavaScript add-in installed:
-Adam
| |
|
Join us for our special series of webinars where we’ll be going over some of the topics covered last year's DevCon events in detail (see full list below). These webinars are a great opportunity for you to learn about Autodesk Forge and, of course, where Autodesk is taking the desktop platforms in the coming year.
Click on the links below to register today for the webinar(s) of your choice. All webinars start at 8am PST (4pm GMT, 5pm CET, 11am EST). If the session timing is inconvenient for you to attend (which is true for most of our partners in Asia), you can rest assured we will be recording all the sessions and will post them on the web for your later viewing. Registration is open to all except where noted below.
Tuesday February 25 - DevDays Keynotes
Jim Quanci, Senior Director for Software Partner Development, kicks off our DevDays online webinar series with the latest news for desktop developers (get ready for the 2021 releases this Spring), Forge roadmap that includes the Forge Design Automation CAD Engines on the cloud (AutoCAD, Revit, Inventor and 3ds Max) and an overview of the enhanced BIM 360 APIs for the Autodesk Construction Cloud.
Register - https://autodesk.zoom.us/webinar/register/WN_J-iJ9Iy1TQ-TYgB3CdQoLg
Wednesday February 26 - Forge API update
Augusto Goncalves will discuss in detail the updated and new APIs added to the Forge platform during the last year.
Register - https://autodesk.zoom.us/webinar/register/WN_MlyzAqW8TF-oC7XPFcC7FA
Thursday February 27 - Revit, Civil 3D and InfraWorks API updates (for ADN members only)
Join Mikako Harada and Augusto Goncalves to discover the product and API changes and enhancements coming in the next releases Revit, Civil 3D and InfraWorks.
Register - https://autodesk.zoom.us/webinar/register/WN_jLl0gXjxTnK3PWHsGyzARg
Tuesday March 3 - Inventor, Vault and Fusion API update (for ADN members only)
We will review upcoming changes in the next release of Inventor as well as recent updates in Vault and Fusion 360 API.
Register - https://autodesk.zoom.us/webinar/register/WN_XlRo7ADySLGofmc7M9cdkQ
Wednesday March 4 - BIM 360 API update
Learn about the new APIs for the BIM 360 family. We’ll talk about what’s in the pipeline for API enhancements.
Register - https://autodesk.zoom.us/webinar/register/WN_TIxv3ZpPS1228DYy_-i7HA
Thursday March 5 - The next release of AutoCAD APIs (for ADN members only)
Discover API changes coming in the upcoming release of AutoCAD Rogue
Register - https://autodesk.zoom.us/webinar/register/WN_h1Mmc-leRjKAFhqIjiv9Sw
After registering, you will receive a confirmation email containing information about joining the webinars.
| |
|
We already have some articles on using the Entitlement API from Inventor:
- Entitlement API in Inventor
- Entitlement API in Inventor 2018
There is now a change you have to be aware of.
Starting with Inventor 2020, to guarantee the Entitlement API calls work properly to get the UserName, call the Inventor API's Application.Login() function before or after webServiceMgr.Initialize() so the WebServices are fully initialized.
Otherwise, you may see a valid UserId, but an empty UserName when the user is already logged in:
Note: the Application.Login() function is hidden, so IntelliSense in Visual Studio will not list it.
And, if the user attempts to login when you have not used the Login() API call, they may get an error dialog that the service is not available:
You can use the following code to get userId and userName:
public void Activate(Inventor.ApplicationAddInSite addInSiteObject, bool firstTime)
{
m_inventorApplication = addInSiteObject.Application;
CWebServicesManager mgr = new CWebServicesManager();
bool isInitialized = mgr.Initialize();
if (isInitialized)
{
try
{
m_inventorApplication.Login();
string userId = "";
mgr.GetUserId(ref userId);
string userName = "";
mgr.GetLoginUserName(ref userName);
MsgBox.Show(
"User ID = '" + userId + "\n" +
"User Name = '" + userName + "'");
}
catch (Exception ex)
{
MsgBox.Show(ex.Message);
}
}
}
This solved the problem:
As pointed out in one of the above-referenced articles, there is a GitHub repo with a project showing the usage of the Entitlement API from an Inventor add-in. I updated it with "releases" for Inventor 2016/2017, 2018/2019 and 2020: https://github.com/ADN-DevTech/EntitlementAPI_Inventor
-Adam
| |
|
We are upgrading the Python version used in Fusion 360 to 3.7.3 in the September release.
It could mostly impact add-ins written in Python where the version of Python used to compile the source code to a *.pyc file has been locked down.
If that is the case then please test your add-in once the September release is out, and in case of any problems, recompile your add-in with the 3.7.3 version of Python and upload the new version of your add-in to the App Store.
It might be a good idea to check your add-in even if your Python source code is not compiled.
We are also going to replace the editor from Spyder to VSCode in this release.
If you've done any web development, you might be quite familiar with it already - and hopefully, you like it as well :)
| |
|
Subscribe