Publishing GUI for stadalone use

I’ve noticed this problem for awhile and have always simply compiled my GUI and copied the exe file into a directory where OpenTAP is installed and functional. However, I would like to use the publishing wizard in VS2022. Currently this builds an installation package and the GUI runs, but the opentap engine doesn’t seem functional. Hunting down the directory where clickonce installs this I see all the appropriate DLL’s, but no tap.exe. Copying tap in doesn’t solve the issue and testing with .\tap package list produces an error telling me to re-install OpenTAP. Is there a guide on setting up a VS project with OpenTAP and using the publishing wizard?

If you use the OpenTAP nuget package, you should get everything built into the same folder, so if you use that I think the publish functionality should work.

1 Like

The problem appears to be the publishing wizard doesn’t include a “settings” directory and some necessary “package”

FileNotFoundException: Could not load file or assembly ‘System.Reflection.Metadata, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. The system cannot find the file specified.

1 Like

Deploying a “settings” directory is basically covered by

1 Like

The “Package” issue is resolved the same way. For some reason my VS2022 project required copying my custom DLL in its package directory as well as the tupple dependency directory. Both dll’s were already in the root folder of the installed application.

1 Like

Hi Craig
I stick this in the Properties/AssemblyInfo.cs

[assembly: OpenTap.PluginAssembly(true)]

it seems to help opentap find custom plugins easier …

regards Andy