My logic has three separate AddOns with different code for each. They display colored text in my own defined UserControl which is custom built as a DLL and used in the xaml.
When starting up I look them up successfully and set their "Content" to simple identifying text strings. (originally for debug)
During runtime the content changes, and what has happened with the latest NT8 build is it appears these three are now ONE object as the first one works and the other two generate exceptions saying the object is owned by a different thread. There are three when initially look them up, but when using a Method call to "obj.SetContent(string)" one works and the other two trap saying not owned by task.
This was working fine until upgraded NT8 today to latest build. It is now creating all sorts of weird issues as well.
Does this make any sense? I've been programming a long time this isn't a new user type error. Did try to create three different user control classes as well in the DLL but the problem persists even with different named classes.
Comment