I want to move my SDK installation to another folder. To do so, I tried to remove all SDKs from the PLCnext extension in order to have them subsequently re-installed in the new folder.
While uninstalling the SDKs, the PLCnext extension crashed. It is now in an unrecoverable state.
Has this issue been fixed in the latest release? I’m currently using PLCnext extension v22.6.0.1153.
Steps to reproduce:
Even uninstalling and re-installing the Visual Studio extension doesn’t remedy the issue.
EDIT:
I did some further investigation: Apparently, it’s PLCnCLI that’s causing this issue:
Please advise.
I found a workaround for this issue by following 's advise he mentioned here:
Forum - PLCnext Community PLCnext Community Yet, I believe such situation should be avoided by further harnessing the VS extension and PLCnCLI.exe.
One more note on this:
I don’t think it’s wise to have the SDKs installed as a Visual Studio background process.
The process of installing an SDK takes minutes. If Visual Studio is being closed during that period, I’m pretty sure that the PLCnCLI process spawned by Visual Studio gets killed without further notice.
Hello WhiteKnight,
the SDK’s are managed by plcncli. The VS will be used as Code-Editor. The VS-Extention will be used for templates of PLCnext projects, access to plcncli and library builder.
If you would like to change the folder with SDK you have first remove the SDK-Entries in plcncli. Then you can create the new SDK-folder, copy the SDK-Installer-File into this folder and add or install the SDK via plcncli tool.
If you start the VS, the SDK should be found without any additinally steps, because the plcncli provides the information of available SDK’s.
I hope with this info the relaitions between plcncli, SDK, VS and VS Extention will be clearer.
If you have additionally questions, please don’t hesitate to ask!
BR Eduard
Hello Eduard,
I comprehend … still, the VS Extension provides buttons for removing SDKs. So, there is a GUI approach available.
If providing such functionality, I humbly suggest it to work properly and thoroughly, without getting any hiccups.
I particularly believe it is dangerous in a time constrained project to have the PCLnext VS extension perform installation steps in a non-modal dialog while being programmed without proper resumption measurements in case the installation process is getting aborted. So, I would rather suggest to perform any SDK operation in a modal dialog when hitting the [OK] button to avoid such misconfiguration situation.
Best regards,
Axel
The process of installing an SDK takes minutes. If Visual Studio is being closed during that period, I’m pretty sure that the PLCnCLI process spawned by Visual Studio gets killed without further notice.