Good morning.
We are live with 2025.2 on prem. We have one screen that we are still running in classic because it is dependent on Seagull Bartender SDK dll (Seagull.BarTender.Print.dll). We are actively working to convert it.
As of Bartender 2022, the SDK DLLs are only 64 bit.
With Kinetic 2022, we would just switch users, that need to use this screen, to run the Kinetic 64 bit client.
In 2025, this is still the same, but what is odd is that we have to open this screen in the 32 bit version first, close Kinetic, open the 64 bit client, and open the screen to avoid a compile error.
We need to use this process for each user that logs in as it seems to be user specific.
If we start by opening this screen in the Kinetic 64 bit client it throws a compile error that states that it cannot find the Seagall namespace, but after the steps above, it works.
I was wondering if anyone has any ideas on what might be causing this so that we can find a way to avoid the 32 bit/64 bit workaround until we can finish converted this screen.