Will VSCode Python Extension downgrade be fixed?

[regalheros]

Hi,

Is there a solution to the "downgrade Python extension to fix VSCode not opening"?

I have:

1. Downgraded VSCode Python Extension to 2019.9.34911.  <Begrudgingly>

2. Opened a Python script for editing in Fusion 360.

3. VSCode opens.  <Great>

4. Upgrade Python Extension to 2020.8.103604 (latest today).

5. Running the script from VSCode (press f5) results in object appearing in Fusion 360.  <Fantastic>

It appears Fusion can't 'link' to VSCode.  No problem with VSCode.

As I don't only use VSCode for Fusion 360 programming I would like a fix to this.  Is there a time frame for this?

Using VSCode 1.48.2, Fusion 360 2.0.8816 Personal

Would it be possible for Autodesk to provide a Remote Fusion 360 Extension for VSCode allowing connection between the two programs?  Much like Microsoft does for WSL (Windows Subsystem for Linux).  Just a thought.

Regards

RH

[goyals · Accepted solution]

We are working on it and will try to provide fix in next Fusion release. Thanks.

[regalheros]

Hi,

Great news; I will look forward to the new version.

RH

[Anonymous]

Meant to reply to the person claiming this is solved by "promising" it would be fixed by now...

[Anonymous]

How is this Solved?  I'm fairly sure there have been several new versions since this.
I'm still using the outdated extensions but still. not working 

[BrianEkins]

This has been solved.  Microsoft retired the previous component Fusion was using to work integrate with VS Code. It's been replaced with a new component and Fusion switched to the new component a few months ago.  Since then, you have been able to use the latest Python extension.