Home > Forum > Plugins > WEBCON BPS SDK Tools does not start after Update to Visual Studio 2022 v17.12.x

WEBCON BPS SDK Tools does not start after Update to Visual Studio 2022 v17.12.x
0

Hello,

yesterday, after installing the current Visual Studio 2022 Update v17.12.x (from v17.11.x), the WEBCON BPS SDK Tools no longer started when trying to open them via 'View -> Other Windows -> WEBCON BPS SDK Tools'.

I've got an error message (I don't have a screenshot from this message) with a reference to the ActivityLog.xml file within the VS main program folder.

On the ActivityLog.xml file I've found a System.Reflection.TargetInvocationException, followed by a System.IO.FileLoadException and a HRESULT exception number.

The issue occured with all version of WEBCON BPS SDK Tools available via Visual Studio Extension Manager (2022 to 2025).

Long story short, nothing helped, not even repair installation of VS via VS Installer. Only when I downgraded to v17.11, the Tools worked again.

Hope someone can confirm this as bug of 17.12 or helps another one to solve this issue.

Greetings
Marco

MVP
In reply to: Franek

I have the same problem.(bps tools 2022-2025) So, how can we publish an extension package without the WEBCON BPS SDK Tools?

The publishing mechanism for a simple SDK, no form field extension, is:
- Updating the assembly version number
- Create a .zip package with the necessary .dlls and the JSON file containing the SDK actions

I've created two PowerShell scripts which I execute as
Pre-build event: IncreaseRevisionNumber.ps1
Post-build event: CreatePackage.ps1
https://github.com/Daniel-Krueger/webcon_xmlToItemList/blob/main

<PropertyGroup>
<PreBuildEvent>powershell $(SolutionDir)\IncreaseRevisionNumber.ps1 -absoluteProjectFolder $(ProjectDir)</PreBuildEvent>
</PropertyGroup>
<PropertyGroup>
<PostBuildEvent>powershell $(SolutionDir)\CreatePackage.ps1 -targetDir '$(TargetDir)' -projectDir '$(ProjectDir)' -projectName '$(ProjectName)' </PostBuildEvent>
</PropertyGroup>

You may need to update the package file, to exclude more files.

Best regards,
Daniel