You’re offline. This is a read only version of the page.
Hello, I'm currently in the process of registering a new plugin. All of my previous plugins were registered normally. However, when I select the latest plugins dll through the Update button in the PRT, the selected plugins dll has " - Isolatable" after each plugin in the assembly that was selected. These are the default settings in the "Update Assembly" dialog:
Isolation Mode=None
Location=Database
All of the plugins in my previous plugins.dll were registered without " - Isolatable" at the end. However, for some reason, they all now display " - Isolatable" in the "Update Assembly" dialog, although the plugins that were already registered do not display this in the normal PRT "Registered Plugins" view. Any idea why I might be seeing this behavior? I don't want to register the new plugin as Isolated or update existing plugins to be Isolated.
*This post is locked for comments
I have the same question (0)
Hi Guido, I haven't made any changes to the SDK or PRT in my environment. Sounds like simply having a plugin with "Isolatable" in the name:
* doesn't create additional limitations for the plugin
* doesn't make security less restrictive for the plugin
It really only means that the plugin has the *ability* to be registered in the sandbox for reduced functionality. I'm assuming that this is probably some sort of bit setting with *minimal* if any performance impact to support the overhead of supporting 2 different modes for the plugin.
However, I could see someone arguing that they wouldn't want a plugin to be "isolatable" because it could potentially allow a deployment admin to improperly register the plugin in the Sandbox which could unknowingly impact/reduce the expected plugin functionality. So is there any possible way to specifically remove the "Isolatable" setting from a plugin?
Share
Report
All responses (
Answers (
2
