Plugin Problems after upgrading to SDK 2020 R3

MIP
, , ,
1 
public partial class myAlarmPropertiesWpfUserControl : PropertiesWpfUserControl { ..... }

This plugin worked 100% properly before upgrading to the 2020R3 Milestone SDK.

Now we found that it does not work until going in SETUP, and tabbing through the fields. Then exiting SETUP.

What can we do to get our plugins working as well as they did before the 2020R3 SDK upgrade?

2

Regarding PropertiesWpfUserControl, we don’t expect to see properties unless you go to the Setup mode. Please see this page -

https://doc.developer.milestonesys.com/html/index.html?base=miphelp/class_video_o_s_1_1_platform_1_1_client_1_1_properties_wpf_user_control.html&tree=tree_search.html?search=propertieswpfusercontrol

It would surprise me if the control was seen if not in setup mode in the previous version. Perhaps you can elaborate on what is wrong assuming that it is not wrong that you only see the control when in setup mode?

3

I reinstalled MIPSDK_Redist_Installer_x64_2020R1.msi dotnet 4.6

and the plugin works 100%, without entering setup on a Milestone 2020R2 server. But with the 2020R3 sdk installed, the plugin does not work (on a 2020R3 server) until I go into setup and tab through the values and exit setup (then the 2020R3 compiled plugin function correctly).

We are not trying to “view” properties, but just have the plugin use the values. Definitely, no changes where made except recompiling for 2020R3. (We are also having trouble with other plugin(s) since the upgrade to R3 also.)

4

Can you please tell us what you are doing inside the control? We need to know about it for further investigation.

5

The issue is not really with the control.

The issue is: The plugin uses properties.

MY APOLOGIES …

It is NOT a 2020R3 bug.

I found I had Property variable names in this plugin

that matched Property variable names in another plugin**.**

Two plugins that had some properties with the

same exact name was fouling up my 1st plugin,

so this was MY BUG. Sorry about all that.

It is all working now in 2020R3.