CaptainGreenhat Posted 15 hours ago Posted 15 hours ago I basically have a full suite of Divoom devices, but unfortunately they don't integrate particularly well with anything. One of the simpler ones is probably my Dittoo Pro, which is essentially a Bluetooth speaker with a 16×16 pixel-art display. I can already send images to it over Bluetooth using various GitHub projects and libraries, so I'm trying to build a simple .NET LaunchBox plugin that reacts to game selection changes and eventually sends the appropriate image to the Dittoo Pro. I've got the basic LaunchBox plugin working: it loads normally and receives SelectionChanged events. The weird part happens when I try to access the selected game. As soon as I reference PluginHelper.StateManager (for example, GetAllSelectedGames()) or try to access the IGame through that route, the plugin stops loading and LaunchBox gives me: "The plugin ... could not be loaded because Windows is preventing access to it for security reasons." The DLL is locally built in Visual Studio. There is no Zone.Identifier alternate data stream, and the DLL's Properties don't even have the usual "Unblock" checkbox. I've also verified that the DLL is actually being rebuilt and getting a new timestamp. What's especially strange is that the exact same plugin loads fine as long as I don't reference PluginHelper.StateManager. Adding that reference is enough to make the plugin fail to load. Has anyone run into this with LaunchBox plugins/.NET, or have any idea what Windows/LaunchBox might actually be objecting to here? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.