Debug-Virus has struck again!

[MichaelT_123]

Hi TF360,

Debug-Virus has struck again … hopefully only me but not for apparent reason.

The saga with the reliability of attaching VSCode+PythonDebuger seems to continue.

One can ask the simple question ... Why?

In this particular case, the system has been working fine for a week or so without resetting. After rebooting WinOS for maintenance purposes, I could no longer open VSCode in the usual way hitting Edit button.

Is there any file which logs steps of starting VSCode/debug a process which could help to identify the problem?

Regards

MichaelT

[MichaelT_123]

Hi TF360,

As the additional info I have noticed in the CMD window (just after hitting Edit button), very briefly (~0.5 s) displayed two lines:

?????? installing

?????? is already installed.

The second attempt produces nothing.

Is it possible that some flags regarding VSCode are corrupted or they haven't  been cleared up?

Regards

MichaelT

[MichaelT_123 · Accepted solution]

Uuuuffff,

... uninstalled VSCode, MS Python VS Extention,  scrubbed them cleanly, and installed them back (the latest versions). 

The System works now.

I am not sure, but the problem was probably triggered by maintenance - update of Intel System Studio.

The Windows Resource Protection process:

> sfc /scannow

has found the wrong hashtag on file mscormmc.dll

which is part of the Microsoft .NET Framework

responsible for Microsoft Management Console (MMC) module.

Regards

MichaelT

[MichaelT_123]

Hi Fellows,

Please read my 'foundation post'.

The problem still bites.

Does anyone have a problem launching VS_Code (by hitting the Edit button)?

I am currently on:

F360:

2.0.10148

VS_Code:

Version: 1.56.2 (user setup)
Commit: 054a9295330880ed74ceaedda236253b4f39a335
Date: 2021-05-12T17:13:13.157Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: 8.9.255.24-electron.0
OS: Windows_NT x64 10.0.19041

MS_Python:

v2020.10.332292344

I am repeating the question:

Is there any file that logs steps of starting VSCode/debug, which could help identify the problem?

If not, how difficult would it be to add a simplistic diagnostic? I believe that the CMD process does VS_Code launching.

How about adding a couple of script lines capturing possible errors in the successive steps required to bound F360 and VS_Code together ... which seems to be a persistent problem!?

Regards

MichaelT

[MichaelT_123]

Hi TF360,

Please consider that various update processes, from MS (Windows, Visual Studio, etc.) or other software vendors can mess up the configuration of VS_Code. The update of F360 itself changes the path to python interpreter and respective adsk modules. (C:\Users\MichaelT\AppData\Local\Autodesk\webdeploy\production\xxxxxxxxxxxxxx\Python)

How difficult would it be to check AUTOMATICALLY (while launching a debug session) if the proper python interpreter path (owned and contained by F360) is configured in VS_Code field - Python:Select Interpreter ?

Mind you, in the realistic user's development environment, there might be more than one python and its version installed.

Sincerely

MichaelT