Impossible to add library if project is encrypted

[elconfa]

I found a problem: my project has software protection (encryption) of the project and Twinpack does not allow to import of any library into the project. By unencrypting the project, everything works fine. Currently, to work around the problem, I unencrypt the project, add the library, and then put the encryption back before uploading the project to the PLC.

Thanks

[iadonkey]

Can you please try the following:

• Unencrypt your project
• Create a config.json file by pressing the "Create" Button in the catalog.
• Encrypt your project again

Then you should be able to add libraries and keep the project encrypted. Since the project is encrypted it seems that Twinpack is not able to create the configuration on the fly. Having a configuration file should workaround this issue for now.

[elconfa]

The "Create" button gives me an error (the project is unecrypted)

[iadonkey]

Sometimes the automation interface is a bit weird here. Can you to save and close the solution, open it again and press create again please?

[elconfa]

I tried to unencrypt the project and close Twincat. Reopen the project, but the "Create" button still does not work.

[iadonkey]

Unfortunately we can’t reproduce the problem. Could you upload the Twinpack Log, which is located in

%LOCALAPPDATA%\Zeugwerk\logs\Twinpack\Twinpack.debug.log

If possible, could you also upload your solution? We need the general structure of projects, plcs of the solution to debug this. Maybe you have non-plc projects in your solution? (This would cause an issue atm). Of course you can delete all the source code for this.

If this is not possible and/or we still don’t find the issue with our setup: Since Twinpack is open source you could also try to debug it yourself. We will write a guide how to debug the vsix, but it boils down to this:

• Clone the repository
• Open Twinpack.sln with VS2022 and build the solution
• For TcXaeShell, copy the Content of TwinpackVsix/bin/Debug/Package to C:/Program Files (x86)/Beckhoff/TcXaeShell/Common/Extensions/Zeugwerk/Twinpack (overwrite the files that the installer placed here)
• Open your Solution in TcXaeShell and navigate to the Twinpack Catalog
• In VS2022 click Debug -> Attach to process and select the TcXaeShell
• Place a breakpoint in the File CatalogWindow.xaml.cs in the method CreateConfig_Click
• Click the create button in the Twinpack Catalog
• You can now step through and locate the issue